For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
DashboardProduct
DocsAPI ReferenceArchitecture
DocsAPI ReferenceArchitecture
  • Start here
    • What is Panicly?
    • Core concepts
    • Quickstart
    • Component gallery
  • Product workflows
    • Gateway lifecycle
    • Controls and policies
    • Usage and billing
    • Dashboard guide
  • Changelog
    • Changelog
LogoLogo
DashboardProduct
On this page
  • Plans
  • Credits
  • How capacity works
  • Stripe state
Product workflows

Usage and billing

Plans, included requests, credits, and Stripe-backed operations

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Controls and policies

Next

Dashboard guide

Built with
Terminology is still settling

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

PlanInternal keyPriceIncluded monthly requestsProject limitNotes
Freefree$01501OpenRouter path, basic controls, no on-demand usage
Proplus$2050,0001Usage insights, Workspace Audit, model controls, direct OpenAI/Anthropic, launch access to Network Controls and Region Rules
Businessbusiness$325500,0001Team-oriented plan copy, 90-day retention language, priority support, higher limits
Free is useful for evaluation

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

Credits

$15 package

15 credits and 100K credit-backed log allowance.

$30 package

30 credits and 200K credit-backed log allowance.

$45 package

45 credits and 300K credit-backed log allowance.

How capacity works

1

Use included monthly volume

Each workspace plan starts with an included monthly request allowance.

2

Stop or continue at the limit

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

3

Record overage usage

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

Owner-only billing

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

Stripe state

stripe_customer_id
string

Stored on the organization after Stripe customer creation.

stripe_subscription_id
string

Stored on the organization for active subscription state.

plan_tier
free | plus | business

Updated from checkout and webhook flows.

credit_logs_balance
number

Implementation balance that represents continued routing capacity after included volume.