Connect an agent to Lumify's hosted, read-only market-data API via MCP or REST — sportsbook odds, historical line movement, and public betting splits (bets% / handle%). This is market data only: no predictive intelligence attached — see the sibling lumify-bet-intelligence skill (also in lumifyai/sports-intelligence-skills) for that layer.
This skill installs no code and runs nothing locally. It teaches the agent how to get a key, connect an MCP client (or call REST directly), and pull odds/splits for an event it already has an id for.
Read-only market data — not advice. Outputs are informational. Not betting, trading, financial, or investment advice.
get_player_propslumify-bet-intelligence (get_intelligence / list_ev / list_forecasts) for thatlumify.ai (MCP over HTTPS, or REST)npx (Node.js)Ask before setting up a metered MCP or persisting a key. Never ask the user to paste an API key into chat.
LUMIFY_API_KEY in the environment or the host's MCP secret store — do not hardcode itMCP — remote Streamable HTTP (Cursor, Claude Desktop remote, most hosts):
{
"mcpServers": {
"lumify": {
"url": "https://lumify.ai/mcp",
"headers": { "Authorization": "Bearer lmfy-YOUR_KEY" }
}
}
}
MCP — stdio bridge:
{
"mcpServers": {
"lumify": {
"command": "npx",
"args": ["-y", "@lumifyai/mcp"],
"env": { "LUMIFY_API_KEY": "lmfy-YOUR_KEY" }
}
}
}
REST (no MCP host, or scripting directly):
curl "https://lumify.ai/v1/events/EVENT_ID/odds?bookmaker=all" \
-H "Authorization: Bearer lmfy-YOUR_KEY"
If your host supports MCP tool filtering, scope this skill to: get_odds, get_odds_history, get_splits, get_player_props (plus list_events/query_events/estimate_cost to find event ids and budget first).
lumify-live-scores skill's list_events/query_events, or call them directlyestimate_cost (always free) before spending credits, especially with bookmaker=allget_odds (defaults to bookmaker=pinnacle, 1 credit; all or a comma-separated list is still 1 credit; default is main lines, is_main=true)get_odds_history for past snapshots up to a limit, each with its own timestampget_splits for the consensus split plus a per-bookmaker breakdownget_player_props for mains + live box progress. Catalog: https://lumify.ai/docs/player-props.md. Other sports return HTTP 400.available field before assuming a failureavailable: false, or a 402/400), say so explicitly rather than presenting a guess as a confirmed lineUser request: "What's the current line on tonight's Lakers game, and has it moved?"
Inputs: a team/date query resolvable to an event id (e.g. "nba lakers tonight")
Expected result: Agent finds the event id via query_events, calls estimate_cost, then get_odds
(current line) and get_odds_history (movement), and summarizes book, line, and movement
direction with timestamps — no "bet this" language. (Illustrative; not a captured transcript.)
get_splits is populated for MLB, NBA, NHL, and NFL; other sports may report unavailableget_player_props is NFL/NCAAF/NBA/NCAAB/NHL/MLB/soccer only; get_odds stays moneyline/spread/totals and never returns propsinsufficient_credits — treat as a hard stop, not a retry conditionrisk: safe); no writes, no bet placement, no trade executionlumify.ai is required; no other external recipientslumifyai/sports-intelligence-skills, skills/lumify-odds/SKILL.md, pinned at commit 694da3d0d1efc32da1425a9a931c812957b3c1b6lumify-live-scores (event/score lookup, used to resolve event ids), lumify-stats (raw box-score stats), lumify-bet-intelligence (predictive EV/forecast layer)