Build on WalletGuard
Everything you need to audit smart contracts from code, CI, AI agents, or your editor. Pick a path below, or start with the methodology to understand what the engine actually does.
Getting Started
The quickest route depends on what you are building.
- 1Audit a live contract. Paste an address at /audit or call the API with a chain id and address.
- 2Audit source in CI. Use the source-direct API or the GitHub Action to fail PRs on critical findings.
- 3Audit from your editor. Connect Claude Code or Cursor via MCP and call security tools without leaving your workflow.
- 4Audit from an AI agent. Use the x402 protocol to pay per request in USDC. No accounts, no keys.
Browse the docs
Methodology
How we auditHow the audit engine works. Agent roster, scoring algorithm, prompt transparency, and on-chain verification.
API Reference
RESTBase URL, authentication options, response shapes, rate limits, and links to every endpoint.
x402 Protocol
PaymentsPay-per-audit with USDC on Base. No accounts, no API keys. Machine-native commerce for AI agents.
Source-Direct API
SourceSubmit Solidity source directly (no on-chain fetch). Ideal for CI pipelines and local builds.
MCP Integration
Claude / CursorWire WalletGuard into Claude Code and Cursor. Six security tools, one Model Context Protocol server.
GitHub Action
CIDrop-in workflow that audits changed .sol files on every pull request. Fail the build on critical findings.
Verification
EIP-712 / EASEvery report is signed with EIP-712 and attested on-chain via EAS on Base. Here is how to check one.