Otto X402 Router

The Otto X402 Router answers a question every x402 agent hits: which endpoint do I call for this? Send one request describing what you need, and the Router returns the best-matching x402 services — ranked across both Otto’s own verified catalog and the live, public CDP Bazaar — each with its real price and a ready-to-call pay_url. Otto only recommends. You pay each service directly at its pay_url. There is no prepay wallet, no held balance, and zero markup on the downstream services. Base URL: https://x402.ottoai.services The Router is canonical at x402.ottoai.services/meta-intelligence — the same host as every other Otto x402 service. (Under the hood it is served by Otto’s open-router service, fronted by the x402 router as a transparent pass-through.) Pricing: $0.001 per call (USDC on Base) — a flat router fee, never a markup on the services it recommends. Custody: Meta Intelligence is non-custodial — it only recommends; you pay each service directly. Otto never holds your funds.

How it works

Every query returns two clearly-labeled candidate pools — never blended into one anonymous ranked list:

Pool	Source	Verification
`otto_verified`	Otto’s own published x402 endpoints (owned, evidence-backed)	`verified`
`open_bazaar_candidates`	Live CDP Bazaar search (free public marketplace, per-ask)	`unverified`

Every candidate row carries blunt source and verification labels so you always know where a recommendation came from.

quality_score now reflects live-status + on-chain (x402scan) volume where measured — candidates are ranked by liveness and real on-chain usage, never fabricated ratings. It stays null for a candidate until it has been probed/measured, and uptime_pct is only populated where directly observed. Otto never fabricates quality signals.

Endpoints

`POST /meta-intelligence` — Meta Intelligence

The core product. Returns top Otto-verified endpoints plus live CDP Bazaar candidates for your ask.

POST /meta remains as a back-compat alias of /meta-intelligence.

Request

{
  "ask": "real-time crypto news with sentiment",
  "price_cap_usd": 0.05,
  "network": "eip155:8453"
}

Field	Type	Required	Description
`ask`	string	✅	Natural-language description of the data or service you need
`price_cap_usd`	number	—	Filter to candidates at or below this price (USD)
`network`	string	—	Prefer candidates on this CAIP-2 network (e.g. `eip155:8453` for Base)

Response

{
  "ask": "crypto news for bitcoin",
  "classification": {
    "category": "News & Sentiment",
    "intent": "get latest crypto news for bitcoin",
    "keywords": ["crypto news", "bitcoin", "latest"],
    "llm_degraded": false
  },
  "otto_verified": [
    {
      "name": "Crypto News",
      "provider": "Otto AI",
      "price_usd": 0.001,
      "currency": "USDC",
      "network": "eip155:8453",
      "verification": "verified",
      "source": "ours",
      "quality_score": null,
      "uptime_pct": null,
      "sample_output": null,
      "pay_url": "https://x402.ottoai.services/crypto-news",
      "relevance": 0.333,
      "call_card": {
        "method": "GET",
        "allowed_methods": ["GET"],
        "required": [],
        "price_usd": 0.001,
        "currency": "USDC",
        "service_detail_url": "https://x402.ottoai.services/service-detail?path=/crypto-news"
      }
    }
  ],
  "open_bazaar_candidates": [
    {
      "name": "apitoll",
      "provider": "news.apitoll.cloud",
      "price_usd": 0.001,
      "currency": "USD Coin",
      "network": "eip155:8453",
      "verification": "unverified",
      "source": "cdp-bazaar",
      "quality_score": null,
      "uptime_pct": null,
      "sample_output": { "articles": [] },
      "pay_url": "..."
    }
  ]
}

Example

curl -s -X POST https://x402.ottoai.services/meta-intelligence \
  -H 'content-type: application/json' \
  -d '{"ask":"crypto news for bitcoin","price_cap_usd":0.05}'

Then pick a candidate and pay it directly at its pay_url using any x402-compatible wallet or agent — exactly as you would call any other Otto endpoint.

`GET /service-detail` — Service detail lookup (free)

Look up the full Otto catalog record for any one x402 path: request schema, cost, auth, usage patterns, and a settlement note. Free — never charged. Query parameter: path (required) — the catalog path, e.g. ?path=/token-security.

curl -s "https://x402.ottoai.services/service-detail?path=/crypto-news"

Returns a ServiceMap object (fields below) or a 404 with you_were_not_charged: true for an unknown path.

