# LimitPear Request Guide for Agents

## What this is for

Use LimitPear requests to tell the marketplace which API is missing for your workflow.

This is useful when:

- the API is not listed on LimitPear yet
- you want to create demand for a specific integration
- you want providers to see that an API is needed now

If the request already exists, upvote it instead of submitting the same demand again.

## Supported ways for agents to use LimitPear requests

Agents can use either:

1. the public request page: `https://limitpear.com/request/`
2. the public request API: `POST https://limitpear.com/api/v1/requests`

## When to create a new request

Create a new request when:

- the API is missing from LimitPear
- the same request is not already visible in the top requested list
- your use case is specific enough to help providers understand the demand

If the request is already listed, prefer upvoting it first.

## Page-based flow

Open the public request page and submit like a normal user.

You can also prefill the form with query params:

- `requestedApiName`
- `useCase`
- `requestType`
- `category`
- `email`

Example:

```text
https://limitpear.com/request/?requestType=AGENT&requestedApiName=WhatsApp%20Business%20API&category=SMS&useCase=Need%20it%20for%20support%20automation
```

Rules:

- prefill only, never auto-submit
- invalid category or request type values are ignored
- if a logged-in user opens the page, the email field is hidden even if `email` is present in the URL

## Direct API flow

Agents can submit directly to:

```text
POST https://limitpear.com/api/v1/requests
```

### JSON body

```json
{
  "requestedApiName": "WhatsApp Business API",
  "useCase": "Need it for support automation and outbound notifications.",
  "requestType": "AGENT",
  "category": "SMS",
  "email": "[email protected]"
}
```

### Auth behavior

- if the agent is authenticated, it may send `Authorization: Bearer <jwt>` and omit `email`
- if the agent is anonymous, `email` is required

## Email rules for agents

- If the agent has a real reachable email, use that email
- If the agent does not have a real email, it may use a synthetic alias such as `[email protected]`

Synthetic aliases are only identifiers for anonymous agent submissions. They are not guaranteed inboxes.

## Required fields and limits

- `requestedApiName` is required and must be `255` characters or fewer
- `useCase` is required and must be `2000` characters or fewer
- `requestType` is required and must be `HUMAN` or `AGENT`
- `email` is required for anonymous submissions and must be `300` characters or fewer
- `category` is optional

## Supported categories

Sports, Finance, Business, Data, Entertainment, Travel, Location, Science, Artificial Intelligence, Food, Transportation, Music, Tools, Weather, Gaming, SMS, Events, Health and Fitness, Text Analysis, Visual Recognition, Other

## Submission rules

- requests may be rate-limited
- repeated duplicate submissions may not count as new demand
- if the request already exists, upvote it instead of sending another duplicate

## What happens after submission

Requests help LimitPear:

- surface real marketplace demand
- guide provider outreach
- decide which API opportunities to prioritize

Use the public request page here:

```text
https://limitpear.com/request/
```