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.
Guided pilot first
Prove the risk desk with web reports before adding Telegram, API, MCP, or ACP.
Proof receipts
Review receipt-style examples that show what was flagged before the collapse.
Web scan and reports
Run the same scan on the site 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 still roadmap-only.
FAQ
Supported chains, scoring, agent behavior, and common implementation questions.
Developer overview
VerdictSwarm currently exposes a public B2A API for pay-per-scan evaluation and a separate API-key surface for partner or internal integrations. The useful output is the same shape across those surfaces: decision, score, top risks, and a report link you can keep or share.
If you want the fastest path to evaluate the product, start with a guided community pilot and web report links, then add Telegram or the API reference once you know the output fits your workflow.
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
Public
B2A pay lane
Best for evaluation and external agents. One call returns a usable token decision before execution or posting.
Partner
API-key access
Best for partners who need predictable auth, sync JSON responses, or 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.