AXIOM
Log in Sign up

Products

PreviewIn use by Studio and the CLI; customer API tokens are planned

The API Studio runs on.

Everything Studio's web app and the axiom CLI do goes through one REST API under /api/v1, described live in OpenAPI. Opening it to your own integrations, with personal API tokens, is the next step.

Talk to us

Today

  • One API, every client

    The web app and the CLI call the same endpoints. A CLI request is checked exactly like a browser request.

  • Described live in OpenAPI

    The API serves its own OpenAPI description at /api/v1/docs on the Studio cell, and contract tests use it.

  • Versioned path

    Every route lives under /api/v1.

Planned for your integrations.

Designed, not yet built. The SDK and the MCP server are built on this.

  • Personal API tokens with scopes (read, write, stream), an expiry, a label, revocable, ended when the user is deactivated.
  • A complete, tagged customer surface in the OpenAPI description, including metering and capability reads.
  • Semantic versioning from the first SDK release, an API changelog, and Deprecation and Sunset headers when a route retires.
  • An event stream you can resume from a cursor, for live activity outside the browser.
  • Rate limits per token and org, and developer documentation with guides.

Building an integration?

Tell us what you want to connect. It shapes which routes open first.

Talk to us