PipedreamHQ / PipedreamHQ/pipedream
[APP] Lumify Sports Intelligence
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Name of app / service**
Lumify Sports Intelligence — https://lumify.ai
Agent-ready sports intelligence API: real-time schedules, live scores, multi-book odds, line-movement history, public betting splits, and explainable bet confidence across MLB, NFL, NBA, NHL, NCAAF, NCAAB, tennis, and soccer (including MLS, EPL, La Liga, Serie A, Bundesliga, Ligue 1, and UEFA Champions League).
Also exposes a hosted MCP server at `https://lumify.ai/mcp` (Streamable HTTP) for agent clients.
**Link to developer documentation**
- Docs / quick start: https://lumify.ai/docs
- API reference: https://lumify.ai/docs/reference
- API base URL: `https://lumify.ai`
- Auth: API key as a Bearer token — `Authorization: Bearer lmfy-...`. Keys are created at https://lumify.ai/api-keys. Free instant trial keys (no signup): https://lumify.ai/docs/ai
- Suggested credential-validation endpoint: `GET https://lumify.ai/v1/sports` (returns 200 + sports list with a valid key, 401 otherwise)
- Example authenticated call:
```bash
curl "https://lumify.ai/v1/events?sport=nba&status=scheduled&limit=5" \
-H "Authorization: Bearer $LUMIFY_API_KEY"
```
- Free tier for testing, no card required (instant trial key or account trial with credits)
**Is lack of support preventing you from moving forward, or do you have a workaround?**
Yes for Pipedream-native workflows and Pipedream MCP discovery. Today Lumify is usable via HTTP / custom code steps and via its own hosted MCP (`https://lumify.ai/mcp`), but it is not available as a first-class Pipedream app, so it does not appear at mcp.pipedream.com and cannot be used with Pipedream’s managed auth / no-code actions.
**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**
Suggested starting actions (all map to existing REST endpoints):
1. **List Events** — `GET /v1/events` (filters: sport, league, status, date / from / to)
2. **Get Event** — `GET /v1/events/{id}` (optional `include_odds`, `include_intelligence`, `bookmaker`)
3. **Get Odds** — `GET /v1/events/{id}/odds` (optional `bookmaker`)
4. **Get Odds History** — `GET /v1/events/{id}/odds/history`
5. **Get Intelligence** — `GET /v1/events/{id}/intelligence` (explainable bet confidence / probability signals)
6. **Get Splits** — `GET /v1/events/{id}/splits` (public betting splits where available)
7. **Search Events (NL)** — `POST /v1/query` (natural-language event search)
Suggested triggers (if useful after the first actions ship):
1. **New / Updated Scheduled Events** — poll `GET /v1/events` for a sport/league
2. **Odds Movement** — poll `GET /v1/events/{id}/odds/history` for a watched event
Happy to provide a test API key and help QA once the integration is in progress.
Contributor guide
Research direction
Start with Lumify's developer documentation and quick start, especially the authentication flow and the listed REST endpoints. Review how existing Pipedream app integrations expose authenticated actions and polling triggers, then verify the proposed actions with the supplied curl request and a trial API key. Done means Lumify is available as a first-class app with managed authentication and the requested actions discoverable in Pipedream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100