# Prime-Agent x402 Intelligence – Token Metadata Lookup

> Prime-Agent x402 Intelligence – Token Metadata Lookup is a paid API for AI agents from prime-agent-x402-intelligence.onrender.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Returns on-chain metadata (name, symbol, decimals, contract status, block snapshot) for a given ERC-20 token address on Base mainnet, paid via x402 micropayment.

## Facts

- Endpoint: GET https://prime-agent-x402-intelligence.onrender.com/token/metadata/%7Baddress%7D?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prime-agent-x402-intelligence-token-metadata-lookup-df7af5d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KtSqnuCbGPS8i4-HwxNfA

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 prime-agent-x402-intelligence-token-metadata-lookup-df7af5d9
```

Example prompt: Look up the on-chain metadata — name, symbol, and decimals — for the token at address 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa on Base mainnet, and include the block snapshot so I have provenance.

## When to prefer this

Choose this endpoint when you need verified, block-anchored token metadata (name, symbol, decimals) specifically on Base mainnet (eip155:8453), with cryptographic provenance via block hash — particularly when auditability or downstream trust in the data source matters. Prefer over generic blockchain explorers when you need structured JSON output with evidence IDs and missing-field detection, or when operating in an x402-compatible micropayment environment.

## Known failure modes

- Address not a contract: is_contract returns false, fields may be empty or missing
- Invalid address format: request fails with a 4xx error
- Token missing metadata fields: missing array lists unpopulated fields
- x402 payment failure: 402 response if micropayment not processed
- Network unavailable: 5xx if Base RPC is unreachable
- Non-Base address: results may be empty if contract only exists on other chains

## How this service works

x402-paid Base intelligence with free machine-readable discovery.

## Output

A JSON object containing the token address, a fields object with name, symbol, and decimals, a list of any missing fields, the network identifier (eip155:8453), a snapshot with block hash, block number, and observed_at timestamp, a boolean is_contract flag, and an array of evidence IDs for provenance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "token": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "fields": {
   "name": "Example Token",
   "symbol": "TOKEN",
   "decimals": 18
  },
  "missing": [],
  "network": "eip155:8453",
  "snapshot": {
   "network": "eip155:8453",
   "block_hash": "0x1111111111111111111111111111111111111111111111111111111111111111",
   "observed_at": 1760000000,
   "block_number": 12345678
  },
  "is_contract": true,
  "evidence_ids": [
   "example-evidence-id"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prime-agent-x402-intelligence-token-metadata-lookup-df7af5d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prime-agent-x402-intelligence.onrender.com](https://www.zero.xyz/host/prime-agent-x402-intelligence.onrender.com/llms.txt)