Public API access
All Correlated Markets endpoints are public partner API endpoints under the Discovery tag in the API Reference. They require only your app header:string
required
Your AGG app identifier.
includeResolved: true.
Endpoint map
Resolve a market
Useresolve when your app stores venue-native identifiers. The endpoint resolves the market,
checks whether signals already exist, and then returns a paginated cascade.
Expand vs hedge
mode: "expand" returns Yes-side events that become more attractive if your thesis is right.
mode: "hedge" returns Yes-side events that become more attractive if your thesis is wrong. Hedge
results exclude the expand results for the same market and side.
Use an AGG market id directly
If your UI already has avenueMarket.id from GET /venue-events or GET /venue-markets, call
the cascade endpoint directly.
limit is capped at 100. Pagination uses the returned nextCursor.
Result shape
Each result is an event-level candidate. UsevenueEventId to fetch full event details or navigate
to the event in your UI.
Inspect generated signals
Each market is summarised by a set of generated Yes/No signals — short statements that explain which real-world states become more or less likely if the market resolves a given way. These signals power the cascade and connection endpoints; fetch them directly when you want to render “why this market is related” copy.Side- and mode-agnostic connections
connections returns related events for a market without requiring a side or mode. It is the
right call when you just want “what else is connected to this market” — for example, on an event
detail page where you want a single Related Markets rail.
nextCursor. Resolved and closed markets are excluded by default;
pass includeResolved=true to include them.
Search by theme
Use semantic query search when the user starts from a theme instead of a specific market. Query results include market and event status/date fields, so clients can keep resolved markets out of tradeable recommendation UIs without extra lookups. Usedirection to request only
more_likely or less_likely signals, or balanced: true to mix both directions in one page.
Coverage and worker status
status exposes signal coverage, embedding coverage, and the background worker configuration so
operators can spot stalled generation or low coverage from a dashboard.
Related
API Reference
View schemas and try the Correlated Markets endpoints.
Building Market Views
Compose Discovery endpoints into event grids and trading views.