Buyer Intent

Base Honeypot Detection API

Use Augur when an agent needs a fast Base token screen before buying, routing, or surfacing a token to a user. Honeypot patterns are checked alongside the rest of Augur's bytecode risk model.

Augur scores Base mainnet contract bytecode for agents. A safe result means no major bytecode-level risk signals were detected in this scan, not a full audit or guarantee.

Why teams look for this API

Catch transfer restriction patterns before a trading agent routes funds.
Avoid treating a token as clean just because a swap quote succeeds.
Pair honeypot checks with proxy, fee manipulation, and deployer signals.

What Augur checks on the same request

Honeypot bytecode patterns that can trap exits or restrict transfers.
Fee manipulation and hidden mint signals that often travel with scam tokens.
Proxy and delegatecall behavior that can hide mutable token logic.
Deployer reputation context from Basescan-backed history checks.

Call the canonical endpoint

All buyer-intent pages map back to the same paid API: GET https://augurrisk.com/analyze?address=0x4200000000000000000000000000000000000006

curl -s "https://augurrisk.com/analyze?address=0x4200000000000000000000000000000000000006" \
  -H "PAYMENT-SIGNATURE: <x402-payment-proof>" | jq

x402 payment is per-call, using USDC on Base. For the 402 flow details, see How Augur payment works.

Integration links

Related intent pages

Base Proxy Risk API

/proxy-risk-api

Base Deployer Reputation API

/deployer-reputation-api