Billing and API keys
Plans control how many sites, audits, chat messages, and AI tokens your account can use. API keys are for agent and MCP access.
Plans
| Plan | Price | Sites | Audits | Chat |
|---|---|---|---|---|
| Pro | $20/month | 10 | 50/month | 200 messages/month |
| Business | $199/month | 50 | 200/month | 1,000 messages/month |
Business raises the monthly token budget from 500K to 2M and is better for teams, agencies, and accounts that need more sites, audits, or chat volume.
Usage limits
nimo tracks sites, audits, chat messages, and token usage. If you hit a limit, upgrade or wait for the monthly reset. Limits keep the agent useful without surprise AI spend.
Current public billing is built around Pro and Business. If you have a comped account, your limits may be handled separately.
API keys
API keys power the nimo MCP server. Keys:
- Start with
nimo_. - Are shown only once.
- Are stored as hashes.
- Can be revoked from Settings.
- Are limited to five active keys per user.
- Require an active paid or comped account for bearer auth.
Create the key
Go to Settings, choose API keys, and create a named key for your client.
Store it safely
Put the key in the MCP client config or a secret store.
Use bearer auth
Send it as Authorization: Bearer nimo_YOUR_KEY.
Keep keys safe
Use one key per agent or environment. Revoke keys when a laptop, teammate, project, or client no longer needs access.
MCP sanity check
Use nimo MCP to list my sites, then read the latest audit for the site with the worst mobile performance.
Create an API key
Use API keys only for agents and automations that should read your nimo data.