address_label
Protocol, exchange, bridge, locker — or just a wallet? — What is this Base address? Matches a sourced registry of known protocol, exchange, bridge, locker and burn addresses (each with the docs/deployments/Basescan source it came from), then reads the chain: contract vs EOA (EIP-7702 delegation shown), ERC-4626 vault (asset()), Safe multisig (getThreshold), DEX pool interface (token0/token1). Unmatched addresses are reported as unlabelled, never guessed. Required input: address. Priced $0.005 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"address": "<address>"
},
"name": "address_label"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Base address to identify |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The result payload. Shape is service-specific; every field is documented in the tool description. | |
| service | No | The service id that answered. | |
| checkedAt | No | ISO-8601 timestamp of when the underlying reads were taken. |