Find a service
POST /meta-intelligence accepts:
ask is required. price_cap_usd filters candidate prices and network expresses a preference. The same fields work as query parameters on GET; /meta is a compatibility alias. The call costs $0.001 through x402; the current challenge is definitive.
The response separates otto_verified from open_bazaar_candidates. Each row includes source and verification labels, indicative price and pay_url. An Otto row’s call_card includes the method, required inputs and a service-detail link.
Set provider_scope: "otto_only" to return only Otto services. The default is all.
For block evidence, use required_capabilities: ["block_hashes", "source_identity", "observation_timestamps"]. These filter on Otto’s declared output contracts; Bazaar listings without them do not qualify. GET accepts a comma-separated list. The response echoes applied_constraints, and call cards list discovery_capabilities. No permitted match returns 503 without settling the discovery fee. Invalid filters return 400 without settlement.
Chain Status provides mined-head hashes, provisional/nullable pending hashes, safe source identification and observation timestamps.
Choose a candidate and pay that provider directly. Recommendation mode holds no balance and adds no markup to the downstream price. Third-party providers have their own contracts.
Inspect a request for free
GET /service-detail returns the Otto route’s methods, request schema, indicative cost, auth and measured signals. Unknown paths return 404 without a charge. For complete route discovery use OpenAPI and API schemas and examples.
Buy a result with Full Auto
POST /full-auto accepts ask (1 to 1,000 characters) and an optional price_cap_usd. It picks the best-matched Otto service that can answer the ask and returns that service’s data. It answers from Otto services that need no input, or one input it reads from your ask: a ticker, a coin name, a search topic or a domain. A plain question that no service fits goes to the web answer. For a search or a domain lookup, the router sends that topic or domain to the service’s data source. /auto is its compatibility alias.
The 402 quotes one exact price, within price_cap_usd when you send one. You pay Otto once. For one service, the price is that service’s catalogue price plus a $0.01** router fee, and nothing is paid to anyone on your behalf. For a [combined answer](#combined-answers), the price is the sum of its parts plus one **$0.01 router fee. A combined answer can include named outside x402 sellers. Otto pays them itself, and their prices are inside your quote. Pay it with an ordinary exact-price x402 client, like the read example in the HTTP guide.
You are not charged when the answer fails, when a web search finds nothing (404, no_results), when no Otto service fits the ask within your cap (404), or when the quote has changed by the time you pay (409; request a new quote). A successful answer names the service, shows in filled what it read from your ask, and carries a receipt with service_usd, router_fee_usd and charged_usd. Keep it with the settlement transaction hash.
If a paid answer does not reach you, retry the same request with the same signed payment within 15 minutes of first sending it. The router returns the stored answer and does not charge again. A new signature can pay a second time.
GET /stats reports x402Enabled, fullAutoEnabled and refundsEnabled.
Combined answers
Some asks get one answer built from several Otto services. There are two:- Stock due diligence, for asks such as “stock due diligence on NVDA” or “stock deep dive on AAPL”: company fundamentals, analyst ratings, insider trades, the earnings calendar and news for one ticker.
- Market brief, for asks such as “market brief” or “markets today”: the macro regime, market risk, tokenized stock movers, news recaps and FX rates.
bundle (id and name) and gives each Otto service’s data under its route path in parts. Data from an outside seller comes under outside_parts, with the seller’s name and route. A language model writes a short summary from the data in the answer. The summary is not advice: check it against the parts. The receipt lists the price of each part, with outside sellers under outside. If any part or the summary fails, you get an error and you are not charged. Sign the payment valid for at least 120 seconds; standard x402 clients sign it for 300.
Ask for a custom service
POST /customize-auto costs $0.10 in USDC on Base. Use it to ask Otto to change an Otto service for you, or to build a new one. Say what you need: the format, the fields, or how you take in the data, such as a webhook, CSV, a JSON schema or an update frequency.
service: an Otto route path, such as/insider-trades, or"new"for a new service.need: what you need, 1 to 2,000 characters.example: optional, an example request or output, up to 2,000 characters.contact: anemail, a Telegram username intelegram, or both. You must give at least one.
request_id with status: "received". We read every request and reply on the contact you gave, by email from admin@useotto.xyz or on Telegram. We clear your contact details from the stored request 90 days after payment.
You are not charged when the request is not valid (400), or when the same wallet sends a second request within one minute (409). An unpaid request with a body that is not valid gets a free 400, so you never sign for a refusal.
Refunds
POST /feedback is itself a paid route, currently $0.001. To request a refund, send the original settlement transaction hash, a verdict, a reason of at least 50 words, and refund_request: true:
tx_hash and call_id are accepted aliases for original_tx_hash. Take the transaction hash from the original settlement evidence, including X-Payment-Receipt where supplied; a payment challenge is not a receipt.
The program covers qualifying Otto services reached through the Router and Full Auto calls. It does not reimburse third-party Bazaar charges or every direct API purchase. For a service claim, the payer needs an unused matching Router purchase in the receipt record; a standalone Meta fee is not a refundable original call.
An approved claim includes eligible service/router charges and the feedback fee, subject to all limits:
- Only the original payer can receive the refund, never more than its eligible payments to Otto.
- Maximum $0.01 per transaction and 10 claims per wallet in a rolling 24 hours.
- $10 per rolling 24 hours is the global budget, shared across all wallets. Service circuit breakers can also pause claims.
- One original payment can back one refund. A feedback purchase cannot be recycled into another refund claim.
refund.status: "reserved" is approval, not a completed payout. Payout requires the feedback fee to settle from the same payer and the payout service to complete the transfer. An ambiguous payout is held for review rather than blindly retried. Keep the response and check the refund transaction before treating funds as returned. Otto evaluates its own claims; this is a counterparty guarantee, not an independent ruling.
Receipt lookup and outcome reports
ACP proof for past jobs:GET /receipts/v1/{rail}/{chainId}/{contract}/{jobId} returns the on-chain proof of a past ACP job, free. Use rail=acp-v1 or acp-v2, chain 8453 and that rail’s allowlisted contract.
x402 content receipts arrive in the paid response’s PAYMENT-RESPONSE header where generated; this lookup does not support rail=x402.
Outcome reports: POST /report-outcome and POST /report-pattern are free, data-only reports for settled Full Auto calls. They require call_id, success, an EIP-712 signature from the original payer, and optional network and diagnosis. They do not issue refunds. A duplicate returns 409 already_reported.
The signed OutcomeReport fields, in order, are callId: string, network: string, chainId: uint256, kind: string (outcome or pattern) and success: bool. Use domain { name: "Otto X402 Open Router", version: "1", chainId }, with the receipt’s numeric EVM chain ID and exact network string.
Router MCP
https://x402.ottoai.services/mcp exposes otto_meta_intelligence and otto_feedback. Both proxy their paid HTTP routes; this server has no free-call allowance. It is separate from Otto Intel MCP.
Pass the route’s fields plus x_payment after signing its challenge. Keep _meta["com.ottoai/payment-response"]. After a dropped connection, retry the same input and authorization to recover the stored result; reusing it for another input is refused. For Full Auto in MCP, use Otto Intel MCP’s ask_otto.