Clearance402

Clearance402 is the trust, testing, and safety layer for autonomous agent payments over x402 and MCP on Base Sepolia.

Agents can pay for APIs—but should they? Clearance402 answers that before USDC moves:

• Live x402 probes (402 challenge → settlement → response)

• Trust cards with scores: protocol, price, output, drift, permissions

• Venice AI output evaluation (quality, drift, risk)

• ERC-7715 spend mandates via MetaMask Smart Accounts Kit (caps, domains, expiry, revoke)

• ERC-7710 redelegation path for buyer agents (A2A lab)

• Pay-if-cleared: clearance check → server or session x402 payment

• Wallet-scoped persistence (Postgres on Vercel) — same account on any device

• Full console: dashboard, tool registry, onboarding, audit, payment lab, permissions, agent clearance, A2A lab

• Agent surface: @clearance402/sdk, @clearance402/cli, @clearance402/mcp-server (9 MCP tools)

Target: MetaMask Smart Accounts Kit × 1Shot × Venice AI Dev Cook Off — Best x402 + ERC-7710, Best Agent, Best A2A, Best Venice AI.

Week 1: Core clearance engine — live x402 probe, check decision (ALLOW/WARN/BLOCK/RETEST/HUMAN_APPROVAL), Venice eval API, audit log, builtin tool registry.

Week 2: MetaMask integration — ERC-7715 permission grant/revoke, session smart account, ERC-7710 redelegation in A2A lab, pay-if-cleared flow.

Week 3: Production platform — wallet-scoped Postgres persistence, account/session APIs, React Query UI (no localStorage), server-side x402 execute, SDK/CLI/MCP packages, Vercel deploy, E2E smoke test (18 API checks).

Honest limits: 1Shot mainnet relayer track not targeted (Base Sepolia testnet only). Venice x402 endpoint migrated to /api/v1 — updating builtin probe URL in progress.

Pre-seed / bootstrapped — hackathon MVP only. No fundraising round closed. Open to grants and ecosystem partners (MetaMask, Venice, x402) after Cook Off judging.