Use it when your goal in payments and business operations is clear and you can limit it to the data and actions it actually needs.
Polymarket
Query Polymarket: markets, prices, orderbooks, history
What does it add to Hermes?
Query Polymarket: markets, prices, orderbooks, history
Polymarket is a skill related to payments and business operations. It handles financial or commercial data and actions; any write operation needs stronger approval and limits than ordinary use.
This plain-language explanation is based on the publisher description. The original text remains visible for verification.
Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.
Best for users who want a repeatable way of working inside Hermes.
Use a sandbox or test data and do not grant real payment or refund permissions in the first test.
Query Polymarket: markets, prices, orderbooks, history
This entry was indexed from Hermes Optional Skills. Our explanation interprets the type and domain without inventing a capability not present upstream.
The source is official or editorially reviewed, but you still need to review permissions and version compatibility.
Inspect, install, then test.
- 01Open the source
Match the publisher, license, and description to your need. Check the real update history.
- 02Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
- 03Copy setup only after review
The controls below copy text. They do not execute commands on your device.
- 04Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.
Review the command, then copy it.
hermes skills install polymarketHermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.
Exactly what Hermes loads when this skill runs.
Reproduced from the official documentation. Read it before enabling the skill: this text becomes the agent's instructions.
Query Polymarket: markets, prices, orderbooks, history.
Skill metadata
A lookup table. Do not read it all; find the row that applies to you.
| Source | Optional — install with hermes skills install official/finance/polymarket |
| Path | optional-skills/finance/polymarket |
| Version | 1.0.0 |
| Author | Hermes Agent + Teknium |
| License | MIT |
| Platforms | linux, macos, windows |
Reference: full SKILL.md
Explains the idea itself. Read it slowly; the later sections build on it.
Query prediction market data from Polymarket using their public REST APIs. All endpoints are read-only and require zero authentication.
See references/api-endpoints.md for the full endpoint reference with curl examples.
When to Use
Explains the idea itself. Read it slowly; the later sections build on it.
- User asks about prediction markets, betting odds, or event probabilities
- User wants to know "what are the odds of X happening?"
- User asks about Polymarket specifically
- User wants market prices, orderbook data, or price history
- User asks to monitor or track prediction market movements
Key Concepts
Explains the idea itself. Read it slowly; the later sections build on it.
- Events contain one or more Markets (1:many relationship)
- Markets are binary outcomes with Yes/No prices between 0.00 and 1.00
- Prices ARE probabilities: price 0.65 means the market thinks 65% likely
outcomePricesfield: JSON-encoded array like["0.80", "0.20"]clobTokenIdsfield: JSON-encoded array of two token IDs [Yes, No] for price/book queriesconditionIdfield: hex string used for price history queries- Volume is in USDC (US dollars)
Three Public APIs
Explains the idea itself. Read it slowly; the later sections build on it.
- Gamma API at
gamma-api.polymarket.com— Discovery, search, browsing - CLOB API at
clob.polymarket.com— Real-time prices, orderbooks, history - Data API at
data-api.polymarket.com— Trades, open interest
Typical Workflow
Explains the idea itself. Read it slowly; the later sections build on it.
When a user asks about prediction market odds:
- Search using the Gamma API public-search endpoint with their query
- Parse the response — extract events and their nested markets
- Present market question, current prices as percentages, and volume
- Deep dive if asked — use clobTokenIds for orderbook, conditionId for history
Presenting Results
Explains the idea itself. Read it slowly; the later sections build on it.
Format prices as percentages for readability:
- outcomePrices
["0.652", "0.348"]becomes "Yes: 65.2%, No: 34.8%" - Always show the market question and probability
- Include volume when available
Example: "Will X happen?" — 65.2% Yes ($1.2M volume)
Parsing Double-Encoded Fields
Explains the idea itself. Read it slowly; the later sections build on it.
The Gamma API returns outcomePrices, outcomes, and clobTokenIds as JSON strings
inside JSON responses (double-encoded). When processing with Python, parse them with
json.loads(market['outcomePrices']) to get the actual array.
Rate Limits
Explains the idea itself. Read it slowly; the later sections build on it.
Generous — unlikely to hit for normal usage:
- Gamma: 4,000 requests per 10 seconds (general)
- CLOB: 9,000 requests per 10 seconds (general)
- Data: 1,000 requests per 10 seconds (general)
Limitations
Explains the idea itself. Read it slowly; the later sections build on it.
- This skill is read-only — it does not support placing trades
- Trading requires wallet-based crypto authentication (EIP-712 signatures)
- Some new markets may have empty price history
- Geographic restrictions apply to trading but read-only data is globally accessible