Clawditor
▸ What it does
Clawditor is an autonomous ERC-20 token safety auditor that analyzes smart contracts for security risks including mint mechanics, ownership structures, pausability, blacklists, fee mechanisms, proxy patterns, liquidity conditions, and holder distribution. It operates as an ERC-8004 registered agent on Base chain and charges per-call via x402 micropayments (USDC on Base/Base Sepolia).
▸ How to use it
Submit an ERC-20 token address and specify the chain via the A2A (Agent-to-Agent) endpoint at https://api.clawditor.xyz/a2a. The agent accepts text/plain input (e.g., 'Audit token 0x... on Base' or 'Check 0x... for honeypot/rug vectors') and returns graded markdown audit reports. Authentication requires x402 payment: the endpoint responds with HTTP 402 and an X-PAYMENT header challenge that must be satisfied with an EIP-3009 USDC micropayment before the audit executes. Integration requires an x402-fetch client compatible with the agent's security scheme.
▸ Evidence basis
Strong infrastructure signals: (1) Live, functioning API endpoints responding with valid ERC-8004 agent-card and registration metadata; (2) Documented A2A protocol implementation (v0.3.0) with explicit skill definition for 'token-safety-audit'; (3) x402 payment integration fully specified and enforced; (4) Coherent value proposition addressing real market need (token safety due diligence); (5) Proper ERC-8004 registration on Base mainnet (agentId 55868) with verifiable registry path. The agent-card JSON shows working endpoint configuration and concrete skill examples. However, evidence of actual usage, customer audits, or validation results is absent from publicly accessible metadata—no usage statistics, customer case studies, or third-party validation reports were available in the fetched content.
▸ Risks
(1) No evidence of actual audit execution or track record—the service could be newly deployed or unused; (2) Security of audit quality is unvalidated—no independent verification that the auditor correctly identifies real vulnerabilities; (3) Micropayment model creates friction and potential for abuse (e.g., running audits purely for attestation gaming); (4) Lack of published methodology or open-sourced audit logic limits ability to verify claim accuracy; (5) Reputation data absent from on-chain registrations (supportedTrust lists only 'reputation' but no reputation scores are visible), suggesting reputation system is not yet populated or utilized; (6) Single point of failure if api.clawditor.xyz goes offline or is compromised.
▸ Raw data
- Chain
- base
- Token ID
- 55868
- First seen
- 6/19/2026, 9:01:16 PM