{"api":{"is_user_authenticated":false,"type":"openapi","url":"https://gateway.apiosk.com/openapi.json"},"auth":{"type":"none"},"contact_email":"support@apiosk.com","description_for_human":"The comparison layer for agentic commerce: every provider that can do a job, priced side by side, paid per request over x402.","description_for_model":"Apiosk is the comparison layer for agentic commerce. Listings are grouped by the job they perform, so an agent that needs a task done gets every provider that can do it in one call, priced side by side, with an input mapping that makes the offers substitutable. Three chained endpoints do the comparing, and none of them charges anything: GET /v1/discover (what can perform this task, with stable candidate ids), GET /v1/compare (how those candidates perform against your requirements, scored 0-100 with the weights and per-dimension contributions that produced the number, so it can be recomputed rather than trusted) and GET /v1/decide (one provider back, the rule that picked it, every rejection with the constraint that caused it, and the runners-up in order). Browse the jobs with GET /v1/capabilities; get the candidates for one, cheapest first, with GET /v1/capabilities/{slug}. The call you pick is paid per request over x402 (HTTP 402 + USDC), with no accounts, API keys or SDKs. Describe a need in plain words at GET /v1/search and get the providers ranked. Price, settlement rail and input compatibility are compared for every offer; measured latency and success rate are published for the listings Apiosk has proxied enough calls of, and explicitly absent for the rest. Result quality is not measured anywhere. Also available: browse every listing with GET /v1/apis (supports search, category, sort, order, limit, offset). Read a per-API agent/MCP manifest with GET /{api_slug}/metadata. Call any API with POST /{api_slug}/execute using a JSON body {operation, input}, or call it transparently with ANY /{api_slug}/{path}. Paid endpoints return HTTP 402 (x402 v2) with a base64 PAYMENT-REQUIRED header and JSON body until a valid payment proof is supplied via the PAYMENT-SIGNATURE header (the legacy X-Payment header is also accepted for x402 v1); settlement is USDC on Base. No accounts, API keys, or SDKs.","legal_info_url":"https://apiosk.com","logo_url":"https://gateway.apiosk.com/logo.png","name_for_human":"Apiosk Gateway","name_for_model":"apiosk_gateway","schema_version":"v1"}