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. Owners and admins can change the organization’s settings; members can use them (see Teams and organizations for what each role can do).

Organizations

An organization holds your balance, keys, members and settings. Its name appears at the top left, next to the Zabio logo.

• Switch organization: open the menu at the top left and pick another organization.
• Create an organization: open the same menu 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, then Organization, then Save.
• Choose what happens when the balance runs out: in Settings, under When the balance reaches zero, pick between continuing on the Free plan (100 requests a day on the free models until the next top-up) and stopping all requests. Your keys and members stay either way.

API keys

Keys are what your code sends with each request. Open API keys in the menu.

Create a key: it asks three things, and every other setting starts at its default.

1. Pick the project at the top of the page first: the key is created in the project you are in, or at the organization’s level under All projects.
2. Click Create key and give it a Name (for example, “production”).
3. 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.
4. 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.
5. 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.

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.

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

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 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.
• Archive a project: click Archive. Its keys keep working; the project just stops appearing in lists. Tick Show archived to see archived projects.

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 on the API keys page if needed.

An organization always keeps at least one owner.

Models

Open Models to choose which models your organization can use, with each model’s price per million tokens, context size and capabilities.

• 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 lines have their own checkboxes at the top.
• Click Save changes to store what you changed.
• The same picker sets the account’s models (Account page), a project’s (Models on Projects) and a key’s (Models on API keys); 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 auto models 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

Open Billing for your balance, payments and everything that moves money. The full rules are in Billing.

• 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.
• Edit billing details (name, address and tax ID printed on receipts): click Edit under Billing details.
• 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.
• See every movement: Activity lists each top-up, charge and adjustment, newest first.

Dashboard

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.

• Credits, Spend and Direct cost (what the same calls would have cost at the vendors’ list prices), then Saved, the difference. Calls made while a key’s baseline was pending count no saving, as each of them showed, so Saved can differ from direct cost minus spend.
• Cache hits, the share of input tokens served from a vendor’s prompt cache, and Cost per 1M tokens, the usual way to compare providers.
• Calls, Latency and stored Conversations.
• Below them: daily spend, a cost breakdown (provider price, Zabio’s service fee, the fee for automatic model choice, and the classifier on days before version 1.2.6), where your tokens went, spend by kind of work (the task type routing classified each auto call as, shown by its name, then the difficulty and the stakes; calls that named a model are a group of their own), and spend by model, key and member. The task types are listed in the API reference.

Usage

Usage shows what your calls cost, what Zabio saved and what ran, in your own time zone. It has two tabs under 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 Explore links 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.

Stats draws five 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.
• Saved: what routing saved against each key’s baseline model. A call that cost more than its baseline shows below zero.
• 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, Saved, 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.

Logs lists the calls under the same filters, newest first, with metadata only; tick Errors only to keep the calls that failed. Each row shows the time, the model you asked for and the model that answered, 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.

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, under Stored conversations.

Playground

The Playground lets you try the API and copy the call into your code.

1. Paste an API key in the API key field. It stays in your browser and goes only to the API with each message. Use Show to check it and Forget to remove it.
2. Choose the Mode: Chat completions, or Responses (stored conversation).
3. Choose a Model: auto, a routing tier (auto/cheap, auto/balanced, auto/best), or a model by name.
4. 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.
5. 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.

Referrals

Referrals shows 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

Open Settings for your own account and the organization.

• Profile: your name and language, then Save.
• Change password: enter the current one and a new one (at least 12 characters), then Update password.
• Sessions: every browser where you are signed in. Revoke signs one out; Sign out everywhere signs out all of them.
• 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. See Connect an AI app.
• 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: open Approve a device in the app, enter the code and click Approve.
• Stored conversations: set the Retention (days), from 1 to 365, and Save.
• Download my data and Download organization data: a JSON file with everything Zabio holds about you or the organization (never the keys themselves).
• Delete organization and Delete my account: each page section explains exactly what goes at once, what goes within 30 days and what stays for accounting law. Both cannot be undone.