> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> Understand REST v1 limits and retry headers.

# Rate limits

REST v1 and MCP share a durable limit of **60 requests per minute per credential**. Limits remain consistent across application restarts and server instances.

Raw-report REST requests with `read` consume that quota even when they lack
`credit_reports`. They receive `403 forbidden` while quota remains and `429`
when it is exhausted. The bucket is shared with summary reads and does not
change when the caller switches IP addresses.

When the limit is exceeded, the API returns `429` with the normal error envelope and these headers:

| Header | Meaning |
| - | - |
| `Retry-After` | Whole seconds to wait before retrying. |
| `X-RateLimit-Limit` | Requests allowed in the current window. |
| `X-RateLimit-Remaining` | Requests remaining; `0` on a limited response. |
| `X-RateLimit-Reset` | Unix timestamp in seconds when the window resets. |

Wait for `Retry-After`, then retry with exponential backoff and jitter. Avoid parallel retries for the same credential.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.