# Frequently asked questions Source: https://docs.graphops.xyz/platform/faq Find a short answer to common questions about credits, billing, usage, API keys, and team access. Each answer links to the page that owns the full guidance. ## Credits and billing ### What is a credit? A credit is the unit GraphOps uses to meter service usage. Credits belong to the organization, and each service maps work to credits differently, so check the service's usage page before estimating production cost. ### How is the monthly plan priced? You choose how many credits your organization needs each month, in steps of 100M. Each additional 100M costs less than the one before, down to a floor, so your price per million credits falls as your plan grows. See [current plan prices](./billing-and-credits#choose-your-monthly-credits). ### Do credits renew? Plan credits are added each billing period after that invoice is paid; top-ups do not renew. See [credit sources](./billing-and-credits#understand-credits). ### Do my credits expire? Plan credits last until the end of the billing period after the one they were added for, so unused plan credits roll over for one billing period. Top-up credits, automatic top-up credits, and credits granted by GraphOps never expire. See [credit lifetimes](./billing-and-credits#understand-credits). ### Are top-ups subscriptions? No. A top-up is a one-time purchase of credits in steps of 10M, and its credits never expire. Automatic top-ups are also one-time purchases, made for you when your balance falls below the threshold you set. ### Why does a top-up cost more than adding 100M credits to my plan? A top-up costs your plan's average price per million. Adding 100M credits to your plan costs that step's own price, which is lower because each additional 100M costs less than the one before; in exchange, your monthly price rises from your next renewal. Without an active plan, or beyond your plan-price allowance, top-ups cost the higher pay-as-you-go price. See [Buy extra credits](./billing-and-credits#buy-extra-credits). ### Why was I charged while I still had credits? Automatic top-ups charge when your balance falls below your threshold, not when it reaches zero, so your services stay funded. A plan increase charges the difference as soon as you confirm it, and your plan renews each month whatever your balance. Check **Top-up activity** and your invoice history in Billing to see each charge. See [Automatic top-ups](./billing-and-credits#automatic-top-ups). ### What happens after checkout? Checkout shows the price, taxes, billing details, and total before you pay. After payment succeeds, GraphOps updates the organization's plan and credits; refresh Billing to check them. ### How do I complete a payment that needs my action? Billing shows a notice when a plan increase or an automatic top-up needs you to pay or to confirm with your bank. Choose **Continue** on the notice within 24 hours. See [Complete a pending payment](./billing-and-credits#complete-a-pending-payment). ### Do I get a refund when I lower my plan? No. A lower plan size takes effect at your next renewal, so you keep the size, credits, and price per million you have paid for until then. Increases are charged immediately and are not prorated. See [how plan changes work](./billing-and-credits#change-monthly-credits). ### What happens to my credits and Managed Subgraphs after I cancel? Your plan stays active until the end of the billing period, and automatic top-ups turn off right away. After it ends, your final period's plan credits stay usable for one calendar month, and top-up credits never expire. Existing Managed Subgraphs keep running while your balance is positive, then stop without a grace period. You cannot create new ones without a plan. See [Cancel your plan](./billing-and-credits#cancel-your-plan). ### What happens when credits run out? Requests pause as soon as the available balance reaches zero or below, and return `403 Forbidden` with the code `credits_exhausted`. With a monthly plan, running services such as Managed Subgraphs stop when the grace period ends; without one, they stop right away. Topping up above zero restores service automatically, and automatic top-ups help you avoid the pause; see [keep services funded](./billing-and-credits#keep-services-funded). ### Which currency and taxes apply? Prices are in US dollars and shown before tax. Stripe Checkout and each invoice calculate the applicable tax from your billing details, including a business tax ID when you provide one. ### Can I pay by invoice or bank transfer? Not with self-serve billing. Plans and top-ups are paid by card or Link. To discuss invoiced payment or a larger commitment, contact [GraphOps support](./support-and-status). ### Do organizations share volume? No. Each organization has its own plan, price per million, and balance, so usage in one organization does not lower the price in another. ### Where do I manage invoices, taxes, and payment methods? Open **Billing → Settings** and choose the task under **Payment and tax details**. [Billing settings](https://platform.graphops.xyz/organizations/current/billing/settings) See [payment details](./billing-and-credits#manage-invoices-and-payment-details). ## Usage and limits ### Where do I confirm my active limits? Each organization can have up to 50 active API keys and 10 Managed Subgraphs by default, whatever its plan size; support can raise them. Your plan and credit balance are in **Billing**, and current consumption is in **Usage**. Each service's usage page explains its request limits; contact support to confirm organization-specific values before production traffic depends on them. See [organization limits](./billing-and-credits#organization-limits). ### Why is usage not visible immediately? Usage can take a few minutes to appear after requests, streams, or jobs complete. If activity is still missing after a few minutes, check the UTC time range and filters, then contact support with your organization, product, approximate UTC time, and request ID. ### Which time zone does usage use? Hourly and daily totals follow UTC boundaries. Hover over a time to see its full date, time, and time zone, and include both the UTC range and your local time zone when asking about a discrepancy. ## API keys ### Can one API key access multiple services? Yes. When you create a query key, choose every service it should query. You can add or remove services later without changing the key. Keys work only in the organization that created them; use separate keys for each environment and application. See [API keys](/platform/api-keys#edit-a-keys-access). ### Can I limit what an API key can query? Yes. You can limit Subgraphs to specific Managed Subgraphs, Endpoint Aliases, Deployment CIDs, or Graph Network Subgraph IDs, and RPC or Substreams to specific networks. Requests outside a key's limits are refused as forbidden (`403`). See [Limit a key](/platform/api-keys#limit-a-key). ### Can I manage Managed Subgraphs from CI? Yes, with a service account, your organization's identity for automation, CI, and servers that call the GraphOps platform API. Give it the permissions your workload needs, such as staging new versions, reading usage, or retargeting Endpoint Aliases, and store one of its service account keys as a CI or server secret. A service account cannot create keys, make purchases, or change members and invitations, and cannot query data services, so your applications keep using query keys. See [Service accounts](/platform/service-accounts). ### Can I call GraphOps from a browser? Yes, for RPC and Subgraphs. Limit each of those services on the key to allowed origins, such as `https://app.example.com`, so it works only from pages on your website, and to the networks or Subgraphs your frontend queries. Substreams cannot be limited to allowed origins, so keep it off a browser key. A service without allowed origins works from anywhere, and anyone can read a key shipped to the browser, so put only what your frontend calls on that key and use separate keys on your servers. See [Use a key in a browser](/platform/api-keys#use-a-key-in-a-browser). ### Is an API key shown again after creation? No. The plaintext key is shown once; store it in a secret manager or server-side runtime configuration before closing the dialog. ### Which roles can manage API keys? Owners and developers. Billing admins and viewers cannot see or manage API keys or service accounts. ## Team and account ### Which roles can manage billing? Owners and billing admins. Developers and viewers cannot. ### Is there an Admin role? No. Use the owner role for team administration and the billing admin role for payment responsibilities; custom roles are not available. ### How long do invitations last? Pending invitations expire after 7 days. Owners can revoke a pending invitation before it is accepted, or resend a pending or expired invitation to give the recipient another 7 days. ### How do I change my sign-in methods or secure a lost device? Open **Account** from the sidebar or your account menu to manage passwords, passkeys, connected accounts, two-factor authentication, and device sessions. See [Secure your account](./account-and-security). [Account](https://platform.graphops.xyz/account) ## Services and support ### How do I choose a service? Use RPC for node calls, transactions, logs, and chain-state reads; Subgraphs for GraphQL entity reads; and Substreams for ordered streams, backfills, and sink pipelines. See [Choose a data service](/choose-a-service). ### What should I know before updating an Endpoint Alias? Changing its target can change the schema served to every client that uses it. Test schema compatibility, keep the previous Deployment CID available, and plan a rollback before retargeting a production Endpoint Alias. ### Where do I get support or service-status information? [Open the support chat](https://platform.graphops.xyz/organizations/current/overview?support=open) in the platform for organization-specific questions and current incident information. See [Support and status](./support-and-status) for what to include. ## Next steps * [Billing and credits](/platform/billing-and-credits): Choose your monthly credits, add credits, and set alerts. * [Usage and limits](/platform/usage-and-limits): Find which workloads use your credits. * [Support and status](/platform/support-and-status): Get help with anything this page does not answer.