> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/organizations/billing.md).

# Organization billing

Understand the organization's balance, costs, payments and compute limits.

Each organization has its own balance, payment methods, invoices and billing settings. Usage from its projects, apps and dedicated servers is charged to the organization. Changing who operates an app does not change who pays. Machines in a grid shared from another organization are paid for by the organization that provides them.

Only **admins** can see Billing, invoices, Cost Analysis and the sidebar balance, or manage payments. Other members see a notice when the organization is out of credit and can ask an admin to resolve it.

## Manage funds and invoices

Switch to the intended organization, then open **Organization → Billing**. Admins can add credits, configure auto-reload, manage saved cards, redeem a voucher and inspect transactions. Invoices contain the organization's usage and payments. A single top-up is capped at $500 unless Kinesis raises the cap; for bulk pricing or monthly invoicing, use **Contact Us** on the payment page.

New accounts and organizations don't come with signup credit. A voucher can be redeemed once per person and credits the selected organization. The Discord promotional-credit offer has ended.

Billing notices go to the organization's admins and an optional billing contact configured on the payment page. **Observability → Cost Analysis** shows breakdowns by project, app, provider, region and more over a selected period, in UTC.

## Understand limits and controls

The organization's app-creation and provisioning allowances belong to the organization. Grid quotas are different: each grid can cap the GPUs, apps and running containers held by one person's apps. The app's creator is the person counted, including when another member operates it. Admins are counted unless explicitly exempted.

**Low balance protection** (Servers → **Protection**) hibernates the cloud servers Kinesis provisioned for the organization when the balance is projected to run out within the threshold, and stops the apps on their grids. It is on by default, with a 2-hour threshold. Hibernated servers retain storage charges. **Smart Lifecycle** instead responds to idle machines and wakes them when needed.

Spend estimates include running spot leases. Spot billing excludes periods when a leased machine was offline.

The organization has an allowed negative balance: $0 unless Kinesis has agreed a different limit with you. When the balance reaches it:

* New serverless starts are refused, and running serverless apps stop within the hour.
* Cloud servers Kinesis provisioned for the organization are deprovisioned, which removes them for good, whatever the protection setting. Apps on their grids stop.
* Paid spot capacity pauses. Spot settings are kept, and machines return when the balance covers about an hour of them. Apps can continue on their grids’ other machines.

An organization frozen for a payment problem has its apps stopped and servers hibernated. It cannot start apps, add compute or make payments, and paying does not lift the freeze: contact support. Repeated failed payments or a chargeback can freeze an organization automatically. A frozen personal account can still sign in and look, but its changes are refused in every organization and its API keys and connected apps are revoked. Removing a member does not stop their apps or end their organization's usage charges.

## Automate billing

Pass `?org=<slug>` to REST billing calls or `org` to MCP billing actions. The credential needs billing scopes and its person must be an admin there. A key limited to projects cannot manage organization billing; the costs operation requires an explicit permitted `projectId` and still requires the person to be an admin.

MCP can inspect balances, costs, invoices and ledger history, manage supported saved-card settings, redeem vouchers and configure low balance protection. It cannot buy credits or configure auto-reload. MCP money errors describe the entitlement without payment links; an agent should explain the refusal and leave billing to an admin.

The OpenAI profile omits voucher redemption. Use **Billing** in the portal to redeem a code when connected through that profile.

REST also supports checkout sessions, saved-card top-ups and auto-reload updates. Consult the [Billing API](https://docs.kinesis.network/api/billing.md) for the exact inputs and permissions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kinesis.network/organizations/billing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
