Clearance402
Clearance402 docs
Clearance402 verifies paid agent tools before spend: onboard tools, probe trust dimensions, check agent mandates, and export audit evidence.
Onboarding
Get started
Two calm paths — whether you have never touched a wallet or you ship agents for a living.
- 1
Read the 60-second overview
Clearance402 checks a paid tool before your agent pays for it — protocol, price, output, and permissions.
Open docs - 2
Browse verified tools
See live Trust Cards with a simple ALLOW / WARN / BLOCK decision. No wallet needed to look around.
Browse tools - 3
Try a guided run
Watch an end-to-end clearance happen step by step in the agent demo — nothing to install.
Open agent demo
Clearance402
One quiet checkpoint before an agent pays
Clearance402 keeps the complex verification work behind the scenes. Agents send a tool, amount, and mandate; Clearance402 returns a clear decision with the evidence needed to trust or block the payment.
Discover
Find a paid tool and read its Trust Card.
Check
Run live protocol, price, output, and permission checks.
Decide
Return ALLOW, WARN, BLOCK, RETEST, or HUMAN_APPROVAL_REQUIRED.
Tool onboarding
Developers register the endpoint, protocol, advertised price, output schema, and owner contact. Clearance402 immediately runs a probe and shows pending, passed, blocked, or retest states.
clearance402 tools onboard --name "Weather API" --endpoint https://api.example.com/x402 --protocol x402 --price "0.010 USDC"Clearance402
Trust cards
Trust cards show protocol compliance, price integrity, output quality, reliability, permission safety, relayer readiness, drift, and developer readiness.
Open trust-card registry →Workflows
Agent clearance
Agents register an identity and spend mandate, then ask Clearance402 before each payment. The response is short, machine-readable, and safe for automated routing.
Open agent clearance →Payment checks
Clearance402 checks the advertised price against the payment requirement, verifies the challenge/receipt, and blocks payment when the tool or mandate is unsafe.
Audit export
Audit entries record probes, payments, blocks, approvals, evaluations, relays, revokes, and exports. Filter by event type, search by actor or tool, then download CSV evidence.
Open audit log →Permissions
ERC-7715-style spend mandates and revocation checks are evaluated before delegated wallet spend. See agent demo.
Agent tools
Install the agent connector in Cursor, Claude, Gemini, or VS Code so agents can request clearance before payment.
{
"mcpServers": {
"clearance402": {
"command": "npx",
"args": [
"-y",
"@clearance402/mcp-server"
],
"env": {
"CLEARANCE402_ENV_FILE": "C:/Users/YOUR_USER/.clearance402/.env"
}
}
}
}