System Atlas
SystemAtlas

optimal_engine_pull

Import the connected cloud Optimal Engine's facts (promoted claims; pending ones too with include_pending) about a company into the workspace as private drafts with provenance optimal_engine, each sourced to its claim on the engine. Fails with 409 for a local engine: use optimal_engine_import then. 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

    Name for a company added by domain

    max 120 chars
  • include_pendingbooleanoptional

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_pull",
  "arguments": {
    "workspace": "acme-builders"
  }
}

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": 1,
  "skipped": 43
}

Over REST

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

Previousoptimal_engine_sendNext optimal_engine_export