Projects & organizations

Organizations

An organization is the billing and access boundary. It owns:

• the plan (and therefore the lane caps),
• API keys,
• members and roles,
• the usage ledger.

API keys are scoped to one organization. A suspended organization’s keys are rejected with 403 ORGANIZATION_SUSPENDED.

Projects

A project is an optional attribution label inside the organization. Use one per app, environment, or team so the usage ledger can separate them. Project IDs are free-form strings up to 128 characters.

Send the project with a header:

LUNAROUTE-PROJECT-ID: my-project

Projects do not change authentication, routing, or lane caps — they only split reporting.

Keys

Create keys in the dashboard. A key is prefixed lr_. Prefer user-scoped keys for tooling that acts on a person’s behalf (for example MCP calls, which are attributed to a person), and service keys for automation.

See Authentication for the header forms.