REST and OpenAPI
Use bearer API keys and scoped endpoints under the planned public API domain. Requests are sanitized, logged, rate-limited, and queued before local Atlas work is considered.
OpenAPI guideBuild against Atlas without touching the private runtime.
The Atlas public API is designed for external assistants, GPT Actions, MCP-compatible tools, and partner workflows that need public-safe business routing, website review jobs, playbook recommendations, agent-pack scopes, Project Factory scopes, and proof checklists.
MCP-compatible access
MCP tools wrap the same safe public capabilities. No private tools are exposed through the assistant connector layer.
MCP guideSecurity model
The public API never exposes local files, private memory, Gmail, publishing tools, shell, Docker, Codex, local models, or deployment routes.
Security guideTerms and pricing
API access is gated by terms, scopes, rate limits, usage logging, and planned paid tiers.
API termsQuick answer
What does Build against Atlas without touching the private runtime. help you do?
Developer documentation for Atlas AI public API access, OpenAPI actions, MCP tools, scopes, and safe integration boundaries.
What can Atlas inspect? Atlas can compare the page with its public metadata, internal links, structured data, indexed source records, and available proof. It uses that evidence to separate a confirmed issue from a suggestion, keep the recommendation tied to the page's actual purpose, and avoid inventing business results.
What happens next? Atlas reviews the public context, identifies the smallest useful improvement, and records the evidence. Any send, payment, delivery, production change, or deployment remains behind its specific proof and approval gate.
How is the result checked? The work is compared with the visible page, relevant source records, and a repeatable test. Atlas reports what passed, what remains uncertain, and the next responsible action without claiming guaranteed rankings, leads, or revenue.