Add x402 monetization - let AI agents pay per API call

[sam00101011]

What is this?

x402 is an open protocol that lets AI agents pay for API calls using the HTTP 402 status code. Instead of API keys and billing dashboards, agents pay per call in USDC on Base.

This PR adds the foundation for monetizing okx/agent-trade-kit's API endpoints. We found 10 endpoints in your README that agents could pay to access.

Why agents would pay for okx/agent-trade-kit

Each of these capabilities becomes a pay-per-call endpoint that AI agents discover and pay for automatically:

• Execute complex algo orders like OCO, trailing stops, and conditional trades — agents pay per call instead of needing credentials or rate-limited free tiers
• Access full market data including orderbooks, candles, and funding rates — agents pay per call instead of needing credentials or rate-limited free tiers
• Manage account balances, positions, and audit logs with granular control — agents pay per call instead of needing credentials or rate-limited free tiers
• Automate trading strategies using built-in Grid and DCA bot modules — agents pay per call instead of needing credentials or rate-limited free tiers
• Deploy secure, local-only trading agents via the Model Context Protocol — agents pay per call instead of needing credentials or rate-limited free tiers
• Implement safety-first trading with read-only modes and module filtering — agents pay per call instead of needing credentials or rate-limited free tiers

With x402, every feature above is instantly monetizable. Agents on Claude, Cursor, and any MCP client can discover and pay for access via 402.bot.

What's included

File	Purpose
.well-known/x402.json	Declares your endpoints, pricing, and wallet address - agents and routing networks use this for discovery
x402-middleware-example.ts	Drop-in middleware that returns 402 and verifies payments

How it works

Agent -> calls your API
     <- 402 Payment Required (price: $0.01, wallet, network)
Agent -> signs USDC payment on Base
     -> retries with x-payment header
     <- normal API response

Settlement is instant. No intermediary holds funds. Revenue goes directly to your wallet.

What you'd earn

~$1500/mo projected (10 endpoints x ~150 agent calls/mo x $0.01)

To activate

1. Replace YOUR_WALLET_ADDRESS in .well-known/x402.json with your Base wallet
2. Add the middleware to your server (see x402-middleware-example.ts)
3. Deploy - your API is now discoverable by every agent on the 402.bot routing network

Your endpoints will automatically appear in Claude, Cursor, and any MCP-compatible agent via the 402.bot MCP server.

Live demo

See how okx/agent-trade-kit works on the x402 network ->

Links

• 402.bot - routing oracle and provider marketplace
• llms.txt - machine-readable service catalog
• MCP setup guide
• Provider registration

---

This PR was opened by 402.bot. x402 is an open protocol - you keep 100% of revenue. We just route agents to providers. If this isn't relevant, feel free to close.

[fanqi1909]

Hi @sam00101011 , Thanks for the idea and PR!

x402 is an interesting protocol, but it doesn't fit agent-trade-kit directly — this is an MCP server that runs locally on users' machines with their own OKX API keys, not a public HTTP API.

That said, there's a related effort where x402 could be valuable: the Agent Skills ecosystem.

I'm involved in discussions around a standardized Skills Marketplace (see agentskills/agentskills Discussion #252). One open question is how to create sustainable incentives for skill authors. x402's pay-per-call model could be a great fit here — imagine skill creators earning revenue when agents use their skills.

If you're interested in exploring this direction, I'd suggest joining that discussion. The Skills layer is where monetization makes architectural sense, and x402 could be a strong building block for the ecosystem.

Closing this PR since it doesn't apply to agent-trade-kit, but appreciate you reaching out — and would welcome your input on the Skills side.