Connect your organization to Big Smooth
Mint the credential Big Smooth runs on, so its model spend bills to your organization's own budget and cap.
Connecting is what makes Big Smooth's model usage yours: it mints a gateway credential on your organization, and every turn Big Smooth takes is then metered and capped against your plan instead of somebody else's.
Only org admins can connect, rotate or disconnect — and, because the same restriction covers reading it, only they can see the connection state.
How to
- 1
Open Developers → Big Smooth and read the cap shown before you connect.
That is your plan's model-spend ceiling, and connecting applies it to your whole organization's gateway traffic — not only to Big Smooth. It is shown first because it is the part with consequences.
- 2
Click "Connect Big Smooth".
The cap is applied first and the credential is only minted if that succeeds. There is no uncapped Big Smooth.
- 3
Copy the credential from the dialog, then run `th auth login` and paste it.
It is shown once. Nothing can retrieve it afterwards — the page only ever shows a mask from then on.
- 4
Connect each additional machine by running `th auth login` on it.
Every machine gets its own credential, so you can see what each one spends and rotating one does not lock the others out. They all appear in the machine list.
- 5
Rotate one machine if its value leaks; disconnect to stop Big Smooth entirely.
Rotating affects only that machine. Disconnecting revokes every machine at once — the spend cap already applied to the org stays.
If something goes wrong
- You lost the credential and there is only a mask on screen.
- Rotate. The value cannot be retrieved by design — rotating mints a new one and shows it once, and the old one stops working straight away.
- The page says the connection is visible to org admins.
- You are not an admin of this organization. Reading the connection needs the same role as changing it, so ask an admin — once it is connected you do not need to do anything.
- Big Smooth starts failing with a quota error.
- Check the spend figure against the cap on this page. The cap covers every gateway key on the organization, so another integration's usage can exhaust it — upgrade the plan or reduce that usage.
- The organization has gateway keys but this page says not connected.
- Expected. Only credentials named for Big Smooth count as a connection; other keys are for your own integrations and are managed on the LLM Gateway page.
- A machine you connected is missing from the list.
- Its credential was revoked, or it was created under a name that is not a Big Smooth one. Re-run `th auth login` on that machine.
- The cap says "lifetime — never resets" instead of a monthly figure.
- That is not a display bug: the ceiling really has no reset window, so the spend against it never returns to zero. Raise it with support rather than waiting for the 1st.