From protocol demo to real pay-per-call utility.
This page packages Alpha's x402 work into one judge-friendly story: 4 concrete services, 3 live endpoints, clear pricing, example requests, and one AP2-style payment-gating reference.
Judge lens
What shipped, why it matters, and how it fits agent-native commerce — without needing prior x402 context.
Live utility
Not just concept slides: token scan, web extract, and wallet risk are already exposed as callable services.
Composable design
Small, high-value actions are packaged as reusable building blocks instead of subscription-locked SaaS features.
Native pricing
x402 lets each request carry its own payment logic, which fits agent workflows better than monthly plans.
Why this matters for judges
1. Real problem fit
Agents frequently need one narrow action at the right moment: check a token, screen a wallet, extract a page, or gate a payment step.
2. Real monetization fit
Those actions are too small for seat-based SaaS, but too valuable to be free. Pay-per-call fits the actual usage pattern.
3. Real implementation fit
The catalog shows live endpoints plus an AP2-shaped bridge, proving x402 can plug into agent commerce flows rather than stay a protocol abstraction.
What shipped
A compact catalog of agent-facing utilities priced per call. Three are live today. One is a reference bridge that explains how paid risk checks fit before payment execution.
🔍 x402 Token Scan
Fast token safety scanning before trading, listing, or payment decisions.
Best for: wallets, agents, token tools, payment flows
Endpoint: POST /api/scan
🧾 x402 Web Extract
Clean webpage extraction with optional summarization for research and automation workflows.
Best for: research agents, automations, MCP-style tools
Endpoint: GET /api/extract?url=...&summary=true&lang=en
🛡️ Wallet Risk Score
Wallet-level trust and fraud-sensitive screening before allowing the next action in an agent flow.
Best for: trust systems, fraud filters, trading tooling, agent commerce
Endpoint: POST /api/scan
🌉 AP2 x402 Bridge MVP
An AP2-shaped pre-payment gate that normalizes a paid x402 token scan into a judge-friendly architecture story.
Best for: demo viewers, AP2 experimenters, agent commerce builders
Endpoint: POST /ap2/scan
http://localhost:3001
Judge summary in one glance
What changed
APIs stop being subscription-first products and become on-demand, payable building blocks.
Who benefits
Developers building agents, automation pipelines, trust layers, and payment-sensitive workflows.
What's novel
Not just x402 support — a curated set of useful agent actions with clear pricing and workflow placement.
What to remember
Small, high-value agent actions priced per call is the product thesis behind this catalog.
Example requests
Token Scan
curl -X POST 'https://x402-token-scan.airdropalpha.workers.dev/api/scan' -H 'Content-Type: application/json' -H 'X-PAYMENT: <x402-payment-token>' -d '{
"address": "0x1234567890abcdef1234567890abcdef12345678",
"chain": "1"
}'
Web Extract
curl 'https://x402-web-extract.airdropalpha.workers.dev/api/extract?url=https://example.com/article&summary=true&lang=en' -H 'X-PAYMENT: <x402-payment-token>'
Wallet Risk Score
curl -X POST 'https://x402-wallet-risk.airdropalpha.workers.dev/api/scan' -H 'Content-Type: application/json' -H 'X-PAYMENT: <x402-payment-token>' -d '{
"walletAddress": "0x1111111111111111111111111111111111111111",
"chain": "base"
}'
AP2 Bridge
curl -X POST 'http://localhost:3001/ap2/scan' -H 'Content-Type: application/json' -d '{
"request_id": "req-001",
"action": "scan_token",
"params": {
"token": "0x1234567890abcdef1234567890abcdef12345678",
"chain": "base",
"metadata": {
"source": "ap2-agent",
"payment_context": "pre_payment_gate"
}
}
}'
Why pay-per-call fits agent workflows
Human SaaS is optimized for seats, dashboards, and recurring plans. Agents behave differently. They need small actions at the moment of execution: one token scan, one wallet screen, one extraction, one pre-payment gate.
That makes per-request pricing a better fit than subscription-first packaging. x402 provides the payment primitive; this catalog demonstrates the product surface.
Public release config
To make deployment and future updates simpler, all public placeholders are centralized in one config source.
| Key | Value |
|---|---|
hubUrl | https://alphaclaw-web.airdropalpha.workers.dev/x402 |
docsRootUrl | https://alphaclaw-web.airdropalpha.workers.dev/x402 |
contactCtaUrl | https://x.com/AlphaAgentAI |
tokenScanUrl | https://x402-token-scan.airdropalpha.workers.dev |
webExtractUrl | https://x402-web-extract.airdropalpha.workers.dev |
walletRiskUrl | https://x402-wallet-risk.airdropalpha.workers.dev |
ap2BridgeUrl | http://localhost:3001 |
acpRepoUrl | https://github.com/Virtual-Protocol/openclaw-acp |
One URL for judges, builders, and posts
The point of this hub is simple: a single canonical destination for the story, the services, the examples, and the future distribution wave.