Skip to content
TAO$188.40
BTC0.00293
MCap$2.21B
Vol$86.07M

API reference / EVM

Verified EVM contracts

GET/api/v2/evm/verified-contracts
Status
Stable
Auth
API key or OAuth access token
Scope
data:read
Rate limit
plan

Contracts with verified sources on Bittensor EVM (chain 964): each row is the match summary (match, creation_match, runtime_match, verified_at, match_id, updated_at); read GET /evm/contracts/{address}?include=verification, /abi or /source for the rest.

Full description

Contracts with verified sources on Bittensor EVM (chain 964): each row is the match summary (match, creation_match, runtime_match, verified_at, match_id, updated_at); read GET /evm/contracts/{address}?include=verification, /abi or /source for the rest. Not chain data: bittensor.ai's Sourcify list. Paged by meta.page.next_cursor (null on the last page); no total. Cached for 5 minutes.

Two orderings. Without updated_after: by Sourcify's match_id (assigned increasing as verifications are recorded), newest first (order=desc, the default) or oldest first (order=asc). A partial match upgraded to exact is updated in place in Sourcify: it keeps its match_id and its position, so this ordering (and after_match_id) announces NEW verifications only. With updated_after: only the rows whose updated_at is later than it, ordered by (updated_at, address), oldest change first with order=asc. updated_at is bittensor.ai's observation time of the row's current verification (when it first saw this match summary: a new verification, or a partial match upgraded to exact in place), not a Sourcify field: at most about 60 seconds after the change.

Incremental polling (an ABI feeder): - New AND upgraded contracts: ask order=asc&updated_after=<the last updated_at you stored> (the first time, any early time), follow meta.page.next_cursor to the last page, store the last row's updated_at and ask again later from it. Each change is returned once (send updated_at back exactly as served). - New verifications only: order=asc&after_match_id=<the highest match_id you stored>, the same way.

Errors are application/problem+json: INVALID_LIMIT, INVALID_CURSOR (also for cursor with after_match_id, or a cursor sent with other order / updated_after than it came with), INVALID_ID (an after_match_id that is not digits), INVALID_TIME (an updated_after that is not RFC 3339 with an offset), INVALID_PARAMETER (updated_after with after_match_id), INVALID_ORDER, UNKNOWN_PARAMETER, CONTRACT_VERIFICATION_UNAVAILABLE (503, the verification service failed; Retry-After), CONTRACT_VERIFICATION_DISABLED (503, contract verification is off on this deployment).

Query parameters

orderquery· enum · one of desc, asc · default desc

desc (newest first, the default) or asc (oldest first): by match_id, or by (updated_at, address) with updated_after.

limitquery· integer · default 50 · 1 to 100

Page size, 1..100 (default 50).

cursorquery· string · up to 200 characters

meta.page.next_cursor of the previous page, passed back unchanged with the same order and updated_after. It is opaque: a cursor used with other parameters, or altered, is a 400 INVALID_CURSOR. Not with after_match_id.

after_match_idquery· string

Start strictly after this match_id in order: with order=asc, every NEW verification recorded after it (an in-place upgrade keeps its match_id and is not returned again; use updated_after for those); with desc, the older ones. A match_id (digits) from any earlier answer of this route. Not with cursor (a 400 INVALID_CURSOR) nor with updated_after.

Format: whole number, as a string
updated_afterquery· string · up to 64 characters

Only rows whose updated_at is later than this RFC 3339 time (with an offset, e.g. 2026-10-16T12:00:00.123Z), ordered by (updated_at, address): new AND upgraded verifications. Pass the last updated_at you stored, exactly as served. updated_at is bittensor.ai's observation time of the row's current verification (when it first saw this match summary: a new verification, or a partial match upgraded to exact in place), not a Sourcify field: at most about 60 seconds after the change.

Response

data is a list of objects with these fields. Amounts are integer strings in their base unit, and null means unknown, never zero (see Units and formats). meta.at names the block the answer was read at.

