# Sentinela Base Token Lookup

> Sentinela Base Token Lookup is a paid API for AI agents from agente.sistematech.cloud, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-20).

Looks up ERC-20 token metadata (name, symbol, decimals, total supply) on the Base blockchain by contract address, billed per call via x402/USDC.

## Facts

- Endpoint: GET https://agente.sistematech.cloud/token/%7Baddress%7D?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sentinela-base-token-lookup-1852041f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tfzPLYsbsIGkPnu6_G55A

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 sentinela-base-token-lookup-1852041f
```

Example prompt: What ERC-20 token is at contract address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base? I need its name, symbol, decimals, and total supply.

## When to prefer this

Use this endpoint when you need quick, pay-per-call ERC-20 token metadata lookups specifically on the Base L2 network and want to avoid API key setup or subscriptions. It is ideal for agents that infrequently query Base token info and prefer micropayment billing via x402/USDC. Prefer alternatives if you need Ethereum mainnet data, historical token data, price feeds, or high-volume batch lookups.

## Known failure modes

- Invalid or malformed contract address returns an error or empty response
- Address exists on Base but is not an ERC-20 token (e.g. EOA or non-standard contract) may return null fields
- Contract address from a different chain (e.g. Ethereum mainnet) will not resolve correctly on Base
- Payment failure via x402 (insufficient USDC balance) prevents the call from completing
- Rate limiting or network congestion on Base RPC may cause timeouts

## How this service works

Pay-per-call Base onchain lookups via x402 (USDC on Base).

## Output

Returns a JSON object containing the token's human-readable name, symbol (ticker), number of decimals, total supply (as a string), network identifier (e.g. 'base'), and the queried contract address. Example: {nome: 'USD Coin', rede: 'base', address: '0x833589...', simbolo: 'USDC', decimais: 6, supplyTotal: '4203507751.082895'}.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "nome": "USD Coin",
  "rede": "base",
  "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "simbolo": "USDC",
  "decimais": 6,
  "supplyTotal": "4203507751.082895"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sentinela-base-token-lookup-1852041f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agente.sistematech.cloud](https://www.zero.xyz/host/agente.sistematech.cloud/llms.txt)
