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

# Billing and plans

> Manage your Aixy subscription and review organization entitlements.

**Billing** shows your organization's current plan, available plan features, and capacity.
The Owner manages the subscription. Provider inference usage continues to belong to the upstream
accounts connected in [Providers](/gateway/providers).

## Review or change a plan

1. Open **Billing** from the account menu as the organization Owner.
2. Review **Your plan limits** for used and remaining monthly calls, configured MCP connections,
   and analytics retention. Usage loads when you open Billing; use **Refresh usage** to update
   the reading. Enterprise analytics retention is shown as **Custom**.
3. Use **Continue with Stripe** for an available checkout, or the Enterprise contact path for an
   agreed subscription.
4. Return to Billing and confirm the effective plan after the subscription updates.

Use the displayed checkout and agreement for current pricing. Use **Manage subscription** to
open the billing portal for an existing customer, including supported subscription changes.

## Separate subscription and model spend

[Aixy budgets](/costs/budgets) control model requests using their cost evidence and configured
limits. They do not change your subscription or your provider's account-level billing controls.
Use Cost control for request attribution and the provider's billing records for invoice totals.

Review capacity before inviting a larger team or creating resources. Available reporting history
follows the effective plan. Complete the applicable [Data processing](/administration/data-processing)
setup separately from subscription management.

## Starter allowances

Starter includes five days of analytics, up to three MCP server connections,
5,000 remote MCP tool calls and 20,000 model requests per month. Monthly allowances
are shared across the organization and reset at 00:00 UTC on the first day of each
calendar month, independently of your billing date.

Aixy tool search, discovery and connection helpers do not consume MCP tool calls.
Executing a remote tool through the execute helper counts once. Model requests
include Playground and streaming; routing retries and fallbacks count as part of
the original request. Provider failures after admission still consume that request.
An exhausted monthly allowance blocks new executions until reset or a plan upgrade.
The five-day analytics window does not reset monthly consumption.

The connection allowance counts configured MCP servers across projects, including
disabled servers. You can edit or delete connections at capacity. Existing connections
are kept if a plan change puts your organization above its allowance; remove connections
before adding new ones. Pro and Enterprise have no hard monthly plan request cap.

Monthly consumption comes from the quota counters, independently of analytics history.
An unavailable counter is shown as **Usage unavailable**, not as zero. Enterprise has no standard
monthly request cap. Pro shows recorded model requests and estimated service overage for its
subscription period, with any pending reporting identified separately.

## Pro subscription and overage

Pro is EUR 50 per organization per month, with 250,000 model requests included and
EUR 0.00009 per additional model request. MCP tool calls are unlimited, do not consume the model
allowance and incur no Aixy usage charges. Provider inference costs and applicable taxes are separate.
The included allowance follows your subscription period rather than the first day of a calendar month.

Billing shows recorded model requests, the included allowance and estimated overage. Recording
and reporting are asynchronous; **Refresh usage** retrieves the latest available reading. The
Stripe invoice determines the final amount. Records are independent of the analytics retention
window, and missing historical usage is not reconstructed from analytics.

Use **Continue with Stripe** to subscribe. If the billing account is still being prepared after
registration, retry shortly. The subscription includes the base fee and metered overage together.
Use **Manage subscription** to review payment details and invoices. If a payment fails, the
organization Owner receives a notification when transactional email is configured.


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