# Billing and credits Source: https://docs.graphops.xyz/platform/billing-and-credits Keep your services funded without surprises. Choose how many credits your organization needs each month, buy extra credits when a workload needs them, and turn on automatic top-ups so a busy period does not pause your services. Every service in your organization draws from one credit balance. [Manage billing](https://platform.graphops.xyz/organizations/current/billing) ## Understand credits Credits measure service usage. Each service charges for different work; use the current [RPC](/rpc/usage-and-limits), [Subgraphs](/subgraphs/usage-and-limits), and [Substreams](/substreams/usage-and-limits) rates to estimate your workload. Credits belong to your organization, not to an API key or a teammate. Creating another key does not create a separate balance. _Plan credits, top-ups, automatic top-ups and grants add credits to one organization balance, and every service draws from it, plan credits first. When the balance runs low, alerts fire and automatic top-ups can add credits; at zero or below services pause, and topping up above zero restores them automatically._ - Monthly plan: Plan credits each paid month; used first, roll over one month. - Top-ups: One-time purchases that never expire. - Automatic top-ups: Added when the balance falls below your threshold. - Grants and adjustments: New-organization grant and support credits. - Funded: Services run and draw usage. - Low balance: Alerts fire at your thresholds; automatic top-ups add credits when on. - Zero or below: Requests pause; with a plan, running services stop after a grace period. - Topped up: Service restores automatically above zero. Your balance can hold credits from several sources, and they last for different periods: | Credits | Where they come from | How long they last | | --------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | Plan credits | Each paid month of your monthly plan, and each increase to your plan | Until the end of the billing period after the one they were added for | | Top-up credits | Top-ups you buy and automatic top-ups | They never expire | | Granted credits | The one-time grant for a new organization, and credits added by GraphOps support | They never expire | GraphOps uses plan credits first, oldest first, and then credits that never expire. Unused plan credits therefore roll over for one billing period. For example, if your plan renews on the 1st, plan credits added on November 1 can be used until January 1. Credits returned to your balance by a usage correction never expire. Billing shows your **Plan credits** beside the balance, including how many expire at the end of the current billing period. If your plan ends, the plan credits from your final billing period stay usable for one calendar month after it ends. If your balance or plan is unavailable in Billing, contact [support](./support-and-status) with the organization and displayed error. An unavailable balance does not mean you have zero credits, and refreshing the page does not create a new billing account. ## Choose your monthly credits Your organization can have one monthly plan, sized in steps of 100M credits. Each additional 100M costs less than the one before, down to a floor, so the more credits you commit to, the less you pay for every credit. Two numbers describe any size: * The monthly price is what your plan renews for each month, before tax. * The price per million credits is your average price for one million credits: your monthly price divided by your plan's credits. While your plan is active, it is also what top-ups and automatic top-ups cost. The list price is the price of the first 100M, applied to every credit. Your volume discount is the difference between that and your monthly price. The first 100M credits cost $39 a month. Each additional 100M costs $1 less than the one before, down to $20. Current monthly plan prices. Prices are shown before applicable taxes; Stripe Checkout shows applicable taxes and the total before payment. Prices as of Nov 14, 2026, 12:11 AM UTC. | Monthly credits | Monthly price | Price per million credits | | --- | --- | --- | | 100M | $39 | $0.390 | | 500M | $185 | $0.370 | | 1B | $345 | $0.345 | | 2.5B | $690 | $0.276 | | 5B | $1,190 | $0.238 | | 10B | $2,190 | $0.219 | Every size from 100M to 10B credits, in steps of 100M, is available. Billing shows the exact price for any size before you subscribe. To start a plan: 1. Select the intended organization. An **Owner** or **Billing admin** opens **Billing → Plan**. 2. Choose a size with the slider, or adjust it 100M at a time with the **−** and **+** buttons. The page starts at the smallest plan, and the labels under the slider show the volume discount at each size. The price reads like a receipt: your credits at the list price, your volume discount, and what you pay each month, with your price per million credits and what the next 100M would add. When your last 30 days used more credits than your current plan adds, the page suggests a size that covers them. 3. Continue to Stripe Checkout. Checkout shows applicable taxes and the total before you pay. 4. Return to Billing after payment. Your plan credits arrive when the payment is confirmed; refresh Billing to check your plan and balance. If a successful payment is still missing after refreshing, contact [support](./support-and-status) with the checkout time and receipt. Plans bill monthly in US dollars, and you pay by card or Link. Free trials are not available. A promotion code for a new plan applies to its first invoice only and does not change your price per million. Top-ups do not accept promotion codes. Each organization has its own plan and price per million. Organizations do not combine their usage to reach a lower price. ### Organization limits Credits are the main constraint on your usage. Two limits apply to every organization, whatever its plan size: | Limit | Default | | ----------------- | ------------------- | | Active API keys | 50 per organization | | Managed Subgraphs | 10 per organization | Contact [support](./support-and-status) to raise a limit for your organization. Request rates and other service limits are on each service's usage page. ### Managed Subgraphs need a monthly plan To create a Managed Subgraph, your organization needs a monthly plan and a positive balance. A plan that is set to cancel still counts until it ends; a plan whose payment needs attention does not. After a plan ends, existing Managed Subgraphs keep running while your balance stays positive, but they stop without a grace period when credits run out. See [Keep services funded](#keep-services-funded). ## Buy extra credits Buy a top-up when a workload needs more credits than your plan adds, or to use GraphOps without a monthly plan. A top-up is a one-time purchase of credits in steps of 10M. It does not renew, and top-up credits never expire. Current top-up prices. Prices are shown before applicable taxes. Prices as of Nov 14, 2026, 12:11 AM UTC. | Top-up price | Price per million credits | Purchase limit | | --- | --- | --- | | Plan price | Your plan's price per million | Up to your plan size each billing period | | Pay-as-you-go price | $0.500 | Up to 2B every 30 days | Each purchase buys credits in steps of 10M, up to 10B at a time. Which price you pay depends on your plan: * **Plan price:** with an active monthly plan, top-ups cost your plan's price per million, up to your plan size in top-ups each billing period. This is your plan-price allowance: on a 2.5B plan, you can buy up to 2.5B credits of top-ups at your price per million each billing period. * **Pay-as-you-go price:** applies without a monthly plan, while a plan is set to cancel, while a plan payment needs attention, and beyond your plan-price allowance. It is higher than the price of the first 100M on a plan, so a plan is always the cheaper way to buy recurring credits. Pay-as-you-go purchases are limited per organization over a rolling 30 days. To buy a top-up: 1. An **Owner** or **Billing admin** opens **Billing → Top-ups**. 2. Choose how many credits to buy, in steps of 10M. The page shows the price per million credits that applies and where it comes from, how much of your plan-price allowance remains this billing period, and the total before tax. 3. Complete Stripe Checkout. The credits arrive when the payment is confirmed, and the invoice appears in your invoice history. When your plan-price allowance is used up, the page shows the pay-as-you-go price before you continue. To keep adding credits at plan prices, [increase your monthly credits](#change-monthly-credits) instead: you pay only the difference now and receive the added credits immediately. A top-up does not settle an unpaid plan invoice. Resolve a payment warning from Billing first; see [Manage invoices and payment details](#manage-invoices-and-payment-details). If a payment to GraphOps is disputed or your card issuer reports it as fraudulent, GraphOps puts new purchases on hold: top-ups, plan increases and automatic top-ups are unavailable, and automatic top-ups turn off. Your plan and existing credits are unaffected. Contact [support](./support-and-status) to resolve the hold. ## Automatic top-ups Keep your services running through a traffic spike without watching your balance. With automatic top-ups on, GraphOps buys credits for you whenever your balance falls below a threshold you choose, up to a monthly spending limit you set. Automatic top-ups need an active monthly plan. An **Owner** or **Billing admin** sets them up in **Billing → Settings → Automatic top-ups**. The **Top-ups** page shows their status and links there. ### Choose your settings The settings read as one sentence: when my balance falls below a threshold, add a number of credits, up to a monthly spending limit. | Setting | Allowed values | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Top-up threshold | A multiple of 10M credits, from 10M up to your monthly plan credits. | | Credits per top-up | Steps of 10M, from 10M up to your monthly plan credits. | | Monthly spending limit | Before tax. At least the cost of one top-up, and at most your monthly plan price during your first three paid months, then three times your monthly plan price. Contact support to raise it further. | Billing suggests a threshold from your recent peak usage and a limit equal to your monthly plan price. Keep the threshold well above zero: usage is recorded after it happens and a payment takes a little time, so a higher threshold lets new credits arrive while your services are still funded. Each automatic top-up costs its credits at your price per million, plus tax. The price follows your plan size: if a renewal changes your price per million, later automatic top-ups use the new price and GraphOps emails you before they do. ### Turn on automatic top-ups 1. Enter your settings. The panel shows the cost of each top-up and the most you could pay this billing period, including your plan. 2. Read the authorization statement. It names the threshold, the amount, your current price per million, the spending limit, and how to turn automatic top-ups off. 3. Continue to Stripe Checkout and authorize a card or Link for automatic charges. GraphOps uses this payment method only for automatic top-ups; your plan keeps its own default payment method. 4. Return to Billing and check that automatic top-ups are **On**. If your balance is already below the threshold, the first automatic top-up runs as soon as you finish, and the panel tells you before you authorize. Changing the threshold or the credits per top-up, or raising the limit, asks you to accept the updated statement. Lowering the limit does not. To use a different card, authorize again. A top-up that hasn't been charged yet always follows your current settings, so a change you save just before the charge applies to it. ### What happens when your balance falls below the threshold * GraphOps charges one automatic top-up to the authorized card. Your card statement shows `GRAPHOPS TOPUP`. * If your balance is far below the threshold, for example negative after a burst, the top-up adds enough 10M steps to bring it back to at least the threshold. * One automatic top-up runs at a time. If your balance is still below the threshold after it is paid, another follows. * A top-up that would take this billing period's automatic top-ups over your spending limit is reduced to the largest number of 10M steps that fits. When no 10M step fits, automatic top-ups stop until your next billing period. Owners and billing admins receive a warning when automatic top-ups reach 80% of the limit, and a notice when the limit stops them. * Each successful automatic top-up emails a receipt to the billing email, owners, and billing admins, with the amount, the card, and this period's spending against the limit. You can turn these receipts off in **Billing → Settings → Billing contact**. * **Top-up activity** lists every manual and automatic top-up with its credits, amount, tax, status, and invoice. You can export it as CSV. If automatic top-ups run very often, Billing suggests more credits per top-up or a larger plan. ### When an automatic payment fails * If your bank declines a payment temporarily, GraphOps retries once. Other declines fail right away. * If your bank asks you to confirm a payment, GraphOps emails you. Confirm it within 24 hours; see [Complete a pending payment](#complete-a-pending-payment). After 24 hours, the payment is canceled and treated as failed. * After a failed payment, automatic top-ups pause. The billing email, owners and billing admins receive a notice with the reason and your current balance. Low-credit alerts and the usual behavior at zero credits continue. * Removing the authorized card, or a card update that changes its brand, also pauses automatic top-ups. To resume, authorize a card again in **Billing → Settings → Automatic top-ups**. This turns automatic top-ups back on in one step. ### Turn off automatic top-ups Turn automatic top-ups off in **Billing → Settings → Automatic top-ups** at any time. A top-up that has not started charging is canceled; one that is already being charged finishes. Automatic top-ups also turn off, with a notice to owners and billing admins, when: * your plan is set to cancel or ends; * a payment dispute or fraud warning places a hold on purchases. Billing shows **Held by GraphOps** until GraphOps support reviews it. Turning them back on afterwards needs a new authorization. They also do not run while a plan payment needs attention or while GraphOps has disabled the organization. When a renewal lowers your plan size, any setting above the new maximum is lowered to fit, and you receive a notice. GraphOps never raises your settings automatically. ## Change monthly credits Change your plan size whenever your usage changes. Open **Billing → Plan**, choose the new size, and review the change before confirming it. | Change | When it takes effect | What you pay | Credits | | ----------------------------------------------------- | -------------------- | ------------------------------------------------------- | ------------------------------ | | Increase above the size you have paid for this period | Immediately | The difference between the two monthly prices, plus tax | The added credits, immediately | | Any size up to the size you have paid for | At your next renewal | Nothing today, and no refund | The new size at renewal | An increase is charged to your plan's default card right away. For example, if you have paid for 1B this period and increase to 2.5B, you pay the 2.5B monthly price minus the 1B monthly price, plus tax, and receive 1.5B credits now. From your next renewal you pay the 2.5B monthly price. Your billing date does not change. Large increases ask you to confirm the amount a second time. A decrease leaves your current size, credits, and price per million in place until renewal. Billing shows the new size and the date it takes effect; choose **Cancel scheduled change** before then to keep your current size. At renewal, your new price per million applies to top-ups and automatic top-ups too. GraphOps does not prorate plan changes or refund part of a period. You cannot change your plan while it is set to cancel (choose **Keep my plan** first), while a plan payment needs attention, while an earlier increase is waiting for payment, or for the few seconds while a paid increase is applied. If you increase your plan by mistake, contact [support](./support-and-status) within 24 hours. Support can refund an increase when less than 5% of its added credits have been used. The refund removes the added credits and returns your plan to its previous size. ### Complete a pending payment Billing shows a notice when a plan increase or an automatic top-up is waiting for you to pay or to confirm with your bank. This happens when there is no card on file, or when your bank declines the payment or asks you to confirm it. * Choose **Continue** to open the secure payment page, then pay with another card or confirm with your bank. The credits arrive when the payment succeeds. * Choose **Cancel** to abandon a plan increase. Nothing changes, and you are not charged. * A plan increase that is not paid within 24 hours, or by the end of your billing period if that comes first, is canceled automatically. You can then request the change again. * An automatic top-up that is not confirmed within 24 hours is canceled, and automatic top-ups pause. If you leave Stripe Checkout before paying for a new plan or a top-up, start again from Billing. An unpaid top-up Checkout expires after a short time and releases any plan-price allowance it held. If a purchase reports an error, refresh Billing and check for an updated plan or a pending payment before trying again. If the state remains unclear, contact support with the displayed error and approximate time. * If Billing reports that it is temporarily unavailable, try again shortly. Nothing was purchased. * If a plan increase reports that your billing address needs updating, correct it in **Billing address & tax details** (see [Manage invoices and payment details](#manage-invoices-and-payment-details)), then request the increase again. You were not charged. * If Billing reports that your billing account needs review, contact support. Trying again does not resolve it. ## Cancel your plan Before you cancel, check what changes: * Your plan stays active until the end of the current billing period, subject to available credits. There is no refund for the rest of the period. * Automatic top-ups turn off immediately, and owners and billing admins receive a notice. * Until the plan ends, top-ups cost the pay-as-you-go price, and you cannot change your monthly credits. * When the plan ends, plan credits carried over from earlier periods expire. Plan credits from your final billing period stay usable for one more calendar month. Top-up credits never expire. * After the plan ends, you cannot create Managed Subgraphs. Existing ones keep running while your balance is positive, then stop without a grace period when credits run out. To cancel, choose **Cancel plan** in Billing, review what changes, then confirm the end date in the secure billing portal. Billing shows your plan as **Ending** until the end date. Choose **Keep my plan** before then if you want it to renew. After the plan ends, Billing shows **No monthly plan**. You can keep using your remaining credits, buy pay-as-you-go top-ups, and start a new plan at any time. ## Understand your invoices Every charge produces an invoice in your invoice history. Prices are shown before tax, and tax is calculated from your billing details. | Invoice | What it charges | When | | ------------------ | ---------------------------------------------------------------------------------------------------- | -------------------------------------------- | | First plan invoice | The monthly price of the size you choose | When you subscribe | | Renewal | The monthly price of your renewal size | On each billing date | | Plan increase | The difference between the monthly prices of the new size and the size you have paid for this period | When you increase | | Top-up | Its credits at the price per million shown when you bought it | When you complete Checkout | | Automatic top-up | Its credits at your price per million | When your balance falls below your threshold | Here is how one month could look on a plan that renews on the 1st. Look up the monthly prices in [Choose your monthly credits](#choose-your-monthly-credits). Each invoice adds tax. 1. **November 1:** You subscribe to 500M. The first invoice charges the 500M monthly price, and 500M plan credits arrive. 2. **November 10:** Usage grows, so you increase to 1B. An increase invoice charges the 1B monthly price minus the 500M monthly price, and 500M plan credits arrive immediately. 3. **November 20:** You buy a 300M top-up. Its invoice charges 300 times your 1B price per million. You can buy up to 700M more at that price before December 1. 4. **November 25:** Your balance falls below your automatic top-up threshold, and an automatic top-up adds 300M credits at your price per million. 5. **December 1:** The renewal invoice charges the 1B monthly price, and 1B plan credits arrive. Unused November plan credits stay usable until January 1. ## Get notified before credits run low Set low-credit alerts to help avoid interrupted service. In **Billing → Settings → Low-credit alerts**, an **Owner** or **Billing admin** can configure alerts: 1. Enable low-credit alerts. 2. Add up to five different remaining-credit thresholds. Each is an absolute, non-negative whole number of credits. Suggested thresholds are based on your monthly plan credits; they are editable credit amounts, not percentages that track future plan changes. 3. In **Recipients**, choose who receives alerts: the billing email, active members in selected roles, or both. Enabled alerts need at least one recipient; if none is selected when you save, the requirement appears under **Recipients**. 4. Save the settings and check that the saved thresholds and recipients match your choices. The billing email is selected by default. Deselect it when alerts should reach only members in the selected roles; their addresses stay hidden from one another. Each address receives one email, even if the billing email also belongs to a selected member. If your organization has no billing email, add one in **Settings → Billing contact** so a selected billing email receives alerts. Until then, alerts go only to the selected roles, so choose at least one role. Each threshold alerts once when the balance crosses down to or below it. After you replenish credits above that threshold, it can alert again on a future drop. When automatic top-ups are on, alerts below your automatic top-up threshold rarely fire, because a top-up usually restores the balance first. ## Keep services funded When your available credits reach zero or below, your organization's services are paused unless support has arranged an exception. Requests to your services stop being served right away and return `403 Forbidden` with the code `credits_exhausted`. With a monthly plan, services that run continuously, such as Managed Subgraphs, keep running and accruing their usual charges until the end of a grace period, then stop. Without a monthly plan, or while a plan payment needs attention, they stop right away. While your balance is zero or below, you cannot start or change services. _Requests pause as soon as the balance reaches zero or below. With a monthly plan, running services such as Managed Subgraphs keep running and charging until the grace period ends, then stop; without a plan they stop right away. Topping up above zero restores service automatically unless GraphOps support applied the pause._ | Balance | Requests | Running services | Start or change services | | --- | --- | --- | --- | | Above zero | Served | Running | Allowed | | Zero or below | Paused right away | Keep running with a plan | Blocked | | Grace period ends | Paused | Stopped | Blocked | | Topped up above zero | Restored automatically | Restoration requested | Allowed | Turn on [automatic top-ups](#automatic-top-ups) so credits are added before your balance runs out. Before a large backfill or expected traffic increase, also check your balance, review recent [usage](./usage-and-limits), and add credits if needed. Every member of a paused organization sees a notice at the top of each organization page. An **Owner** or **Billing admin** can top up credits from it; other members are asked to contact one. Billing shows the same pause in detail, including when the grace period ends. Top up enough credits to bring your available balance above zero. Service is restored automatically; you do not need to resume anything manually. A pause applied by GraphOps support is not lifted by topping up; its requests return the code `usage_access_paused` instead of `credits_exhausted`. Contact support instead. If your organization is also out of credits, running services still stop when the grace period ends unless you top up. Owners and billing admins receive mandatory service notices when services are paused and when running services stop, together with the configured billing contact. Turning off optional low-credit alerts or changing their recipients does not affect these notices. Use the grace period end shown in Billing to plan recovery even if you have not received an email. After a top-up or credit allocation, refresh Billing to check the available balance and service status. If the balance is positive but access or indexing remains unavailable, contact support. ### Managed Subgraphs during a pause With a monthly plan, both Current and Next versions keep indexing during the grace period, with their usual indexing charges, even while requests are paused. Without a monthly plan, or while a plan payment needs attention, there is no grace period: indexing stops as soon as your balance reaches zero. You cannot start new indexing, stage an upgrade, or restore indexing while your balance is zero or below unless support has arranged an exception. When the grace period ends, or right away without one, GraphOps requests that your organization's affected Current and Next versions stop indexing. Another organization funding the same deployment does not keep your versions indexing. Indexing charges can continue until disconnection from the indexing service is confirmed. Your Managed Subgraphs, Endpoint Aliases, and version history remain available for recovery. After you top up, GraphOps automatically cancels a credit-related stop request or requests restoration of indexing stopped because of exhausted credits. An operator pause or a resource scheduled for deletion is not restored automatically. If indexing capacity or stored data has been released, restoration may require indexing again. Check [indexing health](../subgraphs/guides/monitor-sync-health) before relying on the recovered data. ## Manage invoices and payment details Open **Billing → Settings** and use **Payment and tax details** to choose the task: [Billing settings](https://platform.graphops.xyz/organizations/current/billing/settings) * **Invoices & receipts:** open invoice history to download plan, increase, top-up, and automatic top-up invoices, or pay an outstanding invoice. You can also open this from the Billing sidebar. * **Payment methods:** open your saved payment methods to add a method, change the default, or remove one. This action is also available in the Billing sidebar. * **Billing address & tax details:** update your legal name, billing address, and tax IDs for future invoices. The **Billing contact** section of Settings controls your organization's billing email, which also receives automatic top-up receipts and, when it is selected as a recipient, low-credit alerts. For a payment warning, use **Resolve payment issue** on the warning, then return to Billing and refresh to check the result. The card you authorize for automatic top-ups is separate from your plan's default payment method. Changing your default payment method does not change it; authorize a card again in **Billing → Settings → Automatic top-ups** instead. Removing the authorized card from your saved methods pauses automatic top-ups. Stripe Checkout collects the billing information needed for your purchase, including a business tax ID when applicable, and calculates applicable taxes before payment. ## Next steps * [Usage and limits](/platform/usage-and-limits): Find which workloads use your credits. * [Team and roles](/platform/team-and-roles): Give a teammate the billing admin role. * [Support and status](/platform/support-and-status): Get help with a payment or balance.