Back to Browse
Goldsky Polymarket Balances Feed
x402
Goldsky Polymarket Balances Feed is a paid API for AI agents from edge.goldsky.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-31).
Returns token balances for a given wallet address on Polymarket, including position tokens and USDC holdings, with optional filtering and pagination
Price / call$0.005
Success—
StatusUnknown
How this service works
Goldsky Feeds: onchain data over REST. Formerly Edge Data / Data APIs; existing URLs and keys keep working. - **Wallet feeds**: one wallet's token transfers or balances across chains, with USD values (`/feeds/wallets/transfers`, `/feeds/wallets/balances`). - **Tokens**: metadata and current USD price for up to 100 `chain:token_address` pairs per request (`/feeds/tokens`). - **Prediction markets** (Polymarket, on Polygon): Activity, Positions and Balances (`/polymarket/*`). - **Chain datasets**: Blocks and Chain head for each supported chain (`/blocks/{chain}`, `/blocks/{chain}/head`). Base URL: `https://edge.goldsky.com/data`. Every endpoint is a `GET` that returns JSON. ## Authentication Send your Feeds API key in the `x-api-key` header, as the `?key=` query parameter, or as `Authorization: Bearer <key>`. Get it at [app.goldsky.com](https://app.goldsky.com) under **Feeds → API keys**. One key works for every endpoint; an invalid key gets `401`. ## Billing Requests made with a key bill compute units (CUs) at $10 per million: - Wallet feeds and Tokens: 35 CUs per request. - Prediction markets and Chain datasets: 1 CU per row returned. Chain head is 1 CU per call. Errors are not billed, and a Prediction markets or Chain datasets request that returns no rows costs nothing. Rate limits are set per plan (`429` when exceeded); Goldsky support can raise them. ## Pay per request with x402 No account or key needed. A request without a key gets `402` with an x402 v2 challenge in the `PAYMENT-REQUIRED` header (base64 JSON; the body carries the same challenge). Pay in USDC through Circle Gateway and retry. Each payment is a $0.005 prepaid top-up, tied to the paying wallet and shared with Edge RPC, that later requests spend down: - Wallet feeds and Tokens: $0.00035 (350 atomic USDC) per request. - Prediction markets and Chain datasets: $0.00001 (10 atomic USDC) per request, whatever the row count. The payment flow is in [x402 nanopayments](https://docs.goldsky.com/edge-rpc/capabilities/x402).
Output
A paginated JSON object containing an array of token balance records (each with address, token_id, balance, optional token_type, block_number, block_timestamp, contract_address), a limit integer, and a next_cursor string for fetching the next page (null if no more results).
Example use cases
Portfolio snapshot for a Polymarket trader
“Pull all the current outcome token balances for Polymarket wallet 0xABC123...def456 so I can see what positions they're holding right now.”
Minimum balance filter for large holders
“Find all token balances over 1000 units for wallet 0x789...xyz on Polymarket — I only care about meaningful positions, not dust.”
Historical balance audit at a specific block
“What did Polymarket wallet 0xDEAD...BEEF hold as of block 65000000? I need the balance snapshot at that exact point in time.”
Technical details
Endpoint
GEThttps://edge.goldsky.com/data/polymarket/balances?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need onchain token balance data specifically for Polymarket wallet addresses — particularly for querying outcome token positions, filtering by minimum balance, or paginating through a large number of holdings. Prefer this over generic blockchain RPC calls when you want a structured REST response without raw EVM decoding. Best suited for agents doing portfolio analysis, leaderboard construction, or position monitoring on Polymarket.
Side effects
- Missing required 'address' query parameter returns a 400 or validation error
- Invalid wallet address format may return empty data or an error
- as_of_block set too far in the past may not be available in the indexed dataset
- Payment not included or prepaid balance exhausted returns HTTP 402 Payment Required
- Cursor from a previous query becomes stale if data has been re-indexed
- Rate limiting or network issues at edge may cause transient 5xx errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"schema": {
"type": "object",
"properties": {
"data": {
"type": "array"
},
"limit": {
"type": "integer"
},
"next_cursor": {
"type": [
"string",
"null"
]
}
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"