# BitBooth Contract Honeypot Check

> BitBooth Contract Honeypot Check is a paid API for AI agents from app.heinrichstech.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Analyzes any Base mainnet ERC-20 token contract for honeypot characteristics, returning a yes/no signal, 0-100 risk score, and per-signal severity breakdown for a 0.001 USDC fee.

## Facts

- Endpoint: POST https://app.heinrichstech.com/v1/cdp/contract-honeypot-check
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitbooth-contract-honeypot-check-83c469e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1weQpFFmYkcpukIBxiAcp

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bitbooth-contract-honeypot-check-83c469e0 -d '<json body>'
```

Example prompt: Before I buy this token, run a honeypot check on the Base mainnet contract at 0x1234...abcd — I want to know if it's a honeypot, its risk score out of 100, and which specific signals are flagging red.

## When to prefer this

Use this endpoint when you need a fast, low-cost (0.001 USDC) honeypot signal for a Base mainnet ERC-20 token before executing a trade or swap. It is ideal for pre-trade safety gates in DeFi bots, wallet risk UIs, or token vetting pipelines where speed and cost efficiency matter more than deep on-chain simulation. Prefer it over heavier wallet-risk or approval-safety endpoints when you only need the contract-level honeypot verdict, not full wallet history or approval analysis.

## Known failure modes

- Invalid or malformed contract address returns an error response
- Non-ERC-20 or non-Base mainnet contracts may return unexpected results
- Insufficient USDC balance or payment failure prevents the check from running
- Contracts that are highly obfuscated or use novel proxy patterns may produce incomplete signal sweeps
- Rate limiting or network issues with the Base RPC may cause timeouts

## How this service works

BitBooth Contract Honeypot Check: pay 0.001 USDC, get a yes/no honeypot signal for any Base mainnet ERC-20. Single eth_getCode fetch + static-selector sweep (blacklist, pausable, dynamic fee, mint, owner-transfer, tiny proxy, EOA). Returns isHoneypot, 0-100 riskScore, and per-signal severity. Cacheable per (chain, address).

## Output

Returns a JSON object containing: `isHoneypot` (boolean), `riskScore` (integer 0-100), and a breakdown of per-signal results with severity levels for signals including blacklist, pausable, dynamic fee, mint, owner-transfer, tiny proxy, and EOA detection. Results are cacheable per (chain, address) pair.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitbooth-contract-honeypot-check-83c469e0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from app.heinrichstech.com](https://www.zero.xyz/host/app.heinrichstech.com/llms.txt)