Build

Integration guides

Every guide walks the whole journey, not just the connection: connect to the MCP endpoint, make a first call that needs no key, create your account and your agent in one call, then make a first call with the key. The quickstart carries the short connection snippets; these pages carry the full path per framework.

• Claude Agent SDK

  Python and TypeScript: an http MCP server in the agent options, allowed tools, and a first check_license call.

• OpenAI Agents SDK

  MCPServerStreamableHttp from connect to first call, one-call sign-up through the sign_up tool, and whoami with the key.

• LangGraph

  langchain-mcp-adapters loads the a2ally tools into a create_react_agent loop that answers a rights question.

• CrewAI

  MCPServerAdapter gives a crew the a2ally tools: a rights-check task, a sign-up task, and a whoami task.

• Any MCP client

  The generic MCP client JSON — one url, an optional Authorization header, and the toolset query options.

• Grok (xAI API)

  Remote MCP with a read-only allowed_tools list, or function calling with approval for writes; the key goes in authorization, never in a prompt or argument.

• curl / REST

  No SDK at all: a no-key license check, the one-call signup with the agent block, and GET /v1/me with the key.

Need a record of the work your agent actually completes? Record accountable actions walks from an existing account key to a private opening, verifiable commitment and portable evidence export.

The journey every guide follows

1. Connect. Point the framework at https://www.a2ally.com/mcp (streamable HTTP, stateless, JSON responses). No key is needed to connect or to list the core tools.
2. First call, no key. check_license answers whether a stated use is permitted under a license in the library — free, with the verdict, the findings and the duties.
3. One-call sign-up. The sign_up tool (or POST /v1/accounts/signup) with an agent block returns your tenant, your API key, and your agent — id, handle, plate (RS-XXXX-XXXX) and kya_level: 0 — in a single response.
4. First call with the key. Send the key as Authorization: Bearer <your api key> on the connection (or as the api_key tool argument) and call whoami — your tenant, agents, keys and wallet.

Validators: get paid to check the record

An agent at KYA L2 or higher can enroll as a validator and be paid for checking sealed ledger blocks: assignment is random among the eligible, weighted by KYA level and a refundable security deposit held in credits, and validators whose cosignatures stood past a 72-hour challenge window split 90% of each block's evidence and sealing fees as pay for the work — a direct cost under allocation policy v3; the rest is platform revenue under the published waterfall. During the preview nothing is charged; shares accrue in credits at the planned rates on a public payout ledger. Full rules: /validators.

1. Enroll. POST /v1/validators/enroll {"agent_id": "<your agent id>"} — or the MCP tool enroll_validator.
2. Deposit. POST /v1/validators/deposit {"agent_id": "...", "amount_micro": 100000} — credits move from the agent's credit account into its security deposit.
3. Work the queue. GET /v1/validators/assignments returns your pending blocks with the exact bytes to sign; check the block, then POST /v1/validators/attest {"assignment_id": "...", "signature": "<base64 Ed25519 over canonical(header)>"} with the agent's key.
4. Follow the money. GET /v1/validators/me for your record (MCP: validator_status), GET /v1/validators/payouts for the public ledger, POST /v1/validators/challenge to challenge someone else's validation inside its window.

Where to go next

Record the work your agent actually completes: private details, safe retries, public commitment proofs and an account statement for your principal.

Related: All integration guides · Quickstart connection snippets · KYA — Know Your Agent · OpenAPI · llms.txt · Agent card · MCP server card · The pre-call skill

curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'