Platform

Organizations

Organizations let multiple users share a single wallet, API quota, and usage dashboard. Members use their own API keys but all spend from the organization wallet. The organization owner manages members and billing.

How organization billing works

Shared wallet

All member API requests deduct from the organization wallet, not individual wallets. The owner tops up the org wallet centrally.

Subscription on the org

Subscriptions are attached to the organization. Credits are added to the org wallet on each renewal cycle.

Per-member API keys

Each member creates and manages their own API keys. Keys are scoped to the member — revoking a key only affects that member.

Usage attribution

Usage logs track which member (by key prefix) made each request. Org admins see aggregated and per-member breakdowns.

Member roles

Role	Can do
`owner`	All actions. Invite/remove members, manage billing, top up wallet, view all usage, delete the organization.
`admin`	Invite members, view all usage, manage webhook settings. Cannot manage billing or remove the owner.
`member`	Make API calls (deducted from org wallet), view own usage, create and revoke own API keys.

Creating an organization

Go to Dashboard → Organization and click Create organization, or use the portal API:

bash

curl https://api.inferexai.in/portal/org \
  -X POST \
  -H "Authorization: Bearer <session-token>" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Corp"}'

response.json

{
  "id": 12,
  "name": "Acme Corp",
  "wallet_cents": 0,
  "created_at": "2026-01-15T10:00:00Z"
}

Inviting members

Owners and admins can invite members by email. The invited user must already have an InferexAI account. Go to Dashboard → Organization → Members or use the API:

bash

curl https://api.inferexai.in/portal/org/members \
  -X POST \
  -H "Authorization: Bearer <session-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "colleague@acme.com",
    "role": "member"
  }'

Listing members

bash

curl https://api.inferexai.in/portal/org/members \
  -H "Authorization: Bearer <session-token>"

response.json

{
  "members": [
    {
      "user_id": 5,
      "email": "owner@acme.com",
      "role": "owner",
      "joined_at": "2026-01-15T10:00:00Z"
    },
    {
      "user_id": 8,
      "email": "colleague@acme.com",
      "role": "member",
      "joined_at": "2026-01-16T09:30:00Z"
    }
  ]
}

Removing members

Remove a member (owner/admin)

DELETE /portal/org/members/{user_id}

Immediately revokes their membership. Their API keys continue to exist but will no longer have access to the org wallet.

Leave an organization (member)

POST /portal/org/leave

Members can leave at any time. The owner cannot leave — they must transfer ownership first or delete the organization.

Best practices

✓Create separate organizations per client or business unit to isolate billing and usage.

✓Assign the subscription to the organization wallet — individual member wallets are ignored when an org wallet is in use.

✓Use Dashboard → Organization → Usage to see which member is driving the most token consumption.

✓Set a low-balance alert on the org wallet (Dashboard → Settings) — the whole team is affected if it reaches zero.

✓Use member roles precisely: give admin role only to people who need to see all usage data.