Overview

Acme gives every organization a REST API under /v1, an MCP server for AI agents, and a dashboard for the team. The resource it ships with is called items: a name, a description and one file.

• Scoped keys. Each API key carries the access it needs: read, or read and write, and the MCP server or not.
• Credits. A write costs credits. The free plan comes with monthly credits; a paid plan or a credit pack adds more.
• Safe retries. A write sent with an Idempotency-Key header is applied and charged once, however many times it is retried.
• Server-side only. Keys are secret: call the API from your server, never from a browser.

The API in one request

curl -sS "https://example.com/v1/items" \
  -H "Authorization: Bearer $ACME_API_KEY"

{
  "items": [
    {
      "id": "01a17890-0cff-7afb-b802-90296dbb6a9b",
      "name": "First item",
      "description": "",
      "status": "active",
      "moderation": "approved",
      "file": null
    }
  ],
  "next": null
}

Where to go next

• Quickstart: from an account to your first call.
• API conventions: errors, limits, retries and pages, for every route.
• The items API: every route, its fields and its errors.
• Keys and scopes: what each access allows.
• Credits and billing: what a call costs, plans and packs.
• MCP server: connect an AI agent.