System Atlas
SystemAtlas

optimal_engine_import

For an Optimal Engine you run locally: pass the claims array from GET <engine>/api/memory-core/claim-review?workspace=<engine workspace>&lifecycle_state=promoted (up to 1000). Claims about the company land as drafts with provenance optimal_engine; others, rejected ones and this workspace's own sends are skipped. Needs an editor key.

Write · editor keyMCP tool

Parameters

  • workspacestringrequired

    Workspace slug

  • companystringoptional

    Company slug; omit for every company (send, export) or the client (pull, import). For pull and import a domain adds the company once.

    max 200 chars
  • namestringoptional
    max 120 chars
  • claimsobject[]required
    max 1000 items

Example call

Agents call tools by name; you rarely write this by hand. It is here so you can test the server from a shell or your own code.

{
  "name": "optimal_engine_import",
  "arguments": {
    "workspace": "acme-builders",
    "claims": []
  }
}

Response

The result is one text content block holding this JSON (abbreviated here). Errors come back with isError: true and a message such as Error 401: … or Invalid input: ….

Response
{
  "imported": 0,
  "skipped": 0
}

Over REST

The same call without MCP: POST/api/v1/workspaces/:slug/optimal-engine/import

Previousoptimal_engine_exportNext registry_guide