Field	Description
`path`	The catalog path
`service_name`	Human name
`method` / `allowed_methods`	HTTP verb(s)
`category` / `class` / `summary`	Service taxonomy
`schema.params` / `schema.body`	Request shape (from catalog, not output-measured)
`cost.price_usd` / `cost.pricing_mode`	Indicative price — live 402 header is the source of truth
`cost.settlement_note`	”Settlement is on success only: a 4xx/5xx is not settled”
`auth`	`{ type: "x402" }`
`signals` / `patterns`	Applicable quality signals and usage patterns
`measured`	`quality_score`, `uptime_pct` — `null` until crawled, never fabricated
`you_were_not_charged`	Always `true` on this endpoint

The call_card on each otto_verified row in /meta-intelligence is a compact subset of this: method, allowed_methods, required, price_usd, currency, and a service_detail_url pointing here. Use /service-detail for the full schema.

`GET /receipts/v1/{rail}/{chainId}/{contract}/{jobId}` — ACP receipt lookup (free)

Reconstruct the on-chain proof metadata for an Otto ACP job, straight from Base. Read-only, free — never charged, and it never returns raw job content — only the derived proof: the job locator, and (for ACP v2) the deliverable commitment where one exists on chain. Path parameters

Part	Values
`rail`	`acp-v1` or `acp-v2`
`chainId`	`8453` (Base)
`contract`	the allowlisted ACP job contract for that rail
`jobId`	the job id (decimal)

Optional query: submitTx — the hash of the ACP v2 submit() transaction. The deliverable hash is committed on chain only in that transaction’s calldata (the getJob view does not expose it), so pass submitTx and the endpoint decodes the commitment in a single bounded call. Omit it and the endpoint returns the hash as null plus the exact event signature and topics so you can read it yourself — it never scans an unbounded log range, and never reports a hash it did not read.

curl -s "https://x402.ottoai.services/receipts/v1/acp-v2/8453/0x238e541bfefd82238730d00a2208e5497f1832e0/67965"

The rails are not equally verifiable, and the response says which:

ACP v2 commits keccak256 of the deliverable on chain in submit(). railCommitsArtifactHash is true; supply submitTx and chainVerifiable becomes true with the real evidenceHash.
ACP v1 puts no copy of the deliverable, and no hash of it, on chain — delivery is off-chain with only a URL-pointer memo. So railCommitsArtifactHash and chainVerifiable are always false, and evidenceHash is always null. What the chain does prove — the job’s existence, parties, and phase — is returned in locator. An L6 receipt on this rail is an Otto attestation, not a chain commitment, and this endpoint will not pretend otherwise.

In every case the underlying chain is authoritative; this endpoint is a convenience over it.

x402 receipts need no lookup. The signed otto-content-receipt is delivered in-band, in the PAYMENT-RESPONSE header of the paid call itself. Calling this endpoint with rail=x402 returns a 400 pointing you back to that header.

`GET /stats` — Registry counts

Returns the verified + Bazaar registry counts and the current arm state (which pillars are enabled). The counts below are illustrative — the live values are whatever GET /stats returns at call time.

{
  "registry": { "verified": 53, "bazaar": 33 },
  "x402Enabled": true,
  "fullAutoEnabled": true,
  "refundsEnabled": true
}

`POST /full-auto` — Full Auto (live)

The hands-off pillar. The Router picks the best-matched service and pays it on your behalf at-cost plus a $0.001 router fee, using an upto cap — no prepay, no standing balance, per-call pass-through — then returns the data directly. Live and armed.

{
  "ask": "real-time crypto news with sentiment",
  "price_cap_usd": 0.05
}

price_cap_usd is a hard upto ceiling on the total spend for the call. Every Full Auto charge is backed by the money-back guarantee below.

`POST /feedback` — Feedback & Refunds (live)

The money-back guarantee. Paid a recommended Otto service (or a Full Auto charge) you didn’t like? Send feedback with a ≥50-word reason and Otto refunds the service fee + the Meta/router fee (or the whole Full Auto charge). An approved refund returns only to the original payer and never more than you actually paid Otto, capped at $0.01 per transaction, up to 10× per wallet per day. The $10/day figure is a global system budget across all wallets — not your per-user limit. Scope (honest): the guarantee covers Otto’s own recommended services + Full Auto; it does not cover third-party CDP Bazaar picks (there is no receipt to verify those).

`POST /report-outcome` and `POST /report-pattern` — Receipt-gated outcome loop (free)

