Polymarket
Polymarket prediction markets integration for accessing markets, events, pricing, orderbooks, positions, trades, and leaderboard data. Uses Gamma API for market discovery, CLOB API for pricing data, and Data API for trading analytics. API key is optional for most read-only operations. All nodes support both Connect session mode and direct API key credentials per node.
| Namespace | Robomotion.Polymarket |
| Version | 1.1.0 |
| Category | Financial, Analytics |
| Nodes | 16 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Polymarket and returns a Client ID. |
| Disconnect | Closes a Polymarket connection. |
| Get Markets | Gets markets in Polymarket. |
| Get Market | Gets a market in Polymarket. |
| Get Events | Gets events in Polymarket. |
| Get Event | Gets an event in Polymarket. |
| Search | Searches in Polymarket. |
| Get Orderbook | Gets an orderbook in Polymarket. |
| Get Price | Gets a price in Polymarket. |
| Get Midpoint | Gets a midpoint in Polymarket. |
| Get Spread | Gets a spread in Polymarket. |
| Get Price History | Gets a price history in Polymarket. |
| Get Positions | Gets positions in Polymarket. |
| Get Trades | Gets trades in Polymarket. |
| Get Leaderboard | Gets a leaderboard in Polymarket. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
15 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Get Markets, Get Market, Get Events, Get Event, Search, Get Orderbook, Get Price, Get Midpoint, Get Spread, Get Price History, Get Positions, Get Trades, Get Leaderboard.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.