API keys, usage and billing

Run the integration with keys you can rotate in seconds and limits you can see.

Keys

Shown once, prefixed fd_, sent as a Bearer token. Revoke one and it stops working on the next request.

Usage

Requests this month and this minute against the plan, the same numbers every 429 body carries.

Agents

The MCP server takes the same key; keyless tools let an agent read a delayed sample and start a signup.

What it returns now

{
  "data": [
    "..."
  ],
  "meta": {
    "plan": "free",
    "delay_seconds": 300,
    "as_of": "2026-11-06T22:55:00Z",
    "source_status": "ok",
    "remaining": {
      "month": 97,
      "minute": 19
    }
  }
}

Endpoints and parameters

Keys live at /dashboard/keys; the MCP server is https://fanduelapi.com/api/mcp and takes the same key. See the MCP page and connecting an agent.

Code

https://fanduelapi.com/dashboard/keys

{
  "mcpServers": {
    "fanduelapi": {
      "url": "https://fanduelapi.com/api/mcp",
      "headers": { "Authorization": "Bearer ${FANDUEL_API_KEY}" }
    }
  }
}

Keys look like fd_.... Keep one in the FANDUEL_API_KEY environment variable on your server, never in browser code. Every response's meta says which plan answered, how far behind it is and how fresh the collection is.

Which plans include it

• FreeIncluded
• DeveloperIncluded
• ProductionIncluded
• ScaleIncluded

Read from the plans on the pricing page. Every request counts against the monthly and per-minute allowance; request quotas explains how.

Works well with

• CoverageKnow what the feed holds before you build on it, and show users exactly how fresh it is./api/v1/coverage
• Webhooks and streamStop polling: take each change the moment it is collected, on a connection or at your URL./api/v1/stream
• Props feedRead the whole player prop board in one call, already normalised, with where each line opened./api/v1/props