client.markets namespace provides a complete set of discovery methods for finding and resolving prediction market instruments across Molecule’s connected venues — Demo, Polymarket, and Kalshi. Use these methods to run filtered keyword searches, resolve tickers and slugs to instrument IDs, fetch individual instruments, and batch-load multiple instruments in a single round trip.
markets.search
Search for instruments using a keyword query, filtered by venue, status, or category. Returns a paginated list of matching instrument objects. The top-level shortcutclient.search_markets() calls this same endpoint.
GET /v1/markets/search
string
Free-text keyword query. Matches against market title, description, and ticker symbols.
string
Filter results to a specific venue. One of
Demo, Polymarket, or Kalshi.string
Filter by market lifecycle status — for example
OPEN or CLOSED. Omit to return all statuses.string
Filter by category label, such as
Politics or Economics.string
Opaque pagination cursor returned in a previous response. Pass it to fetch the next page of results.
client.search_markets(**params) is a top-level shortcut that delegates directly to client.markets.search(). Use whichever form fits your call site.markets.list
List instruments on a venue without requiring a keyword query. Use this to enumerate all available markets on a specific venue or to apply a broad filter.GET /v1/markets
string
Optional free-text filter. When omitted, the endpoint returns all instruments for the specified venue.
string
Filter to a specific venue. One of
Demo, Polymarket, or Kalshi.markets.match
Resolve a market by a known ticker symbol or URL slug to a single instrument object. Use this when you have a human-readable identifier and need the numericinstrument_id required for order submission and order book requests.
GET /v1/markets/match
string
Venue-native ticker symbol for the instrument. At least one of
ticker or slug is required.string
URL slug for the market. At least one of
ticker or slug is required.markets.get
Fetch a single instrument by its venue-specific integer or string ID. Use this to retrieve the latest snapshot of a known instrument without re-running a search.GET /v1/markets/{id}
integer | string
required
The venue-specific instrument ID. Returned as
instrument_id in search and match responses.markets.lookup
Batch-fetch multiple instruments by their IDs in a single request. Use this instead of issuing multiple sequentialget() calls when you need to hydrate a list of known instrument IDs.
POST /v1/markets/lookup
integer[]
required
List of venue-specific instrument IDs to retrieve. All IDs are fetched in a single round trip.
markets.lookup() issues a POST request to /v1/markets/lookup. Use it to hydrate a set of instrument IDs you already hold — for example, after reading them from your own database or a previous order record.markets.venues
Retrieve the list of venues known to the Molecule platform, including their names and current status. Live venues areDemo, Polymarket, and Kalshi.
GET /v1/venues
markets.venue_health
Check the health of each connected venue to determine which are currently reachable and responsive before routing orders.GET /v1/venues/health
