Detects which EVM chains an address is active on
Detects which EVM chains an address is active on (probes 6 chains)
/api/browser/detectRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| q | string | Optional | — | — | Address to classify; non-EVM input returns unsupported_format. Example: 0x00000000219ab540356cBB839Cbe05303d7705Fa |
Example request
curl -s "https://www.coinboss.com/api/browser/detect?q=0x00000000219ab540356cBB839Cbe05303d7705Fa"Response fields
The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| kind | string | — | Kind. |
| results | array | — | Chains on which the address lookup succeeded, one entry per chain with `chain`, `ok`, `balance` and `usd`. empty in the samples used to generate this table |
| failed | array | — | Chains on which the lookup failed or returned no balance; the state on these chains is unknown, not empty. |
| failed[] | string | — | Chain id, for example `eth`, `bsc`, `polygon`, `avalanche`, `optimism` or `base`. |
| no_activity_chains | array | — | Chains on which the address format is valid but no activity was found. empty in the samples used to generate this table |
Generated 2026-11-11 23:01 UTC from 1 real responses.
Example response
/api/browser/detect?q=0x00000000219ab540356cBB839Cbe05303d7705Fa · Real response captured 2026-11-13 03:53:37 UTC.
- "success"true
- "kind""lookup_failed"
- "results"
- "failed"
- "eth"
- "bsc"
- "polygon"
- "avalanche"
- "optimism"
- "base"
- "no_activity_chains"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- Not cached
- Edge micro-cache
- 10s
- Update frequency
- real time (60 s cache)
- Window
- latest snapshot
- Data sources
- Address activity lookup across EVM chains, scraped at request time from a third-party block explorer website (not an official public API).
- Exchange coverage
- EVM addresses only (0x + 40 hex) on eth, bsc, polygon, avalanche, optimism, base; other formats return unsupported_format. Currently all chains fail.
- Sorting
- USD value descending
- Units
- USD value per chain
- Method
- Probes the address on each chain in parallel and returns the chains with activity, sorted by USD value.
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
`kind` is `lookup_failed` when no chain could be queried and `no_activity` only when every chain answered and none shows activity.
Availability, last 30 days
100% of 407 checks passed
Errors
Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A required parameter is missing or a value is not accepted. `param` names the parameter when it is known. | Do not retry unchanged; fix the request. |
| UNAUTHORIZED | 401 | The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key. | Do not retry unchanged. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected server error. The message is generic by design; quote `request_id` when reporting it. | Retry once after a few seconds; report it with the request id if it persists. |
| UPSTREAM_FAILED | 503 | The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place. | Retry with backoff; check the status page. |
| UNAVAILABLE | 501 / 503 | The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet. | Retry later; the catalog marks endpoints that are unavailable by design. |
| REQUEST_FAILED | 200 | Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status. | Depends on the message; treat as a failed request. |
Try it
/api/browser/detectPartialstring — Address to classify; non-EVM input returns unsupported_format.
https://www.coinboss.com/api/browser/detect?q=0x00000000219ab540356cBB839Cbe05303d7705FaMore in this category
- Multi-chain address lookup /api/browser/:chain/address/:addr
- Multi-chain block lookup /api/browser/:chain/block/:hashOrHeight
- Multi-chain transaction lookup /api/browser/:chain/tx/:txid
- Detects which EVM chains an address is active on /api/browser/detect
- Balance changes among BTC rich-list addresses /api/btc/rich-flow
- BTC rich list /api/btc/rich-list
- BTC rich-list statistics /api/btc/rich-stat
- BTC rich-list holdings trend /api/btc/rich-trend
- Bitcoin address summary /api/explorer/address/:addr
- Bitcoin address transactions /api/explorer/address/:addr/txs
- Bitcoin block detail /api/explorer/block/:hashOrHeight
- Bitcoin chain tip /api/explorer/tip
- Bitcoin transaction detail /api/explorer/tx/:txid
- Count of BTC addresses holding more than a threshold /api/indicators/addr-above/:tier
- BTC on-chain valuation indicator series /api/indicators/bdc/:name
- Bitcoin reachable-node count and distribution /api/indicators/bitnodes
- BTC holder comparison series /api/indicators/btccmp/:pair
- BTC on-chain chart series /api/indicators/chain
- Exchange BTC inflow / outflow history /api/indicators/cm/exchange-flows
- BTC supply held on exchanges /api/indicators/cm/exchange-supply
- BTC non-zero address count history /api/indicators/cm/nonzero-addresses
- Government BTC holdings /api/indicators/gov-treasuries
- Bitcoin halving countdown and history /api/indicators/halving
- Share of BTC supply dormant for more than N years /api/indicators/hodl-wave-above/:years
- Bitcoin mining-pool block share /api/indicators/mempool/pools
- Strategy BTC cost basis and holdings history /api/indicators/mstr-cost
- Share of BTC supply in profit /api/indicators/supply-profit-pct
- WBTC reserve balance history /api/indicators/wbtc-balance
- Multi-chain rich list /api/rich-list/:chain
- Multi-chain rich-list balance changes /api/rich-list/:chain/flow
- Multi-chain rich-list statistics /api/rich-list/:chain/stat
- Multi-chain rich-list holdings trend /api/rich-list/:chain/trend
- Public-company / institutional coin treasuries /api/treasuries/:coin