API Terms

The JSON API at /api/v1, the MCP server at /mcp, the systatlas CLI, and the signed download links at /api/data/link. These terms add to the Terms of Service and the Data Licence; the Data Licence decides what you may do with what the API returns.

• Keys are created in Settings, on your account, and are shown once. Creating a key asks you to accept the current Terms, Data Licence and these API Terms, and records that you did.
• A key can be narrowed to one workspace, to the public registry, or to reads. It acts as you: what it can read and write is what your account can.
• Keep keys out of public code, client-side apps and shared files. Revoke a key the moment it may have leaked; we may revoke keys we find exposed.
• Do not share a key outside your organization, sell access through it, or use several accounts to get around a plan's limits.

Each plan includes a monthly number of API and MCP calls, shown on /pricing. Download links are short-lived, rate-limited per account (and per address when signed out) and each names one file. Responses over the size cap are refused with a message saying how to narrow or page the request. We may slow or stop traffic that harms the service for others.

Every API and MCP response carries a licence object with your tier, the Data Licence version and its URL. Keep it with data you store, and do not strip it from data you pass on within your licence.

You may connect an AI agent with your key. You are responsible for what the agent reads and writes with it, including uploads to your workspace and contributions to the registry, as if you had made them yourself. Answering your own questions with an agent is normal use; training a model on the responses needs an AI Training Licence.

We keep the API stable and announce breaking changes in the changelog before they ship, but it is provided as is and without an uptime commitment unless an Enterprise contract says otherwise. Questions: hello@systematlas.org.