Organization Setup

Your NemoRouter organization is the top-level entity that owns all resources: teams, API keys, credits, guardrails, budgets, and analytics. This guide covers how organizations work and how to configure yours.

Organization Creation

An organization is automatically created when you sign up for NemoRouter. During the onboarding flow, you'll:

1. Create your account — Sign up with email or OAuth
2. Choose a plan — Select your plan (Pay as you go, Pro, or Enterprise)
3. Create your API key — Get your first sk-nemo- key
4. Invite your team (optional) — Add team members right away

Your organization is assigned a unique UUID that is used consistently across all NemoRouter systems. This same UUID identifies your organization in API responses, billing, analytics, and logs.

Your Organization

An organization is the single top-level tenant created for you at signup. It owns everything — teams, API keys, credits, guardrails, budgets, and analytics — and works the same whether you're a solo developer or a multi-member company. Start solo and invite team members whenever you're ready; there's no separate account "type" to switch between.

Organization Settings

Access your organization settings from Settings in the dashboard sidebar.

General Information

Data Policies

Configure how NemoRouter handles your data:

These policies apply to all requests made through your organization's API keys.

Branding

Customize the dashboard appearance for your organization:

• Logo — Upload your organization logo (displayed in the dashboard header)
• Organization name — Shown in the dashboard and in team member invitations

Organization Structure

Here's how resources are organized within your NemoRouter organization:

Organization
  ├── Members (Owner, Admin, Member, Viewer)
  ├── Teams
  │     ├── Team Members
  │     └── Team API Keys
  ├── API Keys (org-level or team-scoped)
  ├── Credit Balance
  ├── Budgets
  ├── Guardrails
  ├── Prompt Templates
  ├── A/B Tests
  └── Analytics & Logs

Resource Ownership

• Credits belong to the organization and are shared across all keys
• API keys can be org-level or scoped to a specific team
• Budgets can be set at the org, team, or key level
• Guardrails are configured at the org level and auto-apply to all requests
• Members are invited to the organization and optionally assigned to teams

Managing Your Organization

Viewing Organization Details

Your organization ID and current plan are visible in the Settings page. The organization ID is the same UUID used in API response headers (x-nemo-org-id).

Updating Settings

1. Navigate to Settings in the sidebar
2. Update the desired fields (name, slug, logo, data policies)
3. Save your changes

One Organization Per Account

Each account belongs to exactly one organization, shown statically in the dashboard header — there is no org switcher and no switch-org flow. If you need to work in a different organization, create or join it under a separate account.

Plan and Billing

Your organization's plan determines the platform fee charged on credit purchases:

Every feature is available on every plan. The platform fee is charged on top of your credit purchase amount — you always receive 100% of the credits you buy.

Manage your plan and billing from the Billing page in the dashboard.

Danger Zone

The organization settings page includes a danger zone for destructive actions:

• Delete Organization — Permanently deletes the organization and all associated data (keys, teams, credits, logs). This action is irreversible and requires confirmation.

Only organization owners can access the danger zone.

FAQ

Do I need to create my organization manually?

No. Your organization is created automatically when you sign up — during onboarding you just choose a plan, create your first sk-nemo- API key, and optionally invite teammates. It works the same whether you're a solo developer or a multi-member company, so there's no separate account "type" to pick or switch between later.

Can I belong to more than one organization or switch between them?

No. Each account belongs to exactly one organization, shown statically in the dashboard header — there is no org switcher and no switch-org flow. If you need to work in a different organization, create or join it under a separate account.

Who can change organization settings?

Organization owners and admins can edit the general settings (name, logo, and data policies). Renaming the organization slug, managing billing, and deleting the organization are owner-only. Members and viewers can view settings but cannot change them.

How do credits and budgets work across my organization?

Credits belong to the organization and are shared across every API key, so all usage draws from one balance. Budgets are separate spending limits you can set at the org, team, or key level — see Budget Controls for how those ceilings work.

What determines my platform fee?

Your organization's plan (Pay as you go, Pro, or Enterprise) sets the platform fee charged on credit purchases — a flat 4% with no minimum fee on Pay as you go, or 0% on Pro. The fee is charged on top of your purchase, so you always receive 100% of the credits you buy. Every feature is available on every plan; plans only affect the fee and your RPM/TPM limits.

Where do I find my organization ID, and where does it show up?

Your organization ID and current plan are shown on the Settings page. The same ID is returned on your API responses as the x-nemo-org-id header, so you can correlate a request back to your organization in your own logs.

Do guardrails and data policies apply to my whole organization?

Yes. Guardrails are configured at the org level and auto-apply to all requests, and your data policies (retention, data-processing preference, and region) apply to every request made through your organization's API keys. Guardrails can additionally be scoped more tightly at the team or key level on top of the org defaults.

What's the difference between an org-level and a team-scoped API key?

An org-level key draws on organization resources directly, while a team-scoped key is owned by a specific team and is tracked and budgeted under that team. Both spend from the same shared organization credit balance; the scope mainly changes how spend is attributed and which budgets apply. See Team Management for setting up teams.

If I rename my organization or change the slug, do I need to update my code?

Renaming the organization only changes the display name shown in the dashboard and invitations, so your integration is unaffected. The slug is only used in dashboard URLs — it does not change your API key or endpoint, so your application code keeps working unchanged.

What happens when I delete my organization?

Deleting an organization permanently removes it and all associated data — keys, teams, credits, and logs. It is irreversible, requires an explicit confirmation, and only organization owners can access this action in the Settings danger zone.

Next Steps

• Team Management — Add members and configure roles
• Budget Controls — Set spending limits
• Authentication — Create and manage API keys
• Quick Start — Make your first API call