API terms

Atlas API access is scoped, logged, and proof-gated.

These working terms define the safety boundary for external AI systems, developers, and partners. Legal review is required before paid API access is sold at scale.

  1. What Atlas API is. A public-safe gateway for routing, public website review jobs, playbook recommendations, agent-pack scopes, Project Factory scopes, and proof checklists.
  2. Account registration. API users need an approved account, accepted terms, assigned scopes, and active plan status.
  3. API keys and security. API keys must be protected. Atlas stores only hashed key material.
  4. Approved use. Use documented endpoints for public-safe business workflow guidance.
  5. Prohibited use. Do not request private files, secrets, credentials, unauthorized customer data, local-network targets, shell execution, publishing, sending, deployment, or payment actions.
  6. AI system usage rules. AI systems must follow granted scopes, identify the integration, and keep user-facing claims within the returned evidence.
  7. No direct local-system access. The API is not a tunnel into Atlas local infrastructure or the local operator UI.
  8. No G: drive, private memory, Gmail, publishing, or execution access. External systems may not access private drives, private memory, Gmail, publishing tools, code execution, Docker, local model services, or non-public endpoints.
  9. Billing and usage limits. Plans, monthly limits, and overage rules apply when paid API access is enabled.
  10. Rate limits. Requests may be throttled, blocked, or queued according to plan and system health.
  11. Data handling. Atlas stores job metadata, safe summaries, audit logs, and sanitized results; raw secrets and credential material are not allowed in requests.
  12. Logs and audit records. Requests, scopes, decisions, and blocked attempts may be logged for safety and billing.
  13. Retention policy. Retention windows may vary by plan and legal requirements.
  14. No guarantee of ranking, citations, revenue, or business outcome. Atlas provides review, guidance, and workflow support, not guaranteed rankings, leads, sales, or citations.
  15. Human review and proof gates. External actions remain gated by review, proof, and approval.
  16. Suspension and termination. Misuse, bypass attempts, unpaid status, or policy violations can disable access.
  17. Changes to API or terms. Atlas may change endpoints, scopes, plans, or terms with notice where practical.
  18. Support boundaries. Support covers documented public API behavior, not private local runtime access.
  19. Liability limits. Use is subject to plan, terms, and legal limits.
  20. Contact. Request access or support through Atlas public intake.

Protection language: External systems may not attempt to access, infer, enumerate, scan, or bypass Atlas local infrastructure, private memory, local file systems, developer tools, credentials, Gmail, publishing systems, Docker, local model services, or any non-public endpoint.

Atlas API access is limited to documented endpoints and granted scopes. Any attempt to bypass the API layer, manipulate hidden parameters, request local file paths, request secrets, or trigger unauthorized execution may result in immediate suspension.