For agents and builders
The same atlas, over an API and an MCP server
Read-only today. Same visibility tiers, same shares, same audit log as the app: an agent sees exactly what the person who made its key can see.
1. Make a key
Sign in, open Settings, create a key. It starts with sa_ and is shown once. Public reads need no key.
2. MCP
Streamable HTTP at https://systematlas.org/mcp. Claude Code:
claude mcp add --transport http system-atlas https://systematlas.org/mcp \
--header "Authorization: Bearer sa_…"Any MCP client config:
{
"mcpServers": {
"system-atlas": {
"type": "http",
"url": "https://systematlas.org/mcp",
"headers": { "Authorization": "Bearer sa_…" }
}
}
}3. HTTP API
curl https://systematlas.org/api/v1/industries
curl https://systematlas.org/api/v1/industries/staffing
curl "https://systematlas.org/api/v1/search?q=payroll"
curl https://systematlas.org/api/v1/glossary
# with a key
curl -H "Authorization: Bearer sa_…" https://systematlas.org/api/v1/workspaces
curl -H "Authorization: Bearer sa_…" https://systematlas.org/api/v1/workspaces/acme-builders
curl -H "Authorization: Bearer sa_…" \
"https://systematlas.org/api/v1/workspaces/acme-builders/companies/client?public=1"
curl -H "Authorization: Bearer sa_…" \
"https://systematlas.org/api/v1/workspaces/acme-builders/compare?with=rival-construction-co"Responses are { data } or { error: { code, message } } with the matching HTTP status.
Tools and endpoints
- list_industriesIndustries with a published schema.public
- get_schemaAn industry's primitives, parameters, modules and connection types.public
- searchSearch primitives and modules by name.public
- get_glossaryThe ontology, every term defined.public
- list_workspacesWorkspaces the key can reach.needs key
- get_workspaceCompanies, completeness, layer health and top gaps.needs key
- get_company_atlasComponents, values with sources and confidence, edges and notes.needs key
- compareClient against competitors, one row per primitive, ranked by delta.needs key
What an agent can do with it
- Design against real structure. Pull an industry schema and a client atlas, then propose the modules and interfaces that close the ranked gaps.
- Run comparative analysis. Compare a client against every mapped competitor and write the debrief, citing the source behind each value.
- Keep the vocabulary straight. The glossary tool gives the agent the ontology, so its output uses the same terms the consultant and the client use.
- Respect the tiers. Private values never leave a workspace the key cannot access, and every private read is in the owner's audit log.
Writes (adding components, values and notes from an agent) and the research agent that drafts a company from public sources are next.