Organizations
An organization is the account that owns your API keys, your credits and your usage history. Every Renidly account has one from the moment you sign up — if you're working solo you may never need to think about it.
What belongs to an organization
Everything that costs money or grants access lives on the organization, not on the person who created it. That means people can join and leave without your integrations noticing.
| Belongs to the organization | Belongs to you personally |
|---|---|
| API keys | Your email and password |
| Credit balance | Your role in each organization |
| Rate limit | Which organizations you belong to |
| Request logs and analytics | |
| Payment method, invoices and billing history |
One balance, many keys
An organization has a single credit balance. You can issue several API keys — one per environment or service is the usual pattern — and every one of them draws from that same balance. There is no per-key wallet to top up and no moving credits around.
- Create a key per environment:
production,staging,ci. - Revoke a leaked key without touching the others.
- Pay once — every key keeps working.
Keys are managed from API Keys. See API Keys for creating, rotating and revoking them.
Where your rate limit comes from
The per-minute request limit is a property of the organization, so it is the same for every key it owns. There are two ways it gets set:
| Mode | How the limit is decided | Who has it |
|---|---|---|
| Standard | Scales with your credit balance — see Rate Limits & Credits. | Every account by default. |
| Negotiated | A flat, agreed limit that does not change with your balance. | Accounts on a custom contract. |
You can read the limit that applies to a key at any time from the Tier Info endpoint. Standard accounts report the tier ladder; enterprise accounts return null tiers and a top-level limit_per_minute. Build your client-side limiter against whichever is present rather than hard-coding a number.
Working with more than one organization
You can own up to three organizations and join any number of others by invitation. A common split is one per client, product line, or legal entity — each with its own keys, credits and invoices, none of which are shared between them.
When you belong to more than one, a switcher appears in the dashboard header. The organization shown there decides what the whole dashboard is acting on.
Free credits
The starter credits are granted once, to the organization created with your account at signup. Additional organizations you create later start empty, as do the personal organizations of people who join by invitation.