Agents that purchase occasional capabilities instead of maintaining subscriptions
x402 APIs
Pay-per-result APIs for autonomous agents.
Discover a capability, inspect its exact terms and pay only when an agent executes it — without creating an account or managing a long-lived API key.
Delx publishes x402-compatible APIs for agents that need a machine result with explicit pricing, schemas and delivery boundaries. A caller receives an HTTP 402 challenge, pays the declared USDC amount on Base 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.
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 and image generation grouped in a portable discovery pack.
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.
- DiscoverResolve the 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.
- Prices shown here are linked to the canonical machine documents that own them.
- The discovery path returns exact endpoints and ready-to-run bounded payment commands.
- Media delivery contracts can expose durable artifact URLs, byte counts and SHA-256 values.
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.
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 the free intent router or a governed job pack, then validate the canonical endpoint, current price and example input before authorizing payment.