Agent-native standard
x402
x402 is the HTTP payment protocol for agents. Agents call an endpoint, get a 402 Payment Required challenge, settle on-chain, and the request proceeds. KeeperHub speaks x402 for every workflow execution, so agents pay per call without subscriptions or API keys.
About x402
x402 revives the long-dormant HTTP 402 status code as a payment protocol built for autonomous agents. Authored by Coinbase and Cloudflare, x402 moved under the Linux Foundation on 2026-04-02, with founding members including Visa, Stripe, Google, AWS, Circle, and Mastercard. The protocol is deliberately simple: the server emits a WWW-Authenticate: Payment challenge with settlement terms, the client pays on-chain, and the request retries with an Authorization: Payment header. No new HTTP semantics, no bespoke billing infrastructure.
KeeperHub's integration
Live since 2026-04-13. KeeperHub is registered on x402scan.com as server ID 59aa13ab-2a99-4409-a4e1-8927f4006b29. Every KeeperHub workflow execution endpoint emits spec-compliant 402 challenges that external x402 clients have verified in the wild. No configuration needed on the agent side beyond an x402-capable HTTP client.
Why it matters
How agents use x402 with KeeperHub
Pay per call, not per month
Agents pay at the moment of execution. No subscription, no pre-funded account, no human in the billing loop.
No API keys or accounts
The payment itself is the authorization. An agent does not need to register, get an API key, or manage credentials.
Auto-discovered via x402scan
Agents crawling x402scan.com find KeeperHub's registered server and evaluate the resources and pricing without human coordination.
Works with any HTTP client
Any agent runtime that speaks HTTP with an x402 handler can call KeeperHub. No bespoke SDK required.
Verified in the wild
External x402 clients (unrelated to KeeperHub's code) parse our 402 challenges and settle payments against real workflow executions.
Lowest-friction way to try KeeperHub
No onboarding, no sales call. Your agent points at a KeeperHub endpoint, handles the 402, and executes.
Getting started
Using x402 with KeeperHub
Call a KeeperHub workflow endpoint
Standard HTTP request to the workflow you want to execute.
Receive the 402 challenge
KeeperHub responds with a spec-compliant WWW-Authenticate: Payment header containing the settlement terms.
Settle the payment via your x402 client
The client constructs a payment, submits it on-chain, and retries the request with the Authorization: Payment header.
Workflow executes
KeeperHub verifies the payment, runs the workflow with managed retries, private routing, and audit trail, and returns the result.
References
Further reading
- x402.org - official protocol site
- x402scan.com - ecosystem explorer with KeeperHub registered
- MPP (Machine Payments Protocol) - the complementary pay-per-execution rail
Ready to ship an x402 agent?
Point your agent at a KeeperHub workflow endpoint. Handle the 402. Done.