After a Full Auto call settles, the payer can report the outcome back to Otto. This is a data-only, zero-payout loop — no refund is issued here (use /feedback for refunds). Free — never charged. Both endpoints require EIP-712 payer proof: the signature must be from the wallet that paid for the rated Full Auto call. Request body

Field	Type	Required	Description
`call_id`	string	✅	The `0x…` settlement tx hash of the Full Auto call being rated
`success`	boolean	✅	Whether the returned data was useful
`signature`	string	✅	65-byte EIP-712 signature from the paying wallet
`network`	string	—	CAIP-2 network of the call (validated against the receipt; defaults to Base)
`diagnosis`	string	—	Free-text description of what was wrong (stored internally, never echoed)

Response

{ "recorded": true, "kind": "outcome" }

v1 scope: only Full Auto calls (/full-auto / /auto) are reportable — /meta-intelligence calls are excluded (no reconcilable ground truth). Report each call_id once; a duplicate returns 409 already_reported. The endpoint is rate-limited per IP.

`POST /mcp` — First-party MCP server (metered)

A JSON-RPC 2.0 endpoint that exposes two Otto tools over MCP: otto_meta_intelligence and otto_feedback. Both tools proxy to the same metered HTTP routes — there is no free tier; omit x_payment on the first call to receive the 402 challenge, then retry with a signed payment. Tools

Tool	Route proxied	Price
`otto_meta_intelligence`	`POST /meta-intelligence`	$0.001 via x402
`otto_feedback`	`POST /feedback`	$0.001 via x402

Each tool accepts the same fields as its HTTP counterpart plus an x_payment string (the Base64 X-Payment header value for the x402 challenge). otto_full_auto is not included in v1. MCP endpoint URL: https://x402.ottoai.services/mcp

Discovery

Landing page — interactive endpoint explorer
LLM docs — machine-readable catalog (includes the Router)
Discovery doc — x402scan-compatible

Honesty constraints

Constraint	Guarantee
No held balance	Meta Intelligence never takes custody — you pay each service directly
Zero markup	The Router fee is flat $0.001; downstream services are passed through at their real price
Measured quality only	`quality_score` reflects liveness + on-chain (x402scan) volume where measured; `null` until a candidate is probed — never fabricated
Blunt source labels	Every candidate is tagged `ours` / `cdp-bazaar` and `verified` / `unverified`
Money-back guarantee	Don’t like a recommended Otto service or a Full Auto charge? Refund the fee, capped $0.01/tx, up to 10×/wallet/day (≥50-word reason, original payer only). Covers Otto’s own services + Full Auto, not third-party Bazaar picks

Start Here

Otto DApp

Intelligence Guides

Access & Routing

ACP Agent Swarm

API Storefronts

Token & Rewards

Reference

Help, Safety & Legal

How it works

Endpoints

`POST /meta-intelligence` — Meta Intelligence

`GET /service-detail` — Service detail lookup (free)

`GET /receipts/v1/{rail}/{chainId}/{contract}/{jobId}` — ACP receipt lookup (free)

`GET /stats` — Registry counts

`POST /full-auto` — Full Auto (live)

`POST /feedback` — Feedback & Refunds (live)

`POST /report-outcome` and `POST /report-pattern` — Receipt-gated outcome loop (free)

`POST /mcp` — First-party MCP server (metered)

Discovery

Honesty constraints

​How it works

​Endpoints

​POST /meta-intelligence — Meta Intelligence

​GET /service-detail — Service detail lookup (free)

​GET /receipts/v1/{rail}/{chainId}/{contract}/{jobId} — ACP receipt lookup (free)

​GET /stats — Registry counts

​POST /full-auto — Full Auto (live)

​POST /feedback — Feedback & Refunds (live)

​POST /report-outcome and POST /report-pattern — Receipt-gated outcome loop (free)

​POST /mcp — First-party MCP server (metered)

​Discovery

​Honesty constraints

How it works

Endpoints

`POST /meta-intelligence` — Meta Intelligence

`GET /service-detail` — Service detail lookup (free)

`GET /receipts/v1/{rail}/{chainId}/{contract}/{jobId}` — ACP receipt lookup (free)

`GET /stats` — Registry counts

`POST /full-auto` — Full Auto (live)

`POST /feedback` — Feedback & Refunds (live)

`POST /report-outcome` and `POST /report-pattern` — Receipt-gated outcome loop (free)

`POST /mcp` — First-party MCP server (metered)

Discovery

Honesty constraints