Polymarket — Look up tokens

Resolves token ids, or the tokens of conditions, to their condition, module, outcome, market, event and neg-risk question index in one call with the Polymarket API. The sample response includes titles. Use it for on-chain or crypto market research. The GET request schema also lists token_id. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.

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
Token id(s), comma-separated (at most 50 distinct values): decimal ERC-1155 ids as they appear on receipts and on the `token_id` and `asset` fields of the other routes. Elements are trimmed, leading zeros stripped and duplicates collapsed to their first position. `token_ids` is an accepted alias. Exactly one of `token_id` and `condition` is required. This execution profile requires an explicit non-null value. The original optional/nullable OpenAPI declarations remain in officialOperation.
Condition selector(s), comma-separated (at most 10 distinct values), each `0x` followed by 62 or 64 hex digits: a ConditionalTokens condition id (for a market carried over to polymarket-v2, its whole family), a neg-risk market id (every market of the structure), a polymarket-v2 condition id (that condition only), the 66-character condition id of a native polymarket-v2 market, or the on-chain event id of a polymarket-v2 neg-risk structure (every question of it). Elements are trimmed, lower-cased and duplicates collapsed to their first position. `condition_id` and `conditionId` are accepted aliases. Exactly one of `token_id` and `condition` is required.

Sample response

{
  "data": [
    {
      "clob_index": 0,
      "closed": false,
      "condition_id": "0x7586a96520578acaaaa4ea84a2582f197f84255da1f3392a7aa300386c187b37",
      "event_id": 81557,
      "event_slug": "who-will-be-the-next-prime-minister-of-israel-after-the-next-election",
      "final_price": null,
      "market_slug": "will-benjamin-netanyahu-be-the-next-prime-minister-of-israel",
      "module": "v1_ctf",
      "neg_risk": true,
      "neg_risk_market_id": "0x03c9c6d9f7b20aaa1f33f99bd24bd16e4e0e00cfa892dde097b800655490b200",
      "opposite_token_id": "54533569528927082430133047556849600511985191158927477533124630301934489498530",
      "outcome": "Yes",
      "outcome_index": 0,
      "question_index": 0,
      "resolved": false,
      "structural_condition_id": null,
      "title": "Will Benjamin Netanyahu be the next Prime Minister of Israel?",
      "token_id": "20006732765674855733524007935991362439352594042415161039767275461950712817548"
    }
  ]
}

Response result

Response structure

Inferred from examples
  • dataobject[]
    • clob_indexinteger
    • closedboolean
    • condition_idstring
    • event_idinteger
    • event_slugstring
    • final_pricenull
    • market_slugstring
    • modulestring
    • neg_riskboolean
    • neg_risk_market_idstring
    • opposite_token_idstring
    • outcomestring
    • outcome_indexinteger
    • question_indexinteger
    • resolvedboolean
    • structural_condition_idnull
    • titlestring
    • token_idstring

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 Polymarket — Look up tokens with your agent

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