---
title: "Credits and top-ups"
description: "How managed calls reserve points, settle charges, and obtain more credit."
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.

# Credits and top-ups

Bring-your-own service connections are not billed by AgentMQ. Platform-backed connections spend account-shared points and must reserve enough credit before any provider request.

## Ledger entries

| Kind | Meaning |
| --- | --- |
| `grant` | Operator-issued credit lot |
| `purchase` | Verified self-service credit lot |
| `reserve` | Credit held before a managed invocation |
| `settle` | Successful invocation keeps the reserved allocation |
| `release` | Failed invocation restores eligible reserved credit |
| `adjust` | Reversal such as unused refunded credit |

The UI displays one point per 10,000 USD micros. Read `GET /v1/applications/{appId}/credits` for balance, reservations, expiry, and recent ledger entries.

## Top-up flow

1. `GET /v1/topups/applications/{appId}/quote` returns authoritative packs and `checkoutAvailable`.
2. A signed-in owner may open a Stripe checkout only when `checkoutAvailable` is true.
3. Credit is issued from a verified webhook fact, never from a browser redirect.

Automatic top-up is owner-only, off by default, and requires separate payment-method authorization plus a threshold and monthly cap. Availability depends on server configuration.

## Failure behavior

Insufficient managed credit returns `402` before the provider call. An `UNKNOWN` outcome keeps its reservation until explicit reconciliation; it is not retried with a new call.

## See also

- [Limits and reconciliation](/operate/limits)
- [Errors and retries](/operate/errors)

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