Managing the stack

The operational tasks an administrator does to run Coco Router — most from the web consoles, a few at the platform level. Coco Router is fully managed, so the console tasks are yours and the infrastructure tasks are handled by Cocolevio.

From the consoles (no infrastructure access needed)

Everything here is done in the admin UI at router.cocolevio.com, signed in with your admin credentials.

Adjust routing

Open the Auto-Switch Control Panel to change which models serve each complexity tier, or to change the classifier model. Edit the model pool — one model id per line, top line is highest priority — and click Save changes. It applies to the next request, with no restart. This is the single most common change: swapping in a newer or cheaper model as it appears.

Mint, cap, and revoke keys

From Virtual Keys, create a key per application or teammate. Give app keys an alias starting with auto and a sensible budget. From the Dashboard you can block/unblock, change a budget, or delete any key — these actions prompt for the admin password. Revoking a key never touches provider credentials, so it's safe to rotate freely.

Monitor spend and health

The Dashboard shows spend per day, per key, and per model, with failed-request counts and budget bars. The Logs page gives per-request depth. Check these to catch a key burning budget or a provider erroring before it becomes a bill.

Verify a change

After any routing change, open the AI Console and send a simple / coding / reasoning prompt. The routing log confirms the tier, the model chosen, the latency, and the cost — using the exact path production apps use.

Platform-level tasks (handled by Cocolevio)

Some changes touch the gateway's server configuration and are done by a Cocolevio administrator, not from the consoles:

  • Activating a new provider. A provider's models go live once its API key is added to the gateway configuration. Send the request (and the key, securely) to your Cocolevio administrator — the provider's entire catalog becomes callable and usable in tier pools.
  • Wiring Amazon Bedrock. Bedrock authenticates with AWS credentials and requires per-model access to be granted in AWS. See Amazon Bedrock for what's needed on the AWS side.
  • Scaling, upgrades, and backups of the gateway itself.

If you're not sure whether a task is a console task or a platform task, the rule of thumb is: anything about routing, keys, or monitoring is yours; anything that adds a new provider credential or changes the deployment is Cocolevio's. Reach us at cocolevio.com/contact.