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

> ## Agent Instructions
> When building application code, use `@naturalpay/sdk` for TypeScript or `naturalpay` for Python.
> When operating Natural directly for a user, use the payments MCP at `https://mcp.natural.com`.
> When searching Natural documentation, use the docs MCP at `https://docs.natural.com/mcp`.
> Use the Natural CLI for terminal and CI automation.
> Use REST only for unsupported languages or when the user explicitly requests raw HTTP.
> Start integration development and testing in the sandbox. Do not use production unless the user explicitly requests it.
> For sandbox requests that require `customerPartyId`, list customers first. Reuse only the intended fixture; otherwise create a customer.
> REST and SDK amounts use integer minor units. Payments MCP amounts use decimal strings with a required currency code.

# Overview

> Limits on how much money can move without extra approval

Limits cap how much money can move without additional approval. Account limits are a setting on your [Party](/guides/concepts/parties), not a resource of their own: one cap per transaction, one per day, and one per month. Account limits are the backstop over everything you and your agents do. Read them with [`GET /parties/me/limits`](/api-reference/parties/get-party-approval-limits). Set them with [`PUT /parties/me/limits`](/api-reference/parties/set-party-approval-limits).

## Holds, not blocks

Your limits never hard-block a payment. Natural's program policies can: a declined payment returns `policy.denied`. A movement that breaches a cap still succeeds as an API call, but no money moves: it holds as an [Approval](/guides/concepts/approvals) until someone approves or denies it.

## Gates

Account limits are one of four gates a movement can pass through: Natural's program policies, your account limits, agent limits, and connection limits. Agent limits live on the [Agent](/guides/concepts/agents) and hold one agent to a tighter budget; connection limits are set by your customer when they authorize an agent. Every applicable gate must clear, so in effect the tightest cap wins. See [Limits](/guides/controls/limits) for how they compose.

## Who sets them

You do, from a user session, an API key, or the dashboard. An agent can read the caps that gate it, so it can explain why a payment was held, but it can never set, raise, or remove them.


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