Every model is another integration
New auth, new error formats, new invoices. Your roadmap stalls while engineers babysit plumbing.
For SaaS teams
Smart compose, summaries, search answers, onboarding copilots. Add them to your product behind one endpoint, with per-call pricing you can map straight onto your own plans.
from API key to first feature call
price per call, visible before you ship
swap models without a redeploy
The problem
New auth, new error formats, new invoices. Your roadmap stalls while engineers babysit plumbing.
Product wants to price the AI tier. Finance wants a unit cost. Nobody can say what a summary actually costs.
When the single model behind your feature has a bad hour, your customers see it first.
Capabilities
Summaries, drafts, classification and code help all go through the same authenticated POST, so new features reuse what you already built.
Every response carries token counts and price, so you can attribute cost to a tenant, a feature or a plan.
The model catalog shows per-token pricing for each model, so product and finance can agree on a feature before it ships.
If one model is busy, the request moves to another that can serve it. Your feature stays responsive.
Popular prompts repeated inside the cache window come back fast and cost nothing.
Create separate keys for staging and production and revoke one without touching the others.
Use cases
Turn long threads, tickets or documents into a crisp recap right where your users work.
Draft emails, notes and replies inside your product in the user's own context.
Pair your search results with a short generated answer that cites what you found.
Answer setup questions in-product so new accounts reach value faster.
How it works
Try prompts against catalog models and see tokens, latency and price per run.
Call POST /api/ainf/inference from your backend with a bearer key. Existing chat-style clients adapt with a base URL change and a small body mapping.
Track daily and month-to-date usage in the console as the feature rolls out.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'Every response includes tokens and price, and your keys are tracked per request, so you have the data to build usage-based pricing on your side.
Usually not. Point it at our base URL, send your key as a bearer token and put your text in the prompt field.
Create a key per environment, and tag each response's price and tokens in your own logs so staging and production spend stay separate.
Metered per token at the price shown for each model. Usage beyond the free monthly allowance is invoiced every 30 days and paid online.
Prototype today on the free allowance, then ship with pricing you can explain.