Sourcify — Get verified contract

By default returns minimal information about the contract: `match`, `creationMatch`, `runtimeMatch`, `chainId`, `address`, and `verifiedAt`. To get other details one can either list the fields requested in the `fields` query param or ask all fields but omit several with `omit`. To get everything just pass `fields=all`. **Request only the fields that you need.** `fields=all` returns every field, including all source files and the full standard JSON input and output. It is the most expensive request on this endpoint. Do not use `fields=all` or `stdJsonInput` in loops. To collect data for many contracts, use the [Parquet export](https://docs.sourcify.dev/docs/repository/download-dataset/) or the [BigQuery dataset](https://docs.sourcify.dev/docs/bigquery/) instead. **Available fields:** - `matchId` – unique match ID - `creationMatch` – creation bytecode match status (`match`, `exact_match`, or `null`) - `runtimeMatch` – runtime bytecode match status (`match`, `exact_match`, or `null`) - `verifiedAt` – ISO 8601 timestamp of when the current match was verified. If a later verification upgrades the match (for example from `match` to `exact_match`), this timestamp changes to the time of that verification. - `abi` – contract ABI - `metadata` – Solidity compiler metadata object - `sources` – map of source file paths to their content - `sourceIds` – AST source IDs from the standard JSON compiler output - `userdoc` – user-facing NatSpec documentation - `devdoc` – developer NatSpec documentation - `storageLayout` – contract storage layout - `transientStorageLayout` – transient storage layout (Solidity >= 0.8.24) - `additionalInput` – extra top-level compiler input fields (e.g. Vyper `storage_layout_overrides`) - `stdJsonInput` – full standard JSON compiler input - `stdJsonOutput` – full standard JSON compiler output Nested objects support dot-notation sub-selection (e.g. `creationBytecode.onchainBytecode`): - `creationBytecode` — sub-fields: `onchainBytecode`, `recompiledBytecode`, `sourceMap`, `linkReferences`, `cborAuxdata`, `transformations`, `transformationValues` - `runtimeBytecode` — sub-fields: `onchainBytecode`, `recompiledBytecode`, `sourceMap`, `linkReferences`, `cborAuxdata`, `immutableReferences`, `transformations`, `transformationValues` - `deployment` — sub-fields: `transactionHash`, `blockNumber`, `transactionIndex`, `deployer` - `compilation` — sub-fields: `language`, `compiler`, `compilerVersion`, `compilerSettings`, `name`, `fullyQualifiedName` - `signatures` — sub-fields: `function`, `event`, `error` - `proxyResolution` – proxy detection result (no sub-fields) Documentation prepared only; runtime not verified.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
The chainId number of the EVM chain
Contract's 20 byte address in hex string with the 0x prefix. Case insensitive.
Comma-separated list of fields to include in the response. Can also be `all` to return every available field. See the endpoint description for the full list of available fields. `all` includes all source files and the full standard JSON input and output, so it is expensive. Do not use `all` in loops. Request only the fields that you need.
Comma seperated fields to NOT include in the response. All fields except matching ones will be returned. Can't be used simultanously with `fields`. A short `omit` list returns almost every field, so it costs almost as much as `fields=all`. Do not use `omit` in loops. Use `fields` to request only what you need.

Sample response

{
  "address": "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2",
  "chainId": "1",
  "creationMatch": "match",
  "match": "match",
  "matchId": "1605500",
  "runtimeMatch": "match",
  "verifiedAt": "2024-08-08T13:28:37Z"
}

Response result

Response structure

Inferred from examples
  • addressstring
  • chainIdstring
  • creationMatchstring
  • matchstring
  • matchIdstring
  • runtimeMatchstring
  • verifiedAtstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Sourcify — Get verified contract with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.