Agents that purchase occasional capabilities instead of maintaining subscriptions
x402 APIs
Pay-per-result APIs for autonomous agents.
Discover any of 500 production-ready x402 products, inspect exact terms, and pay only when an agent executes — no account, no long-lived API key.
Delx Commerce publishes a governed portfolio of 500 production-ready x402 APIs (USDC on Base) for autonomous agents. A caller discovers via OpenAPI, ARD catalog, Bazaar or intent router, receives an HTTP 402 challenge, pays the declared amount and retries the same request with proof of payment.
Outcome
A precise job, not a generic promise.
Replace separate subscriptions and vendor onboarding with a governed purchase path that an autonomous agent can inspect before spending.
Workflows that must inspect price and schema before authorization
Teams that need attribution and a reproducible delivery trail
Live capability map
Start from a governed contract.
Each capability links to the property that owns its current terms. Inspect that source immediately before execution.
500-product OpenAPI x402
Full machine catalog of paid paths, schemas, prices and examples on Base USDC.
Inspect the contract →Website content extraction
Clean readable text or a structured site report from a caller-supplied public URL.
Inspect the contract →Agent micro-utilities
DNS, QR, FX reference data, local text/math utils and more in portable packs.
Inspect the contract →Speech generation
OpenAI-shaped input compatibility with a durable WAV delivery URL and SHA-256 in the result contract.
Inspect the contract →Execution
Readable by a person. Runnable by an agent.
The same path can be evaluated manually, embedded in a toolchain or followed autonomously within a bounded authorization.
- DiscoverUse ARD ai-catalog, intent router, a job pack or the complete paid OpenAPI document.
- AuthorizeValidate the exact price, network, input schema and maximum amount before payment.
- ExecuteRead the 402 challenge, pay the declared amount and retry the unchanged request.
- VerifyRetain the response, attribution source and service-specific delivery evidence.
AgentCash · paid website extraction
npx agentcash@latest fetch \
https://api.delx.ai/api/v1/x402/page-extract \
-m POST \
-H 'content-type: application/json' \
-H 'x-delx-source: delx-ai-x402-page' \
--payment-network base --max-amount 0.01 \
-b '{"url":"https://example.com","timeout":8}'Evidence
What can be verified.
- Live portfolio status=ready with 500 governed products and margin floor ≥25%.
- Canonical machine docs: openapi.x402.json, x402-portfolio.json, commerce ARD ai-catalog.json.
- Discovery returns exact endpoints and bounded AgentCash commands; media contracts expose durable URLs and SHA-256.
Boundaries
What is not being claimed.
- A listed price applies only to the linked operation and can change at its canonical source.
- A discovery pack is navigation, not a bundle purchase or a claim that every capability is equivalent.
- Delx does not substitute an unrelated paid product when the intent router has no matching offer.
Direct answers
Questions agents and evaluators ask.
Visible answers mirror the structured data on this page.
What is an x402 pay-per-result API?
It is an HTTP service that communicates payment requirements through a 402 response. The caller authorizes the declared amount and retries the request with payment proof before receiving the result.
How large is the Delx x402 catalog?
The governed live portfolio lists 500 production-ready paid products with status=ready. Agents should treat openapi.x402.json and x402-portfolio.json as the machine truth.
Do Delx x402 APIs require an account or API key?
The public x402 purchase path is designed for accountless, per-request payment. Individual services still publish their own input, policy and delivery boundaries.
How should an agent choose a Delx capability?
Start with ARD ai-catalog, the free intent router or a governed job pack, then validate the canonical endpoint, current price and example input before authorizing payment.