The page's contracts, in order.

addressstring

The contract's address, 0x H160, lower case.

Format: EVM address: 0x and 40 hex digits
chain_idinteger · unit id

The EVM chain the verification is for: 964 (Bittensor EVM mainnet).

matchenum

The overall match. exact_match: the recompiled bytecode matches byte for byte, metadata hash included, so the sources are exactly the ones deployed. match: it matches except for the metadata hash (a partial match: same code, but comments or file layout may differ), and can later be upgraded to exact_match. Sourcify's own words.

One of: exact_match, match
creation_matchenum · can be null

The creation bytecode's match. Null when only the runtime code was checked.

One of: exact_match, match
runtime_matchenum · can be null

The runtime bytecode's match. Null when it was not checked.

One of: exact_match, match
verified_atstring (date-time) · can be null

When the verification was recorded (RFC 3339 UTC).

Format: date and time, ISO 8601 in UTC
match_idstring · can be null

Sourcify's id of this verification (matchId, a string of digits). A new verification of the new verification gets a higher id; a partial match upgraded to exact is updated in place and KEEPS its id (so the id marks a new verification, not a change of an existing one). Opaque: compare for equality only.

updated_atstring (date-time) · can be null

When bittensor.ai first observed this row's current verification (a new verification, or a partial match upgraded to exact in place), RFC 3339 UTC with microseconds: not a Sourcify field, at most about 60 seconds after the change. Send it back exactly as updated_after to poll for changes. Null for a row not observed yet (only on the match_id ordering).

Format: date and time, ISO 8601 in UTC

Response headers

10 headers: ETag, Cache-Control, CDN-Cache-Control, X-BTAI-Stale, X-BTAI-Stale-As-Of, RateLimit-Policy, RateLimit, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
ETag

Strong validator of this answer. Send it back as If-None-Match: an unchanged answer is a 304 Not Modified without a body. A settled answer's validator leaves the chain head out, so it stays valid as the head moves.

Cache-Control

One of three classes: settled public, max-age=3600, stale-while-revalidate=86400 (pinned to a block that cannot move), slow public, max-age=300, stale-while-revalidate=600 (state that moves in minutes or days) or tip public, max-age=6, stale-while-revalidate=12 (follows the chain head); the label routes are cached until the next nightly copy (public, max-age=<seconds>, stale-while-revalidate=60). Never immutable. no-store on an earlier answer served because the data source failed (X-BTAI-Stale).

CDN-Cache-Control

The same class for shared caches (RFC 9213; browsers ignore it): settled 24 h, slow 300 s, tip 6 s, each with stale-while-revalidate and stale-if-error; no-store with X-BTAI-Stale.

X-BTAI-Stale

Present only when the data source failed to answer (it timed out or was unavailable) and an earlier answer to the same request is served instead of a 503 (stale if error, RFC 5861). Then if-error, with X-BTAI-Stale-As-Of, Age (its seconds since then) and Warning: 110 - "Response is Stale", and Cache-Control: no-store: the answer is never kept as fresh, and a later request reads again. Prices and quotes are never served this way.

X-BTAI-Stale-As-Of

With X-BTAI-Stale: when the earlier answer served was produced, an RFC 3339 UTC time (2026-10-21T12:00:00Z).

RateLimit-Policy

The tier's request quota of the current window (IETF draft), e.g. "tier";q=600.

RateLimit

Requests left in the current window and the seconds until it resets (IETF draft), e.g. "tier";r=597;t=42.

X-RateLimit-Limit

The tier's request quota of the current window.

X-RateLimit-Remaining

Requests left in the current window.

X-RateLimit-Reset

When the current window resets, Unix seconds.

Status codes

200 · 304 · 400 · 401 · 402 · 403 · 404 · 429 · 500 · 502 · 503

304 Not Modified: the If-None-Match validator still matches; no body.

Error codes

The codes this endpoint can return. Each links to what it means and what to do.

From the API's published specification, version 1.165.0.