Polymarket (Gamma): 8 reads, one client

Polymarket's search and discovery API — full-text search, events, series, tags and comments. No API key. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Polymarket (Gamma) can do here

The integration exposes 8 reads, each with a declared input and output schema rather than a page of documentation you would have to translate. Polymarket's search and discovery API — full-text search, events, series, tags and comments. No API key.

How it authenticates

Polymarket (Gamma) authenticates with no secret at all, supplied per request or stored once against your account and sealed at rest.

Capabilities it fulfils

Polymarket (Gamma) answers prediction.market.search in the vendor-neutral form, which means code asking for that capability can be pointed at Polymarket (Gamma) without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.

• search — read: FULL-TEXT SEARCH across events, tags and user profiles at once. Public and free — the operation to reach for when the input is what somebody typed rather than an id.
• listMarkets — read: Filter and sort markets. The connection test — public and free.
• getMarket — read: One market by Gamma id. Public and free.
• listEvents — read: Events — groups of related markets, which is how Polymarket presents them to users. Public and free.
• getEvent — read: One event with its markets. Public and free.
• listSeries — read: Recurring market series — NFL weeks, monthly CPI prints. Public and free.
• listTags — read: The category vocabulary — what tag_id filters accept. Public and free.
• listComments — read: Comments on an event or series — crowd sentiment alongside the price.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.