Using the web app
The web app at app.zabio.ai is where you manage everything around your API calls. The menu on the left leads to each section below, in five groups: Overview (Dashboard), Build (Playground, Models, API Keys), Monitor (Usage, Conversations, Batches), Security & Policies (AI Firewall, Audit Log) and Organization (Billing, Members, Settings). Your own account’s pages are in My Profile, in the menu under your avatar at the top right. Long pages have tabs, and every tab has its own address you can bookmark or share. Owners and admins can change the organization’s settings; members can use them (see Teams and organizations for what each role can do).
A short tour shows you around in five steps: create an API key, make your first call, see it in Usage, protect it in AI Firewall and top up in Billing. When you sign in and have not answered yet, a window on the Dashboard offers it: Start tour, Skip for now (it asks again the next time you sign in) or Don’t show this again. Your answer is kept with your account, so it holds on any browser. Each step opens its page and points at the part it explains; Back and Next move between steps, and Escape or the close button ends the tour. Closing it before the end counts as Skip for now. To see it again at any time, choose Take the tour at the end of the menu.
Organizations
Section titled “Organizations”An organization holds your balance, keys, members and settings. Its name appears in the card at the top of the menu, under the Zabio logo, with the project you are looking at (All projects by default).
- Switch organization or project: click that card and pick another organization, or a project to see only its keys, calls and usage.
- Create an organization: click the same card and choose New organization. If you already own one, Zabio first suggests a project instead: same balance, its own keys and spending caps. Choose Continue to a new organization if you really need a separate balance and billing. A new organization starts on the Free plan, with every model vendor turned on.
- Rename it, or set its default language: Settings, General, under Organization, then Save.
- Choose what happens when the balance runs out: in Settings, General, under When the balance reaches zero, pick Continue on the free tier (100 requests a day on the free models until the next top-up) or Stop all requests until the next top-up, then Save. Your keys and members stay either way.
API keys
Section titled “API keys”Keys are what your code sends with each request. Open API Keys in the menu; it has three tabs: Keys, Projects and Limits. Your first key, named “First key”, was created with your account when you signed up; it counts as one of the Free plan’s two keys, and if you did not keep its value, create another one here.
Create a key: it asks three things, and every other setting starts at its default.
- Pick the project in the card at the top of the menu first: the key is created in the project you are in, or at the organization’s level under All projects.
- Click Create key and give it a Name (for example, “production”).
- Choose its Expiration: Never, In 7 days, In 30 days, In 90 days, or On a date (the key stops working at 00:00 UTC that day). An expired key is refused and shows as Expired; whoever created it gets an email 7 days before.
- Optionally set a Spend limit (USD) and when it Resets: every Day, Week or Month at 00:00 UTC (weeks start on Monday), or Never, a budget for the key’s whole life. Once the key has spent it, its calls are refused until the limit resets. Leave it empty for no limit.
- Click Create, then copy the key when it appears. This is the only time the full key is shown; store it somewhere safe.
The list shows each key’s spend against its limit for the current period, when the limit resets, and when the key expires. The Limits tab puts every active key’s spend limit, requests per minute, tokens per minute and expiry in one table, with Edit on each.
Change a key: click Edit on its row. The panel holds everything: the name, the project (owners and admins), the expiration, the spend limit and its reset, the Scopes (Chat, Embeddings, Conversations: which endpoints the key may call), Requests per minute and Tokens per minute, the Fallback policy (Same vendor only, Any vendor, No fallback), Log request and response bodies (off unless you need the full text of calls kept, stored encrypted for your organization’s retention period and readable by owners and admins), and click Save. Below them, Models chooses which models the key may use, saved on their own.
Prompt caching is not a key setting: Zabio caches every call automatically, and a call that does not want it says so with cache.ttl none.
Rotate a key: click Rotate on its row and confirm with Rotate key. The key gets a new secret and keeps everything else: its name, project, settings, limits, models and history. The old secret stops working at once, so anything still using it starts failing on its next call; put the new secret where the old one was. Copy the new secret when it appears: this is the only time it is shown. A connected app’s key is not rotated here: disconnect the app and connect it again.
Revoke a key: click Revoke on its row and confirm. Calls with that key fail at once, and this cannot be undone. Revoked keys are hidden; tick Show revoked keys to see them.
Projects
Section titled “Projects”Projects group keys and their usage under one balance, so you can separate work (an app, a client, a test environment) without a second organization. Open API Keys, Projects.
- Create a project: click New project, give it a name, and confirm. Then assign keys to it from each key’s Project field.
- Rename a project: click Edit on its row.
- Choose a project’s models: click Models on its row.
- Archive a project: click Archive. Its keys keep working; the project just stops appearing in lists. Tick Show archived to see archived projects.
Members
Section titled “Members”Open Members to see who is in the organization, their role, their monthly quota and what they spent this month.
- Invite someone: click Invite, enter their Email, choose a Role (Member or Admin), optionally set a Quota (USD per month) that caps what their keys can spend, and click Invite. The invitation appears under Pending invites until it is accepted, and can be cancelled there.
- Change a role or quota: click Edit on the member’s row.
- Remove a member: click Remove and confirm. They lose access to the organization; keys they created stay active, so revoke them in API Keys if needed.
An organization always keeps at least one owner.
Models
Section titled “Models”Open Models to choose which models your organization can use. It has three tabs: Catalog, the organization’s models with each model’s price per million tokens, context size and capabilities; Prices, your plan in plain terms; and Allowed models, the models of your whole account.
- Allow a whole provider, including the models it adds later, with the switch next to its name.
- Allow single models with their checkboxes; filter by provider, capability or name, and use Select all or Clear on what the filters show.
- Allow everything the level above allows goes back to the default, including models added later.
- The auto models (
autoand its three lines) have their own checkboxes at the top. - Click Save changes to store what you changed.
- The same picker sets the account’s models (Models, Allowed models, for the account’s owner), a project’s (Models on API Keys, Projects) and a key’s (Models in the key’s Edit panel); see Model access.
- Each vendor shows where it processes requests (for example, the United States, North America, or China for DeepSeek’s own API).
- The
automodels only choose among the models turned on here. - Use your own key (optional) lets you add your own key for that vendor; see Your own vendor keys.
Billing
Section titled “Billing”Open Billing for your balance, payments and everything that moves money. It has four tabs: Balance & Top up, Spend Limits (coming soon; until then each key has its own spend limit in API Keys), Receipts and Credits & Referrals. The full rules are in Billing.
On Balance & Top up:
- Add credits: click Add credits, enter an amount (at least the minimum top-up on the pricing page) and pay in the form on the page. Tick the box to save the card for one-click top-ups and automatic recharge. Your billing details are asked with the first top-up.
- Manage saved cards: under Saved cards, see each card, which one is the default, and click Remove to delete one.
- Turn on automatic recharge: under Automatic recharge, switch on Recharge automatically, set When the balance drops below (USD), Add (USD) (at least the minimum top-up on the pricing page), the Monthly cap (USD) (200 by default) and the Card, then click Save. Each recharge sends you a receipt, and you can turn it off at any time.
- Move credit to another organization you own: under Move credit to another organization, the page shows how much can move now (paid credit at least 7 days old). Promotional, referral and match credit stays where it is.
- Use your own vendor keys: under Vendor keys, click Add key.
On Receipts:
- Edit billing details (name, address and tax ID printed on receipts): click Edit under Billing details.
- See every movement: Activity lists each top-up, charge and adjustment, newest first.
Credits & Referrals holds your match, while you have one, and your referral link; see Referrals below.
Dashboard
Section titled “Dashboard”Until your organization’s first successful call, the Dashboard opens on Make your first call: one request on auto as curl, Python and Node, with your key and the API’s address filled in, and Copy on each. Run one; the box turns green with the model, the latency and the cost of that call, and the figures below appear. If this browser does not hold your first key (you signed up elsewhere, or signed out), Make my key creates one for the code, or, when your plan’s keys are all in use, the box points you to API keys. The organization is named after you at signup; rename it in Settings, General.
The Dashboard shows how your organization uses Zabio. Choose the period at the top right (This month or Last 30 days), or Export CSV to download the figures. The line under the title names the organization, the project chosen in the menu (all projects by default) and the dates.
- A message line at the top, one at a time, only when something concerns you: a key found in public and revoked, credits that run out within a week at this month’s pace, a model your calls used that is retiring, a vendor you call having trouble, or a new Zabio release. Hide puts it away until something new comes.
- Four figures: Spend (the calls and the AI firewall’s charges, what you paid, with the calls and the cost per 1M tokens under it), Saved by routing, Calls (with the share that succeeded and the latency) and Credits (your balance and about how many days it lasts at this month’s pace, with Top up). Saved by routing is what your keys’
autocalls would have cost on each key’s baseline model, at that model’s price when each call ran, minus what you paid, fees included. It is computed when you open the page and is never below zero. A key with fewer than 20 calls in its last 30 days shows “Shows after 20 calls on a key” with its count so far, and a period with no saving says so. How it is computed is in Billing. The info icon on each figure says how it is computed. - Below them: Daily spend by model over the last 30 days (the AI firewall’s charges stacked on top, when there are any), with Open in Usage; the cost breakdown (provider price, Zabio’s service fee, the fee for automatic model choice, the AI firewall’s own line when it charged, and the classifier on days before version 1.2.6; You paid is the same figure as on the Usage page and the bill); Top models, the five that cost the most, each opening Usage filtered on it; Kind of work, by Task (the task type routing classified each
autocall as, shown by its name; calls that named a model are a group of their own), Difficulty or Stakes; and Tokens, input, output, cache reads and cache writes, with the share of cache hits. The task types are listed in the API reference. - At the end, a line with your referral link, while the referral offer is open, which you can hide.
Spend by key and by member are on Usage, Overview.
Usage shows what your calls cost, what Zabio saved and what ran, in your own time zone. It has four tabs, Overview, Logs, Exports and Reports; the first two share one filter bar: Range (Today, Last 7 days, Last 30 days, This month, or a custom range), Project, Key, Provider and Model. The view is in the page’s address, so you can bookmark it or share it with a teammate; the Dashboard’s links to Usage open it with the matching filters. A member limited to projects sees and filters only their projects. A call keeps the project it happened in, even if its key moves to another project later.
Overview opens on four figures for the range: Spend, Saved by routing (computed when you open it, as on the Dashboard), Calls and Cache hits. Then it draws four charts, each with its total for the range above it, hourly for a range of two days or less and daily otherwise:
- Spend: what you were billed. The AI firewall’s charges are a part of their own on top, so the chart’s total is the cost breakdown’s You paid.
- Requests, with how many ended in an error.
- Tokens: prompt and completion, with the share of reasoning.
- Caching: input read from the prompt cache against uncached input, and what caching saved at the providers’ prices.
Spend, Requests and Tokens stack by model or by provider (Stack by). Each model and provider keeps one color in every chart; a chart shows eight series at most, the rest as Other. Point at a bar for each part and the total, or use Show as table. Under the charts, Top keys and Top models list the largest spenders with their share. A key’s spend in Top keys includes its AI firewall charges; Top models counts the calls only. Last, By key and By member show each key’s and each member’s calls, spend and saving for the range.
Logs lists the calls under the same filters, newest first, with metadata only; turn on Errors only to keep the calls that failed, came back empty (the model spent its whole output limit reasoning) or failed their check. Such attempts are marked Empty answer or Failed check, and not billed when Zabio absorbed them. The filter bar narrows the calls by Provider, Model (a call matches when the model you asked for or the model that answered is the one chosen) and Key, and the filters are kept in the page address, so a filtered view can be shared. Each row shows the time, the model you asked for and the model that answered, the name of the key and its project, the task type of an auto call, tokens in and out, the cost, the outcome, the total time, Zabio’s own time, and the time to the first token for streamed calls. Click a call’s time to open it; owners and admins also see its request and response when its key logs bodies. Download CSV exports the calls under the filters. Click Load more for older calls. The old Logs address opens this tab. Each row also carries two thumbs: tell Zabio whether the answer was good or bad, and a bad verdict makes Zabio choose the model again on the next turn of that call’s session (the same verdict the API takes at POST /v1/feedback). A call marked Lost is one the server did not finish recording (it stopped between accepting the call and writing its row); it is never billed.
Exports is coming soon; until then, download your calls as a CSV file from Logs, and send call data to your own tools from Settings, Integrations. Reports holds the monthly workload report of an organization that shares calls: how an independent model judged a sample of the answers, by type of work.
Conversations
Section titled “Conversations”Conversations shows the conversations your code stores through the API (/v1/responses or the conversation parameter): how many, how many entries, the estimated tokens and when the oldest expires. Filter by Key at the top. Only metadata appears here, never the messages. How long they are kept is set in Settings, Data & Privacy, under Stored conversations.
Batches
Section titled “Batches”Batches lists the batches your code sends to POST /v1/batches, newest first, filtered by Status and Created (kept in the page address). Each row shows the status, the endpoint, when it was created and ended, the lines done and failed, the cost and the vendors’ discount (what the batch prices took off the standard prices; it is not the saving). Open a batch for its lines by state and one by one, the cost charged and the vendors’ cost, the saving against your keys’ baselines, Cancel batch while it runs, and, for owners and admins, the output and errors files to download once it has ended. A member limited to projects sees only the batches of their projects’ keys. See Batches.
Playground
Section titled “Playground”The Playground lets you try the API and copy the call into your code.
- If this browser holds your first key (the one on your dashboard), the Playground uses it and says Using your first key; there is nothing to paste. Otherwise paste an API key in the API key field, or choose Use another key. The key stays in your browser and goes only to the API with each message. Use Show to check it and Forget to remove it; signing out removes it too.
- Choose the Mode: Chat completions, or Responses (stored conversation).
- Choose a Model:
auto, a routing tier (auto/cheap,auto/balanced,auto/best), or a model by name. - Optionally add a System prompt, and set Zabio’s options (prompt cache, fallback, max tokens). Options left at their default are left out of the request.
- Type your message and click Send. You see the answer, what Zabio did with it (the model chosen, tokens, cost, what was cached), tips to make the call cheaper, and the call ready to copy.
AI Firewall and Audit Log
Section titled “AI Firewall and Audit Log”AI Firewall checks what reaches your models and where your keys can be used from. Prompt Injection sets the prompt-injection guard for the organization and each key and shows what it found this week; Network Access holds the IP allow and deny lists of the organization, a project and a key; Routing Policies has no policies yet. Owners and admins change them; members read them. See AI Firewall.
Audit Log, owners and admins: who changed what in the organization, and when, grouped by day, with a search, filters for the kind, the person and the dates, rows that open to their details, and a CSV download. See Audit log.
Referrals
Section titled “Referrals”Billing, Credits & Referrals shows your match while you have one (see Credits and promotions), then your referral link and what it has earned. The rules are in Credits and promotions.
- Share your link with Copy, Email, Post on X or Share on LinkedIn.
- Change the name in your link: click New name for a random one, or type your own (3 to 20 characters: a to z, 0 to 9 and hyphens) and click Use this name. Every name you have had keeps working, so links already shared never break.
- Choose where the credit goes if you belong to several organizations, under Credit goes to.
- Add the README badge: copy the snippet at the bottom of the page into your project’s README; it links to your referral link.
Settings
Section titled “Settings”Open Settings for the organization. Your own account’s settings are on My Profile (below). Settings has four tabs:
- General: the organization’s name and default language (see Organizations), what happens when the balance reaches zero, Download organization data (owners and admins; a JSON file with everything Zabio holds about the organization, never the keys themselves) and, for the owner, Delete organization, which explains exactly what goes at once, what goes within 30 days and what stays for accounting law. It cannot be undone.
- Integrations (owners and admins):
- Webhooks: the addresses Zabio sends a signed event to when a batch ends. Add endpoint takes a public
httpsaddress and shows its signing secret once; Rotate secret makes a new one, with the old one still signing for 24 hours; Deliveries lists the newest deliveries with their attempts; Remove stops them. See Webhooks. - Call data export: send a record of each call to your own observability tool over OpenTelemetry. Enter the OTLP traces endpoint and its Headers (their values are stored encrypted and never shown again), switch on Send call records and Save; the section shows the last delivery and why one failed. See Call data export.
- Webhooks: the addresses Zabio sends a signed event to when a batch ends. Add endpoint takes a public
- Data & Privacy: Stored conversations: set the Retention (days), from 1 to 365, and Save.
- Routing Policies: the same tab as in AI Firewall; it has no policies yet.
My Profile
Section titled “My Profile”Open My Profile from the menu under your avatar, at the top right. It holds your own account, the same in every organization you belong to, in five tabs:
- Profile: your name and language, then Save; and the Monthly usage report: on the 2nd of each month, each owner of an organization that made calls gets one email about the month that ended: what routing saved against each key’s baseline model when a saving was measured, its calls, models and what it cost, small charts of the spend by day, the calls by model and
autoagainst named calls, the AI firewall’s tokens checked and what it charged when it ran, which the bill includes, and the trial of every model when there was one. The full cost breakdown stays on the dashboard. It is on for everyone; turn the switch off and you will not get it again. The choice is yours alone; other owners choose for themselves. - Security:
- Change password: enter the current one and a new one (at least 12 characters), then Update password.
- Two-step sign-in: after your password, email link, Google or GitHub, Zabio also asks for a second step: a passkey (your fingerprint, face or screen lock, a password manager or a security key) or a six-digit code from an authenticator app on your phone (Google Authenticator, 1Password, Authy or any app that reads a QR code). You can use either or both. For a passkey, click Add a passkey, enter your current password, give it a name and follow your browser’s prompt. For the app, click Set up an authenticator app, enter your current password, scan the QR code, enter the code the app shows and click Turn on. The first one you add turns two-step on: Zabio then shows ten recovery codes once: save them (Copy or Download), because each one signs you in once if you lose your devices. Turning it on signs out your other sessions. While it is on, creating an API key or a personal token, approving the CLI, connecting an app, moving credit, changing two-step and deleting your account ask for your passkey or a code if you have not used one in the last 10 minutes. A passkey works only on the address you made it on (app.zabio.ai). Add a passkey adds another (up to 10), Rename and Remove change one, Replace authenticator moves the app to a new phone, New recovery codes replaces the whole set, and Turn off removes everything; removing your last passkey when the app is not set up turns two-step off too. Five wrong codes in 15 minutes pause the code step for an hour; a passkey still works then. Lost your devices and your codes? Write to hello@zabio.ai from your account’s address.
- Sessions: every browser where you are signed in. Revoke signs one out; Sign out everywhere signs out all of them.
- Access Tokens: your Personal tokens, for the Zabio CLI: click Create token, choose its scopes (Read, Manage keys, Usage, Billing) and copy it when it appears; it is shown only once and expires after 30 days. When you sign the CLI in from a terminal, it shows a code and an address: open that address (app.zabio.ai/device), enter the code and click Approve.
- Connected Apps: the AI apps you connected to Zabio’s MCP server, with their organization, project, what they may do, daily limit and expiry. Disconnect ends a connection and revokes its key. Disconnected and expired connections are hidden behind Show N disconnected. See Connect an AI app.
- Delete Account: Download my data, a JSON file with everything Zabio holds about you (never the keys themselves), and Delete my account, which explains exactly what goes at once, what goes within 30 days and what stays for accounting law. It cannot be undone.