> Full Neon documentation index: https://neon.com/docs/llms.txt

# Organization spend limits, snapshot storage consumption API, One-click Neon MCP setup for Kiro, durable AI agents, and agent-readable docs

## Organization spend limits and email alerts

You can now set a **monthly spending limit** for your organization from the **Billing** page in the Neon Console. When spend reaches **80%** and **100%** of that limit, Neon sends email alerts to organization admins. Spend is evaluated about every **15 minutes**, and reminder emails continue weekly until you raise the limit or the billing cycle resets.

![Spending limit card on the Billing page](https://neon.com/docs/changelog/spending_limit.png)

When you enable a limit, you enter a dollar amount and choose threshold behavior. Email alerts are available now. In a future release, you'll be able to suspend computes automatically when the limit is reached.

![Enable spending limit dialog in Neon Console](https://neon.com/docs/changelog/set_spending_limit.png)

To get started, see [Spending limits](https://neon.com/docs/introduction/spending-limit).

## Monitor snapshot storage consumption

Building on the recent [snapshot size fields added to snapshot API responses](https://neon.com/docs/changelog/2026-04-17#snapshot-api-responses-include-storage-size-fields), the [Retrieve project consumption metrics](https://api-docs.neon.tech/reference/getconsumptionhistoryperprojectv2) endpoint now supports a **`snapshot_storage_bytes_month`** `metrics` parameter. Use it to track monthly snapshot storage in your project-level consumption reporting.

Example response body (excerpt):

```json
{
  "timeframe_start": "2026-02-05T00:00:00Z",
  "timeframe_end": "2026-02-06T00:00:00Z",
  "metrics": [
    { "metric_name": "root_branch_bytes_month", "value": 758611968 },
    { "metric_name": "instant_restore_bytes_month", "value": 983488 },
    { "metric_name": "snapshot_storage_bytes_month", "value": 0 }
  ]
}
```

**Note: Snapshot billing reminder**

Snapshot storage billing starts **May 1, 2026**. Until then, snapshots remain free during the beta period. See [Backup & restore](https://neon.com/docs/guides/backup-restore) and [Plans](https://neon.com/docs/introduction/plans) for pricing details.

For the full list of metrics, see [Querying consumption metrics](https://neon.com/docs/guides/consumption-metrics).

## One-click Neon MCP setup for Kiro

The [Neon MCP Server](https://github.com/neondatabase/mcp-server-neon) now supports an **Add to Kiro** badge for one-click MCP setup. Thanks to [Anil Maktala](https://github.com/AnilMaktala) for the contribution.

[https://kiro.dev/launch/mcp/add?name=Neon&config=%7B%22url%22%3A%20%22https%3A//mcp.neon.tech/mcp%22%7D](https://kiro.dev/launch/mcp/add?name=Neon\&config=%7B%22url%22%3A%20%22https%3A//mcp.neon.tech/mcp%22%7D)

**Tip: Did you know?**

Neon is also a **Kiro Power**. See [Neon Is Now a Kiro Power](https://neon.com/blog/just-launched-neon-is-now-a-kiro-power) for details.

## Build durable agents with Pydantic AI, DBOS, and Neon

Multi-step agents depend on LLMs and tools that can time out, rate limit, or fail mid-run. A practical pattern is **durable execution**: checkpoint progress in **Postgres** so a workflow can resume after a crash or retry without redoing expensive steps from scratch. **DBOS** provides that durable execution layer, **Pydantic AI** structures agent logic and tool orchestration, and **Neon** backs the database so checkpoint state lives in serverless Postgres that scales with your workload.

For a full walkthrough with a working example, see [**Building Durable AI Agents with Pydantic AI, DBOS, and Neon**](https://neon.com/guides/pydantic-ai-dbos-neon).

## Making Neon docs work for AI agents

We've been optimizing our docs for AI agents. The post [**Agents grew up, so did our docs**](https://neon.com/blog/agents-grew-up-so-did-our-docs) covers what worked, what didn't, and what we're still figuring out. It includes findings from a scan of 250+ doc sites, plus details like our MDX-to-Markdown pipeline, content negotiation (serving Markdown to agents or by appending `.md` to any doc URL), agent-aware 404 handling, and a restructured [`llms.txt`](https://neon.com/docs/llms.txt) index.