Skip to main content
Runs and builds are paid for in Notte credits. The balance is in the sidebar; top-ups and invoices are at console.notte.cc.

​
Who pays

Whoever runs it. The API key on the call resolves a workspace and that workspace’s credits are spent. This is what makes publishing safe: a published API is executable by anyone, and every stranger’s run is billed to the stranger. The same rule applies to secrets, which always resolve from the caller.

​
API keys

Create keys at console.notte.cc. One key identifies one workspace, which is why the credential also decides where an MCP build or run acts. Keep keys server-side.

​
Bring your own key

Model calls made by the build agent can run on your own OpenRouter account. Set it under Settings, then Bring your own key. The key is encrypted at rest, used only at request time, and cannot be read back after saving. Owners and admins only. Watch the balance if you leave schedules running unattended: an hourly API is the one that quietly drains a workspace.