Developers
Documentation and examples for existing tools. Explore managed reconciliation and close services.
AgentProof Quick Check
Base chain identity + official USDC contract-presence check.
A small deterministic check on Base. No request body is needed. Not a Token Risk report, transaction simulation, payment proof, or smart-contract audit.
Existing API documentation
Reference documentation for SpendGuard and AgentProof. Paid API checks use USDC over x402 and remain separate from managed close services.
One client for SpendGuard and AgentProof
npm install @kushbitx/sdk
import { KushBitxClient } from '@kushbitx/sdk';
const kushbitx = new KushBitxClient();GET /api/agentproof-quick-checkAgentProof Quick Check · 0.001 USDC / call. Base chain identity and official USDC contract presence; no request body.
ExamplePOST /api/token-riskToken sellability, controls, concentration and market risk.
POST /api/transaction-preflightUnsigned call simulation and dangerous approval detection.
POST /api/verify-paymentBase USDC transfer verification with confirmation count.
Give your agent its first Base check
Copy these instructions into an agent that can make HTTP requests. It can fetch market data and check data availability before you consider a paid report. No account or wallet needed.
Invite another builder to try it
Share this free starting point. The link contains no wallet information or private report details.
Paid services are optional: AgentProof Quick Check 0.001 USDC, payment verification 0.01 USDC, unsigned transaction preflight 0.05 USDC, token report 0.25 USDC. A delivered INCOMPLETE report still carries the displayed fee.
Start with a free API request
Send this JSON request to the same domain. A successful response includes token identity and trading-pair market data. The preview does not include a security verdict.
POST /api/token-preview
Content-Type: application/json
{"chain":"base","address":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}How a paid request works
- Use GET with no request body for AgentProof Quick Check, or POST input JSON for Token Risk, Transaction Preflight and Payment Proof. The initial HTTP 402 response is a payment request; it does not charge your wallet.
- Use an x402 v2 client to read the PAYMENT-REQUIRED header and authorize the displayed USDC amount on Base.
- Retry the same request with the PAYMENT-SIGNATURE header. HTTP 200 returns the completed report. Handle non-200 responses before using a result.
Run the SDK-supported reports from one agent example
Node.js 22 or later. The free token and SpendGuard previews need no package installation. Download the example above, then start free.
node agent.mjs
node agent.mjs --spendguard
# Explicit paid runs. Paid mode requires viem and a dedicated wallet.
npm install viem
# Set AGENT_PRIVATE_KEY in your local secret manager first.
node agent.mjs --paid --service=token-risk
TX_TO=0x… node agent.mjs --paid --service=preflight
TX_HASH=0x… EXPECTED_TO=0x… EXPECTED_AMOUNT=1.00 node agent.mjs --paid --service=payment
# Restore the same saved report without paying again
node agent.mjs --restore --service=token-riskThe example checks the recipient, token, network and exact price before signing. It saves a private recovery file before payment, never submits the transaction being inspected, and never trades. An INCOMPLETE verdict or null score means missing evidence.
Keep each recovery file private. Preflight and payment proof use service-specific default filenames. To reconcile an interrupted settled payment, set PAYMENT_TX_HASH before running --restore. Preserve each recovery file before starting a new report.