Skip to main content
You rely on Natural to run agents, hold funds in wallets, and move money, so the platform is built to stay available and to behave predictably when something fails. This page covers how we run the service and how the API responds under failure.

​
Infrastructure

Natural runs on AWS across multiple availability zones and is served through a global CDN. If an instance or an entire availability zone fails, traffic shifts to healthy capacity automatically.

​
Data

Your data lives in Amazon Aurora PostgreSQL, running with a primary and a replica across availability zones so the database survives the loss of any single zone. It is encrypted at rest with AWS KMS and backed up automatically. For how data is encrypted and protected, see Security.

​
Behavior under failure

The API is built so that a failure or a retry never leaves your data in the wrong state, whether you are creating an agent, funding a wallet, or sending a payment.

​
Idempotency

Any operation whose accidental repetition would matter, like funding a wallet or sending a payment, takes an Idempotency-Key. Retrying with the same key never runs the operation twice, and the recorded outcome, success or failure, replays for 48 hours. See Idempotency.

​
Retries

Transient failures are safe to retry with exponential backoff. A 429 response carries a Retry-After header, and 5xx responses and network timeouts can be retried under the same idempotency key. See Rate limits.

​
Webhooks

Events are delivered at least once from a durable queue. Each event is retried up to seven times over roughly a day with jitter, times out after 30 seconds per attempt, and carries a stable webhook-id so you can deduplicate. An endpoint that fails five events in a row is disabled until you re-enable it. See Webhooks.

​
Compatibility

The Natural API is additive. We add fields and endpoints, but we do not remove or repurpose the ones you already depend on. See Backwards compatibility.

​
Status

Live service status is published at status.natural.com, covering the API, Dashboard, MCP, and Webhooks. Subscribe there to be notified of incidents.
  • Idempotency - Safe retries for mutations
  • Webhooks - Event delivery and verification
  • Security - How we protect data and control access