---
title: "Limits and reconciliation"
description: "Admission ceilings, call reuse, UNKNOWN outcomes, and explicit settlement decisions."
---

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

# Limits and reconciliation

<p>Admission limits bound external requests independently from price. A managed call can fail for insufficient credit (<code>402</code>) or for an admission ceiling (<code>429</code>); the two conditions are not interchangeable.</p>
<h2 id="application-limits">Application limits</h2>
<p><code>GET</code> and <code>PUT /v1/applications/{appId}/limits</code> control:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>Accepted range</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>dailyProviderRequests</code></td>
<td>1–100,000</td>
</tr>
<tr>
<td><code>providerRequestsPerMinute</code></td>
<td>1–600</td>
</tr>
<tr>
<td><code>activeServiceInvocations</code></td>
<td>1–100</td>
</tr>
</tbody>
</table>
<p>Each saved service connection also has a positive <code>dailyLimit</code>. The stricter applicable ceiling wins.</p>
<h2 id="reuse-and-idempotency">Reuse and idempotency</h2>
<p>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.</p>
<h2 id="unknown-outcomes">UNKNOWN outcomes</h2>
<p>An ambiguous provider outcome is recorded as <code>UNKNOWN</code> and is never automatically resubmitted. Managed credit remains reserved. Owners review <code>GET /service-reconciliations</code> and post either <code>settle</code> or <code>release</code> to the specific reconciliation ID.</p>
<h2 id="see-also">See also</h2>
<ul>
<li><a href="/operate/credits">Credits and top-ups</a></li>
<li><a href="/operate/troubleshooting">Troubleshooting</a></li>
</ul>

Source: https://help.tooluse.net/operate/limits/index.mdx