# Anakin: Agent Integration Guide > Machine-readable integration guide for the Anakin Autonomous Business & Organization Engine. Covers Workspaces, Collaborative Multiplayer, Enterprise Vertex, Level-3 Organizational Intelligence, and the Agent Control Plane. Authoritative catalog terms are available at `https://tryanakin.app/pricing`. ## Identity and discovery Anakin publishes multiple complementary discovery mechanisms: - `/auth.md` is the agentic onboarding and self-registration protocol (email OTP authentication + 500 bonus credits). - `/.well-known/ard.json` is the current Agentic Resource Discovery manifest. - `/.well-known/ai-catalog.json` is a compatibility catalog for earlier ARD consumers. - `/.well-known/agent-card.json` is the A2A Agent Card. - `/.well-known/agent.json` is a Cloudflare-style compatibility alias. - `/.well-known/mcp.json` describes the remote MCP server. - `/api/v3/openapi.json` is the typed HTTP API contract. - `/api/v3/resource-model` is the canonical machine-readable Page vocabulary, Page type/content guide, and safe connection contract. Do not infer resource availability from these public documents. They advertise Anakin's platform capabilities only. A specific leased Page is private unless its owner intentionally publishes a separate sanitized card. ## Resource model: Page ### Page: participant-facing interactive surface A **Page** is a durable participant-facing interactive surface hosted on the controller's Anakin workspace. It has a `toolType`, structured `content`, audience, lifecycle, and applicable submission controls. The safe default is `custom_form`; Pages can also present booking, checklist, approval, file, signature, payment-presentation, dashboard, and other supported workspace surfaces. A Page is not an AI subagent, does not execute tasks, does not retain subagent state, and does not provide chat. Use a Page when the intent is form collection, intake, booking, a checklist, approval, file sharing, signature collection, a dashboard, or another controlled participant interaction surface. It is not arbitrary web hosting or a Cloudflare Pages deployment. ### Page types and content Set `toolType` when provisioning or updating a Page and send its content as a JSON object. `custom_form` is the recommended default for a generic request. Its content typically includes `title`, `description`, `fields[]`, `submitButtonText`, and `successMessage`. The live resource model lists every supported type and its content guide: - `custom_form`: `title`, `description`, `fields[]`, `submitButtonText`, `successMessage` - `scheduler`: availability, timezone, slot duration, and booking settings - `checklist`: `title`, `description`, `tasks[]` - `file_sharer` / `file_vault`: file and upload-request metadata - `approval`: request title, description, and details - `e_signature`: document title, signer instructions, and document content - `payment`: invoice/check-out presentation content; it does not settle payments itself - `data_dashboard`: dashboard title and chart data - `order_taker`: catalog/order-intake presentation; any payment or fulfilment provider is configured separately Omit `content` only when the built-in default is acceptable. Retrieve the created Page before relying on its effective content. Some compatibility Page types have application-specific content; do not assume a stable external schema for them. ### Safe method choice 1. Call `list_catalog` or read `/api/v3/catalog` first. The catalog is the authoritative source for live price, network, allowances, and routes. 2. Select **Page** for a participant-facing interactive surface. Read `/api/v3/resource-model` before selecting a non-default Page type. 3. Provision only through standard payment protocols. Let a payment client handle the HTTP 402 challenge; never fabricate `PAYMENT-SIGNATURE`. 4. Store the one-time `at_live_` capability as a secret, then use only `/api/v3/control` or the inbound Anakin MCP server to control its bound resource. 5. Read before write, and destroy only when permanent deletion is intended. Public cards, the catalog, OpenAPI, A2A, and MCP discovery never enumerate actual leases, Pages, knowledge, audiences, submissions, capability tokens, or payer identities. ## Payment and provisioning Provisioning endpoints: - `POST /api/v3/resources/pages` - `POST /api/v3/resources/page/{id}/renew` An unsigned provision request receives HTTP 402 with `PAYMENT-REQUIRED`. Use a compatible payment client configured with a maximum amount that matches the live catalog, then retry with `PAYMENT-SIGNATURE`. A successful provision returns a lease and a one-time plaintext `at_live_` capability token. The payment is settled before the resource is provisioned. Repeating a payment payload is idempotent and does not create duplicate resources. ## Capability tokens `at_live_` tokens are resource scoped. They can have `read`, `write`, `execute`, and `destroy` capabilities. They expire independently and are revoked when a lease expires or a resource is destroyed. Refresh via `POST /api/v3/tokens/refresh` while the lease is eligible. Never send a token to a third-party model, store it in a prompt, or attach it to a public URL. ## MCP Canonical endpoint: `https://tryanakin.app/mcp`. Compatibility endpoint: `https://tryanakin.app/api/mcp`. First call `server/discover`, then read the public MCP resource model with `resources/list` / `resources/read`, or call `get_resource_model` when the host only exposes tools. Call `list_catalog` before a paid operation. The platform also publishes OpenAPI so code-mode or generic HTTP agents can retrieve only the route schemas they need. The public MCP resources are the canonical resource model (`https://tryanakin.app/docs`), live catalog (`https://tryanakin.app/pricing`), and this integration guide. They are public by design and never contain a lease, customer resource, capability token, audience, knowledge file, submission, or payment identity. ## A2A Canonical endpoint: `https://tryanakin.app/a2a`. The public A2A endpoint is a deterministic onboarding agent. It returns live integration guidance and catalog links; it does not receive capabilities, settle payments, or expose leased resources. Use REST or MCP for payment and lease control. ## Authentication and visitors Every human visitor must sign in. `public` means any signed-in user. `private` means only a signed-in workspace owner or approved audience email. This human access policy is separate from a lease controller's `at_live_` machine capability. ## Limits and lifecycle The catalog defines the authoritative values. At publication time, a Page accepts 500 submissions for a 30-day term. Renewal resets term counters. Destroy removes the controlled resource and revokes its capabilities. ## Scoped-Access Operations Studio & Data Plane The **Operations Studio** is Anakin's enterprise data plane, replacing disjointed spreadsheets, legacy CRMs, and rigid external databases with edge-native Cloudflare D1 relational tables: - **Lane-Scoped Access (`lanes = members`)**: Fine-grained RBAC where members are assigned to execution lanes. Access matrices enforce table-level permissions (`can_view`, `can_insert`, `can_update`, `can_delete`). - **Column Redaction & Locks**: Sensitive fields are specified in `hidden_columns` (redacted completely from backend SQL SELECT projections) or `readonly_columns` (locked against mutation, returning HTTP 403 on edit attempts). - **1-Click Member Simulation**: Workspace owners and AI agents inject `X-Preview-Lane-Id` to audit and preview effective table and ERP permissions from any member's perspective. - **Optimistic Concurrency Control**: Mutations require `_expected_version`. Conflicting concurrent edits fail closed with HTTP 409 Conflict to prevent clobbering collaborator changes. - **30-Day Trash & Recovery**: Row deletions apply a soft-delete `deleted_at` timestamp with single-click restore from the Trash Studio and automated 30-day retention purging. - **Autonomous Ledger Loop Closure**: AI agents query and mutate tables via REST/MCP and autonomously post balanced double-entry accounting transactions to the general ledger with immutable SHA-256 hash chains. ## Integration artifacts - [Live catalog](https://tryanakin.app/pricing) - [Resource model](https://tryanakin.app/docs) - [OpenAPI](https://tryanakin.app/api/v3/openapi.json) - [MCP card](https://tryanakin.app/.well-known/mcp.json) - [A2A card](https://tryanakin.app/.well-known/agent-card.json) - [ARD manifest](https://tryanakin.app/.well-known/ard.json)