Developers

Use through OKX AI (A2MCP)

Service: Chaconne Verify · StockProof Trade Verification (ASP #13803). Free phase returns HTTP 200 with the report; paid phase returns 402 + PAYMENT-REQUIRED (x402 v2) and the Agentic Wallet retries with payment.

curl -X POST https://verify.chaconne.xyz/a2mcp/verify -H "Content-Type: application/json" -d '{
  "ownerAddress": "0xYourWallet",
  "inputAssetKey": "eip155:196:0x4ae46a509f6b1d9056937ba4500cb143933d2dc8",
  "outputAssetKey": "eip155:196:0x9d275685dc284c8eb1c79f6aba7a63dc75ec890a",
  "amountInRaw": "5000000",
  "policyId": "STRICT_LIVE",
  "maxSlippageBps": 50
}'

An empty body returns 400 input_required with a JSON schema and example so an agent can collect parameters.

HTTP API (API key)

GET /v1/assets	Supported assets (chain+contract key, registry version/hash)
GET /v1/policies	Three policies with definition hashes
POST /v1/jobs	Create a fixed-intent task; report v1 computed immediately; idempotent by clientRequestId
GET /v1/jobs/:id	Task state: payment / report versions / entitlement / executions
GET /v1/jobs/:id/report	Report + evidence (402 when unpaid)
POST /v1/jobs/:id/prepare-execution	Re-verify → new version + TradeIntent typed data + certificate + Guard call params (2 per 5 min)
POST /v1/jobs/:id/submissions	Record tx hash; fill confirmed from on-chain receipt

Auth: x-api-key or Authorization: Bearer. Responses are private/no-store.

MCP tools (thin wrapper, coming)

list_supported_assets · get_verification_policy · prepare_verification · purchase_verification · get_verification · prepare_guard_trade · get_execution_status

Tools never take private keys or sign on your behalf; payment budget and transaction signing stay with the user-controlled host / wallet.

Trust boundary (stated plainly)

The service holds one attestation key that signs only VerificationCertificate; it never holds user fund keys or signs payments/trades.
Guard enforces amount, minimum output, recipient, route/selector allowlists, deadline and nonce; it cannot know whether off-chain stock data was correct — that judgement is the attestation service's, bound by evidenceHash.
Admin can pause, rotate the signer, edit allowlists; it cannot move user funds.