AgentProof
Evidence API · Base network

Before your agent
acts, get the facts.

Block-tagged contract evidence and available security and liquidity checks in one structured response. Built for agents that need to check a Base token before their next move.

x402 v2 $0.01 per token · Base USDC · No API key

agentproof / evidence.json
One request. Verifiable evidence.STRUCTURE PREVIEW
{
"network": "Base",
"onchain": { /* Base block + code + metadata */ },
"liquidity": { /* GeckoTerminal pools */ },
"price_comparison": { /* Available market observations */ },
"sources": [ ... ],
"flags": [ ... ]
}
Public data. Clear provenance.
Base RPCGoPlusGeckoTerminalContract provenance
01 / The evidence

Less guesswork. More context.

Check the signals an agent needs, without stitching together three different data formats.

01 — CONTRACT EVIDENCE

Verify the contract at a known block.

Read code, token metadata and EIP-1967 proxy storage directly from Base. Available GoPlus checks add attributed security signals.

Pinned block · Code fingerprint · Proxy slots
02 — LIQUIDITY

See the market behind the token.

Inspect pool-level liquidity from GeckoTerminal when covered. Missing or throttled market data remains explicitly unavailable.

Pools · Liquidity · Market context
03 — COVERAGE

Know where the evidence stops.

See available and unknown checks alongside their exact sources and timestamps. A missing flag does not establish that a token is safe.

Source coverage · Known and unknown · Timestamps
02 / Pay per request

A small check before a big decision.

No subscription or API key. A buyer-authorized agent pays with USDC on Base through native x402.

One token

Base
$0.01USDC / report
GET/v1/base/token?address=0x…

Contract evidence with available security and liquidity signals for one Base token.

A small batch

Up to 3 tokens
$0.03USDC / request
GET/v1/base/batch?addresses=0x…,0x…,0x…

Compare up to three token addresses in one paid request. The batch price is fixed.

Payments configured. Inspect the challenge for the exact amount, network, and recipient before authorizing a payment.

03 / Try the protocol

See what your agent will see.

Inspect an unpaid request in your browser. Read the server's payment requirement, or load the free static sample.

  1. Request the evidence.Send a Base token address to the API.
  2. Review the payment challenge.A configured service returns HTTP 402 with x402 payment requirements.
  3. Authorize through your own client.Your buyer-authorized wallet signs the payment and retries the request.

Inspect a token request No payment

8453

An Ethereum-style contract address on Base. Example: wrapped ETH.

No wallet connection. No signing. No funds moved.

04 / Agent integration

Built to be read by machines.

Start with the schema or sample. Let your agent discover the service and keep payment authorization in your own client.

# Inspect the payment requirement. This request does not pay.
curl -i 'https://agentproof-base.softcreek2.chatgpt.site/v1/base/token?address=0x4200000000000000000000000000000000000006'

# Read a static example for free.
curl 'https://agentproof-base.softcreek2.chatgpt.site/v1/sample'
EndpointPurposePrice
GET /v1/base/token

One address via the address query parameter.

$0.01 USDC
GET /v1/base/batch

Up to three comma-separated addresses.

$0.03 USDC
GET /v1/sample

A static, labeled example of a report response.

Free
GET /health

Service and payment-configuration status.

Free
GET /openapi.json

Request parameters and response schemas.

Free
POST /mcp

Streamable HTTP MCP discovery and tools.

See tool
Evidence, with its limits.

A report helps your agent ask better questions.

Public token data is an input to a decision. It cannot establish that a token is safe, liquid enough for your trade, or likely to appreciate.

Unknown means unknown.

Source gaps, stale data, and upstream failures must be considered alongside the evidence. A missing flag is not a clean bill of health.

Keep authority with the buyer.

Programmatic payments require a buyer-authorized wallet. Set spending limits and inspect the recipient, network, and amount before signing.

Use the schema as the contract.

The terminal above shows structure only. The free sample is static. Use the OpenAPI specification and API responses for integration details.