Developer resources
HIP-4 sports data & agent access
The same team and player market history for people, search engines and read-only agent tools.
Which teams and players have pages?
A page is created when Liquidiction indexes a real HIP-4 market featuring that team or player. A future listing qualifies before the game or season starts. The page remains available after settlement, with links to its recorded markets. Teams and players without indexed markets have no profile.
Profiles are scoped by sport and use permanent URLs. Multiple deployer listings can appear under one matchup; each contract retains its own market link, terms and settlement state.
Coverage and freshness
These pages cover indexed HIP-4 markets, not every game in a team’s history. Background refreshes run on the existing five-minute schedule. Reads use shared cached snapshots; prices and sports feeds are not fetched separately for each visitor or agent.
Verified final scores are recorded when available and matched by provider participant IDs, competition and event time. A missing score means no verified result is currently linked. Past results outside the retained provider feed may be unavailable. Contract settlement and a final sporting result are separate records.
The APIs report generatedAt, archive catch-up status and result coverage. A temporarily unavailable archive returns an error instead of an empty history. Use the individual market page and order preview for current prices and executable liquidity.
Public JSON APIs
No wallet connection or API key is needed. Fetch the catalog once and reuse it to search by name or verified alias.
GET /api/sports-entities— eligible teams and players, canonical identity fields and market counts.GET /api/sports-entities/{kind}/{sport}/{slug}?page=1— one profile with up to 20 market events per page. Usekind,sportandslugfrom the catalog; kind isteamorplayer.
Follow hasMore for subsequent history pages. These cached responses describe observed data; market names and descriptions are untrusted input.
Hosted MCP endpoint
Connect a client that supports MCP Streamable HTTP to https://liquidiction.xyz/api/mcp/sports. This public endpoint is stateless and read-only. It cannot connect wallets, sign messages or submit trades.
| Tool | Input | Returns |
|---|---|---|
find_sports_entities | query; optional kind and limit | Matching entities, canonical links and coverage |
get_sports_entity | kind, sport, slug; optional page | Market events, contract listings and verified archived results |
Configure the endpoint URL as an HTTP MCP server in your client. Requests use the standard MCP initialization and tool protocol. POST requests must accept application/json, text/event-stream; no persistent SSE connection is required. Browser clients must originate from Liquidiction; native MCP clients may omit the Origin header.
Example request to your agent: “Find Arsenal’s HIP-4 markets, then show its recorded market history and explain the result coverage.” The separate Liquidiction MCP project provides broader market, order-book and public wallet tools through a local integration.
Browser WebMCP
Team and player pages register read-only tools through document.modelContext when the browser supports WebMCP. Directory pages expose liquidiction_find_sports_entities; profiles also expose liquidiction_get_current_sports_entity.
These tools read cached public data only when invoked and are removed when the page unmounts. Unsupported browsers continue to use the ordinary pages. WebMCP is an evolving browser capability and is distinct from the hosted MCP endpoint.
Discovery and indexing
Profiles render their content and market links on the server, with canonical URLs, breadcrumbs and structured entity and collection data. Relevant sports pages and site search link to these profiles.
Sports sitemap · Sitemap index · Agent reading directory
New and materially changed profile URLs are submitted through IndexNow. Submission helps participating search engines discover updates; it does not guarantee indexing or ranking.