The organization object

Shape of the Organization resource, plan, credit balance, resource limits.

The Organization resource represents the workspace your API key is scoped to. It carries the plan, the credit balance, the resource limits, and the trial dates.

Object shape

{
  "id": "org_64f1c0ef2ec711ef6dc1dcf",
  "name": "Macha AI",
  "slug": "macha-ai",
  "plan": "pro",
  "status": "active",
  "credits": {
    "total": 50000,
    "used": 12345,
    "remaining": 37655,
    "top_up": 0,
    "reset_at": "2026-07-01T00:00:00.000Z"
  },
  "limits": {
    "agents": null,
    "connectors": null,
    "sources": null,
    "chatbots": 20,
    "scheduled_triggers": 3,
    "custom_tool_slots": 5
  },
  "trial": null,
  "created_at": "2026-05-01T00:00:00.000Z"
}

Attributes

Field	Type	Notes
`id`	string	`org_<24 hex>`.
`name`	string	Display name.
`slug`	string	URL-safe identifier.
`plan`	string	`trial` \| `starter` \| `pro` \| `enterprise`.
`status`	string	Subscription status.
`credits`	object	See below.
`limits`	object	Per-resource caps. `null` means unlimited on the plan.
`trial`	object \| null	Trial dates (`start_date`, `end_date`) or null if not on trial.
`created_at`	ISO 8601	When the org was created.

Credits shape

Field	Type	Notes
`total`	integer	Plan allotment per billing period.
`used`	integer	Consumed this period.
`remaining`	integer	What's left, including any top-up.
`top_up`	integer	Additional credits purchased on top of the plan.
`reset_at`	ISO 8601 \| null	When credits reset (next billing cycle).

What's deliberately not exposed

Chargebee customer IDs / subscription IDs, billing internals stay server-side.
Org-provided LLM API keys, if you've configured BYO keys, they're encrypted at rest and never returned.
Internal flags, super-admin allowlists, beta feature flags, etc.