Introducing the Platform API
Most teams start in the console. They create a key, try a model in the Playground and check usage by hand. That works until there are a dozen services, three environments and a finance person asking why last Tuesday cost so much. From then on you want the account itself to be code.
The Platform API gives you that. Anything you can do in the Mixlayer console, you can now do over a REST API, with the same Bearer token format you already use for inference.
What it covers
API keys. Create, list, update, rotate and delete keys for your organization. Keys carry scoped permissions, so you can give production a key that can only run inference and keep admin rights for yourself. A new key's secret is returned once, when you create or rotate it.
Organizations and members. Read and update organization settings, manage invitations, and change or remove members.
Usage analytics. Pull the same numbers the Analytics dashboard shows, including request volume, token counts with cached input tokens, errors and latency, and per-request sequence detail. Then put them in your own dashboards.
Billing and spend controls. Read your balance and usage, configure refills and auto-refill, and set spend controls that warn or block when you hit a threshold.
Audit log. List audit log entries for your organization, so you can see who created that key and when.
Models. List the models your organization can use and request access to new ones.
Permissions
Every key has a set of permissions, and every endpoint checks them. Reads need api-read. Changes to keys, members, billing and settings need api-admin. Requesting model access needs api-write. A CI job that only provisions keys doesn't need billing access, and the key it uses shouldn't have it.
Getting started
Create a key with the permissions you need in the console. After that, the console is optional. The Platform API docs have the full endpoint reference and examples.
If there's something you still have to do in the console, tell us.