The same work, three times
Each new model means an account, a connection, a test, and a launch. Three vendors is three projects.
Model API tokens
One account, one interface, one bill. Pay for use. Stop when you want. See every call.
Thestallisrarelythemodelitself
No single cost
Price is per token, and usage is scattered. Finance cannot close the month from one sheet.
One line, one outage
When the only route wobbles, the product wobbles with it. Most teams never build a spare.
Settlement friction
Cross-border payment and mixed currencies get louder as the product gets faster.
Connect once. Use many models. Read the whole account.
Whatyouget
A familiar call
The call stays close to the common API shape. Switching models is configuration. The protocol and SDK list will ship with the docs.
Several models
Compare quality and cost on one account. The vendor list is published before launch, not invented here.
Keys and limits
Child keys with a cap, an expiry, and a model range. Isolate a project. Revoke a key when the work ends.
Cost
Usage by day, project, key, and model. Set a budget and an alert.
A second route
If the main route fails, traffic can move. We will not quote an uptime percentage until it is measured.
Audit
Company verification, key levels, retained logs, and an export for your own review.
Fourmoves,thenthemodelisinyoursystem
Register
Send the company or personal details and complete verification.
The flow is online, and you can see the status.
Usually the same day
Create a key
Issue an API key and set a credit limit.
Key and permission controls in the console.
A few minutes
Call it
Replace the address and the key, then send a request.
Docs, samples, and error codes.
Depends on your system
Watch it
Move real traffic. Set the budget and the alert.
Usage, alerts, and a support channel.
Ongoing
Payforwhatran
- Billed on tokens used. Prices differ by model.
- Prepay credit if you want. A low balance sends an alert.
- Larger volume can move to a stepped price.
- Export the detail and the monthly bill for your own books.
Amoveisusuallytwoedits
Before
The vendor address, plus the vendor key.
After
The Voiceup address, plus the Voiceup key.
Other parameters stay. This is a sketch. The docs are the source.
Questions
Which languages?
The SDK list is not published yet. Teams that already call a common API usually change the address and the key.
Can one account serve many projects?
Yes. Child keys carry their own credit, so projects stay separate and costs can be split.
What if credit runs out?
You get a warning before the line. Calls pause at zero and resume after a top-up. The terms have the exact rule.
Can we stop?
Yes. There is no minimum spend. Stop topping up.
Monthly invoicing?
Terms and the billing cycle are not published yet. Company accounts confirm them with us.