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

# Subscriptions

> The Standard plan and custom plans: included data, overage, invoices, failed payments and cancellation.

## Subscribing

On **Billing**, choose **Subscribe** on Standard (or on a custom plan prepared for your project).
You pay by card in a checkout page run by Polar, our payment provider. When the payment
completes, the subscription becomes active and its API key is created; it's shown once on the
billing page.

![Subscription billing: data this period, included amount and overage limit](https://mintcdn.com/my-company-7009db77/AEOzPZjunXHOKyLs/images/dashboard/billing-subscription.png?fit=max\&auto=format\&n=AEOzPZjunXHOKyLs\&q=85\&s=bfe0fa873667586ffd5834189c4df881)

## Included data and overage

| | Standard |
| - | - |
| Price | \$200 per month |
| Included data | 1 TB (10¹² bytes) per billing period |
| Overage | \$0.25 per GB beyond the included data |
| Overage limit | \$50 by default; admins can change it |
| Requests per second | 10, across all chains |

* Usage is counted per **billing period** (monthly, from the day you subscribed) and resets at the
  start of each period.
* The **Billing** page shows the data used this period on a meter, with marks for the included
  amount and the most the overage limit allows.
* Overage is charged per GB on your next invoice.

## The overage limit

The overage limit caps what a project can spend beyond its included data in one period. With the
default \$50, a Standard project can use up to 1.2 TB per period (1 TB + 200 GB at \$0.25).

* Admins change it on **Billing** (**Change**). It takes effect immediately on every chain.
* Set it to \$0 to never pay overage: requests stop when the included data is used up.
* At the limit, requests get `402 overage_limit_reached` until the next period starts or someone
  raises the limit. Refused requests are free.

```json theme={null}
{"error": {"code": "overage_limit_reached", "message": "this project has used the data its plan includes plus its overage limit for this billing period; a project admin can raise the overage limit at https://dashboard.bloklake.com/projects/…/billing"}}
```

## Usage emails

Admins get an email at:

* 80% and 100% of the included data;
* 80% and 100% of the overage limit;
* a failed payment.

## Invoices and payment methods

**Billing → Invoices & payment methods** opens the customer portal, where you can download
invoices and receipts and change the card.

## Failed payments

If a renewal payment fails, the subscription becomes **past due**. The key keeps working for a
**5-day grace period** while you update the payment method. After that, the key is suspended and
requests get `403 key_suspended` until the payment goes through.

## Canceling

**Cancel at period end** on **Billing**. The subscription and its key keep working until the end of
the period you've paid for, then the key is revoked. You can resume before then.

## Custom plans

A custom plan is a private plan for your project with its own price, included data, overage
price and requests per second. Ask at [support@bloklake.com](mailto:support@bloklake.com). It
appears on your **Billing** page as "Prepared for you"; subscribe to it like Standard. Switching
between your plans is prorated on the next invoice.

## Switching from pay-as-you-go

A project pays one way at a time. To move a pay-as-you-go project to a subscription:

1. Delete the pay-as-you-go key on **API keys**. The project stops spending its balance.
2. Subscribe on **Billing**. The subscription comes with a new key.

The remaining pay-as-you-go balance stays on the project; it isn't refunded or converted.

> [!TIP]
>
> To keep a running service up while you switch, create a new project with the subscription,
> deploy its key, then delete the old project's pay-as-you-go key.


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