---
title: "Limits and reconciliation"
description: "Admission ceilings, call reuse, UNKNOWN outcomes, and explicit settlement decisions."
image: "https://help.agent.mq/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.agent.mq/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits and reconciliation

Admission limits bound external requests independently from price. A managed call can fail for insufficient credit (`402`) or for an admission ceiling (`429`); the two conditions are not interchangeable.

## Application limits

`GET` and `PUT /v1/applications/{appId}/limits` control:

| Field | Accepted range |
| --- | --- |
| `dailyProviderRequests` | 1–100,000 |
| `providerRequestsPerMinute` | 1–600 |
| `activeServiceInvocations` | 1–100 |

Each saved service connection also has a positive `dailyLimit`. The stricter applicable ceiling wins.

## Reuse and idempotency

Read operations with the same application, credential version, and normalized input may reuse a successful call for five minutes. Write operations reuse only the identical idempotency identity.

## UNKNOWN outcomes

An ambiguous provider outcome is recorded as `UNKNOWN` and is never automatically resubmitted. Managed credit remains reserved. Owners review `GET /service-reconciliations` and post either `settle` or `release` to the specific reconciliation ID.

## See also

- [Credits and top-ups](/operate/credits)
- [Troubleshooting](/operate/troubleshooting)

Source: https://help.agent.mq/operate/limits/index.mdx