Credits and billing

Unyo runs on credits — no seats, no per-message tolls. Your balance is the one number to watch.

You start with 2 500 free credits when you sign up. No card. That's around 16 generated images, or dozens of conversations with an agent, to find out whether the team is any good before you pay anyone anything.

What actually costs credits

The design rule is simple: you pay when something is generated, or when something leaves the building. You don't pay to read your own data — with one named exception: calendar tools are priced per call, reads included.

Of the 105 priced agent tools, 73 cost zero credits — and they write no billing record at all, because there's nothing to record.

Free, always:

• Reading your inbox, opening a thread, searching your mail
• Every Neural Core tool — remembering, searching, updating, exporting your business memory. All 23 of them.
• Drafting an email, drafting a social post, writing a document draft, planning a run
• Social analytics — top posts, posting insights, connected accounts
• Listing your Slack channels and your Drive files
• Every draft card and preview the agents put in front of you
• Reading your website's code, restarting its preview, and taking a published site offline

Paid, because something real happens:

On top of a tool's price, each agent run carries the real cost of the model that did the thinking. That's the part that isn't a fixed grid — see below.

How a chat turn is priced

There is no "one credit per message" charge in Unyo. We deleted it.

Instead, every turn an agent takes is metered against a real per-model price sheet — how many tokens went in, how many came out, how many were served from cache — and converted at the end of the run:

Two consequences worth knowing:

• Cache discounts reach you, not us. When the model serves part of the prompt from its cache, that portion is billed at the cached rate on the price sheet — and that lower number flows straight into your debit. On a cache-heavy turn it's a meaningful saving on the same conversation.
• Retries are free. If a tool hits a transient error and the agent retries it, the retry happens inside the same reservation. One intent, one charge.

Failures are refunded — automatically

Every paid action is a reserve → commit-on-success / refund-on-error cycle. All 32 paid tools are marked refundable on error.

• A publish that the platform rejects → refunded.
• An image generation that fails → refunded.
• A run that crashes halfway → the whole model reservation comes back.

And for the case where the machinery itself dies mid-run: an hourly janitor sweeps the run's model reservation if it's still held after 6 hours and refunds it. A run finishes in minutes, so anything still sitting there after six hours is by definition stranded, and it gets given back without you asking.

Seeing where your credits went

Open Settings → Credits.

1. At the top: N credits available, with a bar that fills up as you spend.
2. Credit activity — a day-by-day heatmap of the last 26 weeks. Hover any square for the exact credit count for that day, in your own timezone.
3. Four numbers underneath: used today, used this month, remaining this month, and bonus credits.
4. On a paid plan, a live countdown to your next reset — days, then hours, then minutes as it gets close.
5. Get more credits opens the top-up options.

The heatmap is built from the real committed ledger — the same rows the server charged you against. It counts model usage and tool calls only; credits you were given (a plan reset, a top-up) are grants, not usage, and are excluded.

Balance, resets and top-ups

Your spendable balance is your monthly credits + your bonus credits, and it's always the server's number, not the browser's — the app can't top itself up.

• Bonus credits (top-ups) never expire, and they're spent first, before your monthly allocation. There's no toggle to remember.
• Monthly credits don't roll over. On a paid plan, your allocation is set back to your plan's full amount each month. Anything unspent from last month is gone; your bonus credits are untouched.
• The free plan never resets. The 2 500 credits are a one-time signup grant. When they're spent, you choose a plan or a top-up.
• Credits do not reset daily. There is no daily limit in Unyo. If you ever see wording suggesting otherwise, it's stale — the daily model was retired.

Plans and top-up packs, with prices and credit amounts, are on Plans and top-ups.

Running out

When your balance hits zero, Unyo tells you plainly instead of failing silently: a full-screen message saying you're out of credits, with the plans and top-ups right there.

• It never appears on the public site, the sign-in pages, or a shared file link.
• Checkout opens in a new tab. When you come back, press I've paid — refresh.
• You usually don't need to: the moment your payment lands, the block clears itself. No reload, no logout, no support ticket.

If you cancel a subscription, you keep your remaining balance and all your bonus credits, and you can keep spending them until they run out.

Tips for spending less

• Ask before you generate. Drafting is free; the image is what costs. Get the caption right first, then ask for the picture.
• Let agents read freely. Inbox triage, Neural Core searches and social analytics are all zero — there's no reason to ration them.
• Keep one conversation going rather than starting a new one for every question. A continuing conversation reuses the cached prompt prefix, and that discount lands on your bill.
• Edit before you republish. A website edit is 15 credits; republishing it live is 25. Batch your changes into one edit, then republish once.
• Top up on the bigger pack if you top up at all — the larger packs are a better rate per credit, and the credits never expire.

FAQ

Troubleshooting

"My balance looks wrong after paying." Press I've paid — refresh. Credits usually arrive within a few seconds of payment and the block clears on its own; if it doesn't, refresh once more. Payments are processed idempotently, so a retried payment notification can never credit you twice — or charge you twice.

"An action was refused for insufficient credits but I have some left." Some actions reserve credits up front and refuse rather than half-complete. Top up, or check Settings → Credits for your real balance — the server's number is authoritative, and the browser can be a few seconds behind.

"I was charged and nothing happened." Check the day's square in the Credit activity heatmap. If a paid action genuinely failed, the refund is automatic — immediately in almost every case, and at worst on the next hourly sweep.