System Atlas
SystemAtlas
Connect your agent · about 5 minutes

Map your company from the inside

Your coding agent reads the docs, tools and records on your machine and maps your company onto the baseline: people, process, software, data, decisions. Everything it uploads is private until you choose otherwise.

  1. Create a free account or sign in

    Step 1 of 4
    What you need
    A work email. No card, no install.
    What happens next
    A private workspace is ready for your company's map; only you can open it.

  2. Create a key for this agent

    After step 1

    A key reads and writes exactly what you can. Revoke it any time in Settings.

    What you need
    To be signed in. One key per agent or machine makes it easy to revoke one later.
    What happens next
    The key is filled into the setup below and into the prompt, so you copy nothing by hand.

  3. Add System Atlas to your agent

    After step 2
    ~/.codex/config.tomlAdd to ~/.codex/config.toml.
    [mcp_servers.systematlas]url = "https://systematlas.org/mcp"http_headers = { "Authorization" = "Bearer sa_YOUR_KEY" }

    Not connecting in Codex? Restart Codex after saving config.toml. One TOML error stops every server in the file from loading.

    What you need
    The agent installed on a machine that can see your company's docs, repos and tools.
    What happens next
    The agent lists System Atlas among its tools. Nothing is read or uploaded until you give it the prompt.

  4. Hand it the prompt, then check

    After step 2

    Paste or drag the prompt into the agent. It creates your workspace, reads the mapping guide, walks your repos, docs and tools (structure only, no secrets or personal data) and uploads the map in batches.

    What you need
    The agent open in your company's main folder, with System Atlas added.
    What happens next
    The count of uploaded components climbs here as it works; open the map when it is done.
Optimal Engine

Exchange maps with your Optimal Engine

Connect a workspace to an Optimal Engine in the workspace's Settings. Sending puts each component (with its values) and each flow into the engine as evidence and one pending claim, through its POST /api/ingest, so it enters the engine's review before it becomes a fact. Pulling reads the engine's facts (GET /api/memory-core/claim-review, promoted claims) and imports those that name the company or its domain as private drafts with provenance Optimal Engine, each linked to its claim. Every exchange is in the workspace's activity log.

MIOSA cloud, or any public engine

Paste the engine's address and an engine key (oe_…, scopes read and write). System Atlas checks it with GET /api/auth/whoami, keeps it encrypted and shows only its last four characters. Send, pull, and sending after each research run then happen from the server, over https only.

An engine on your machine

System Atlas's server cannot reach your localhost, so the exchange runs from your side. In Settings choose Local: the settings page then calls the engine from your browser and keeps any key in the tab. That works when the engine runs without a required key, the local default; an engine with OPTIMAL_AUTH_REQUIRED=true refuses the browser's preflight request, so use your agent instead.

Let your agent carry it

With the System Atlas MCP connected (steps above) and your engine reachable from the agent (its own MCP server or plain HTTP with your engine key), ask the agent to:

  1. Send: call optimal_engine_export with the workspace slug, then POST each returned document as the JSON body of <engine>/api/ingest.
  2. Pull: GET <engine>/api/memory-core/claim-review?workspace=<engine workspace>&lifecycle_state=promoted and pass its claims to optimal_engine_import with the company's slug or domain.
  3. With a cloud engine connected, optimal_engine_send and optimal_engine_pull do both from the server. The HTTP API has the same four under /api/v1/workspaces/<slug>/optimal-engine/ (send, pull, import, and GET export).