> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.panicly.lol/llms.txt.
> For full documentation content, see https://docs.panicly.lol/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.panicly.lol/_mcp/server.

# Usage and billing

The codebase mixes "requests", "logs", "credits", "credit-backed logs", and "included monthly volume". This page normalizes the user-facing model while preserving the implementation caveat.

## Plans

| Plan     | Internal key | Price | Included monthly requests | Project limit | Notes                                                                                                                        |
| -------- | ------------ | ----: | ------------------------: | ------------: | ---------------------------------------------------------------------------------------------------------------------------- |
| Free     | `free`       |   \$0 |                       150 |             1 | OpenRouter path, basic controls, no on-demand usage                                                                          |
| Pro      | `plus`       |  \$20 |                    50,000 |             1 | Usage insights, Workspace Audit, model controls, direct OpenAI/Anthropic, launch access to Network Controls and Region Rules |
| Business | `business`   | \$325 |                   500,000 |             1 | Team-oriented plan copy, 90-day retention language, priority support, higher limits                                          |

Free can route initial protected traffic through OpenRouter and prove the gateway model without requiring paid direct-provider access.

## Credits

15 credits and 100K credit-backed log allowance.

30 credits and 200K credit-backed log allowance.

45 credits and 300K credit-backed log allowance.

## How capacity works

Each workspace plan starts with an included monthly request allowance.

Free stops at the included volume. Paid plans can continue if credit-backed capacity exists.

Successful overage requests can consume credit-backed capacity and appear in usage surfaces.

Checkout, portal launch, credit checkout, and sync actions are owner-only workspace operations.

## Stripe state

Stored on the organization after Stripe customer creation.

Stored on the organization for active subscription state.

Updated from checkout and webhook flows.

Implementation balance that represents continued routing capacity after included volume.