Build on VerdictSwarm
Developer docs for the live product surface: how the scan API works, where the proof surfaces live, and how to reuse report links as decision artifacts.
Integrate the verdict gate
Add POST /v2/verdict, ACP, or MCP before your agent buys, lists, alerts, or routes funds.
Proof receipts
Review receipt-style examples that show what was flagged before the collapse.
Web scan and reports
Run the same check in the browser or open report URLs as clean verification links.
API Reference
Live routes, auth modes, curl examples, response schema, and rate limits for the current backend.
Integration Guide
OpenClaw, agent integrations, sample payloads, and product positioning for partner builds.
Plans and Pricing
Current Free and Pro capabilities, plus what is not live yet.
FAQ
Supported chains, scoring, agent behavior, and common implementation questions.
Developer overview
The pre-trade token risk gate for agents that move money: POST /v2/verdict returns an avoid / caution / clear decision, score, and full signal detail. Pay per call via x402 (Base or Solana USDC) or a prepaid API key — no signup, no OAuth.
If you want the fastest path to evaluate the product, call the API reference or run a browser scan with the token your agent is about to touch. Community pilots remain available when you need a human-facing proof workflow first.
Shareable report URLs are public once a scan exists, which makes them useful for dashboards, alerts, public verification links, and moderation workflows even when you are not running scans yourself.
Quick reference
x402
Wallet-native pay lane
Best for agents with a funded USDC wallet. One call returns a 402 challenge; pay on-chain and retry for a usable token decision before execution or posting.
Credits
API-key access
Best for partners who don't speak x402 yet — prepaid credits, predictable auth, higher-volume routing into their own bots and products.
Reports
Cached retrieval
Read already-generated reports through the public report endpoints without re-running the scan workflow, then reuse those URLs as lightweight proof and verification artifacts.