> ## Documentation Index > Fetch the complete documentation index at: https://docs.recurso.dev/llms.txt > Use this file to discover all available pages before exploring further. # List Cloud Plans > List the Recurso Cloud plan catalog the calling tenant can be on, mirroring recurso.dev/pricing. Returns the catalog of plans Recurso itself offers — Self-Hosted, Cloud and Enterprise — as shown on recurso.dev/pricing. This is Recurso's own pricing for your tenant, not the [plans](/api-reference/plans/list) you sell to your customers. The catalog is static data served from the API so the dashboard and the marketing site never disagree; prices are display strings, not minor-unit amounts, because Cloud is metered as a percentage of tracked volume rather than a fixed charge. Pair it with [Get Billing Status](/api-reference/billing/get-status) to show which tier the tenant is on. ## Parameters This endpoint takes no parameters. ## Example Request ```bash theme={null} curl https://api.recurso.dev/v1/billing/plans \ -H "Authorization: Bearer $API_KEY" ``` ## Response The catalog is returned under a `plans` key (no `data` envelope). ```json theme={null} { "plans": [ { "tier": "self_hosted", "name": "Self-Hosted", "price": "Free", "period": "forever", "free_note": "Unlimited — run it yourself", "features": [ "Every feature, no paywalled add-ons", "All gateways + GST/EU/US tax", "Community support", "MIT licensed" ], "cta": "Get started on GitHub", "recommended": false }, { "tier": "cloud", "name": "Cloud", "price": "0.4% of volume", "period": "usage-based", "free_note": "Free to $10k tracked revenue / mo", "features": [ "Managed hosting + auto-scaling", "Daily backups", "99.9% uptime SLA", "Email support" ], "cta": "Start free", "recommended": true }, { "tier": "enterprise", "name": "Enterprise", "price": "Custom", "period": "", "free_note": "Volume pricing + SOC 2", "features": [ "Priority support + SLA", "99.99% uptime", "SOC 2", "On-prem option" ], "cta": "Talk to us", "recommended": false } ] } ``` ## Fields | Field | Type | Description | | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `plans[]` | array | One entry per plan, in display order | | `plans[].tier` | string | Catalog key: `self_hosted`, `cloud` or `enterprise`. This is a display key only — tenants are not yet assigned to paid tiers, so it does not currently appear as `plan_tier` on [Get Billing Status](/api-reference/billing/get-status), which today is only `trial` or `free` | | `plans[].name` | string | Display name | | `plans[].price` | string | Display price, e.g. `"Free"`, `"0.4% of volume"`, `"Custom"`. A string, not a minor-unit amount | | `plans[].period` | string | Display period qualifier, e.g. `"forever"`, `"usage-based"`; empty when none applies | | `plans[].free_note` | string | The free-usage allowance or headline note | | `plans[].features[]` | array of string | Feature bullets | | `plans[].cta` | string | Call-to-action label | | `plans[].recommended` | boolean | Whether the plan is highlighted as the default choice | ## Errors | Status | Code | When | Fix | | ------ | -------------- | ------------------------------------ | ------------------------------------- | | `401` | `unauthorized` | Missing or invalid API key / session | Send `Authorization: Bearer $API_KEY` | Errors use the standard envelope — see [Errors](/api-reference/errors). ## OpenAPI ````yaml GET /v1/billing/plans openapi: 3.1.0 info: title: Recurso API version: 1.0.0 description: | The Recurso billing engine REST API. Authenticate by passing your API key as a bearer token: Authorization: Bearer Obtain an API key by registering a tenant via `POST /auth/register`. All authenticated endpoints live under the `/v1` prefix. Mutating endpoints support idempotency via the `Idempotency-Key` header. license: name: MIT identifier: MIT servers: - url: https://billing.example.com description: >- Example deployment — substitute the base URL of your own Recurso deployment. security: - bearerAuth: [] tags: - name: System description: Health, version, and API metadata - name: Auth description: Tenant registration - name: Plans description: Product catalog plans - name: Customers description: Customer management - name: Subscriptions description: Subscription lifecycle - name: Invoices description: Invoices, PDFs, and Indian GST e-invoicing - name: Coupons description: Discounts - name: Usage description: Metered usage events - name: Credit Notes description: Customer credits - name: Quotes description: Quote-to-invoice lifecycle - name: Webhooks description: Webhook endpoint management and event feed - name: Analytics description: Revenue analytics - name: Checkout description: Public hosted checkout for invoices - name: Payments description: Payment order creation - name: Inbound Webhooks description: Receivers for payment-gateway callbacks (Razorpay, Stripe) - name: Customer Portal description: Customer-facing portal — magic-link auth and session-scoped data - name: Developer description: API key management - name: Account description: Tenant account settings - name: Finance description: Ledger accounts, entries, reconciliation, and revenue recognition - name: Settings description: Tax (GST) and e-invoicing (IRP) configuration - name: Consents description: Consent records for RBI-compliant recurring billing - name: Referrals description: Customer referral program - name: Gifts description: Gift subscriptions - name: Mandates description: UPI Autopay mandates - name: Offline Payments description: Virtual accounts and manually recorded payments - name: Organizations description: Multi-entity organizations grouping several tenants - name: Accounting description: QuickBooks / Xero accounting integrations - name: Churn description: Churn risk scoring and alerts - name: Cancel Flows description: Configurable retention flows shown at cancellation time - name: Dunning description: Dunning analytics and multi-channel dunning campaigns paths: /v1/billing/plans: get: tags: - Account summary: Managed-cloud plan catalog description: The available managed-cloud plans (mirrors recurso.dev/pricing). operationId: getBillingPlans responses: '200': description: Plan catalog. content: application/json: schema: type: object properties: plans: type: array items: type: object properties: tier: type: string name: type: string price: type: string period: type: string free_note: type: string features: type: array items: type: string cta: type: string recommended: type: boolean '401': $ref: '#/components/responses/Unauthorized' components: responses: Unauthorized: description: Missing or invalid credentials (API key or session cookie). content: application/json: schema: $ref: '#/components/schemas/Error' schemas: Error: type: object required: - error properties: error: type: object description: Structured error detail. required: - code - message properties: code: type: string description: Stable machine-readable error code. examples: - validation_failed - unauthorized - forbidden - not_found - conflict - rate_limited - internal_error - invalid_api_key - key_mode_mismatch - over_refund - invoice_not_paid - invoice_already_paid message: type: string description: Human-readable explanation. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API key description: >- Tenant API key obtained from `POST /auth/register` or `POST /v1/developer/keys`. ````