Pay per API call. No signup, no contract, no minimum.

Every AI or identity API in this market starts the same way: a contact form, a sales call, a contract, a minimum commitment. You find out the price after someone has qualified you as a lead.

We do it the other way round. The price is on the page, and you can call the API before you tell us who you are.

There is no account

GlianaAI has no signup. Authentication is payment: the API answers with HTTP 402 Payment Required, your client pays, and the call goes through. That is the whole gate.

Two ways to settle:

• Per call from your own wallet — stablecoin, on the rail you already use. Nothing is held by us.
• Prepaid balance — top up, spend down, see what is left. Useful if you want one bill instead of one settlement per request.

Either way, we never hold your funds and there is nothing to cancel.

Why this suits automated work

If the thing calling the API is a program rather than a person, "sign up and wait for approval" is a wall. A payment handshake is not — a client can discover the price, pay it, and continue without a human in the loop.

That is also why our catalog, prices and schemas are published as live endpoints rather than a PDF: whatever is calling can read them at runtime.

What it costs

Prices are per call and listed publicly. Nothing is metered per seat, per month, or per environment. A quiet month costs nothing, because there is no subscription underneath.

Safety rails, on by default

An API key you paste into a script is a credential that can be leaked. So every key carries a daily spend cap by default, adjustable in the dashboard. A key that escapes costs you a bounded amount rather than the balance.

And you are only charged for work that completed. A failed call is refunded.

Try it before deciding anything

That is the actual pitch. No form, no call, no procurement cycle — read the price, run one request, decide afterwards.