MCP Rate Limits

Tier Limits

The MCP server uses the same tier-based rate limits as the Health Plans API:

Tier	Daily Limit	Reset
Free	100 requests	Midnight UTC
Pro	10,000 requests	Midnight UTC
Enterprise	100,000 requests	Midnight UTC

Each MCP tool call counts as one request against your daily limit.

Rate Limit Headers

Every MCP response includes rate limit information in the headers:

Header	Description
RateLimit-Limit	Maximum requests per day for your tier
RateLimit-Remaining	Requests remaining today
RateLimit-Reset	Unix timestamp when the limit resets (midnight UTC)

Handling 429 Responses

When the rate limit is exceeded, the server returns a 429 status with:

• Retry-After header — seconds until the limit resets
• An upgrade field pointing to the pricing page

Tip

For MCP clients that handle rate limits automatically (like Claude Desktop), the 429 response is transparent — the client waits and retries. For custom integrations, implement backoff based on the Retry-After header.

Rate Limit Identity

• API key auth (op_ tokens): Rate limited by the raw API key
• OAuth auth: Rate limited by user ID (stable across token rotations)

This means rotating your OAuth access token does not reset your daily counter.

Upgrading

If you consistently hit rate limits, consider upgrading to Pro ($29/month) for 100x the daily allowance:

• View pricing
• Manage subscription