---
title: Rate Limits
description: Understanding the API and MCP usage limits in PromptEasy.
---

To ensure platform stability and prevent abuse, PromptEasy implements rate limiting across all API endpoints and Model Context Protocol (MCP) interactions.

## API Rate Limits

These limits apply to direct interactions with the PromptEasy API.

| User Type / Action | Limit |
| :--- | :--- |
| **Login & Registration** | few requests per minute |
| **Unauthenticated API Access** | 30 requests per minute |
| **Authenticated User API Access** | 60 requests per minute |

## MCP Rate Limits

The Model Context Protocol (MCP) is optimized for higher-frequency interactions from AI agents and development tools.

| Access Method | Limit |
| :--- | :--- |
| **Personal Access Token** | 60 requests per minute |
| **Service Account Token** | 600 requests per minute |

> **INFO**
> **Service Accounts** are designed for high-frequency automation and programmatic access, providing 10x the capacity of a regular user account.

## Exceeding Limits

When a rate limit is exceeded, the API will return a `429 Too Many Requests` status code. The response will include a `Retry-After` header indicating how many seconds to wait before making another request.

### Rate Limit Headers

The PromptEasy API provides standard headers that you can use in your application logic to monitor your remaining quota:

*   `X-RATELIMIT-LIMIT`: The maximum number of requests allowed in the current window.
*   `X-RATELIMIT-REMAINING`: The number of requests remaining in the current window.

These headers are particularly useful for developers building complex integrations to implement pre-emptive throttling.

## Fair Use Policy

While we provide generous limits, PromptEasy reserves the right to temporarily or permanently block accounts that demonstrate patterns of malicious activity or intentional platform destabilization, regardless of whether they stay within the numerical limits defined above.