Tokenly
Enterprise
Procurement asks questions a demo cannot answer: who trained the model, who serves it, what it costs per unit and when the record was last checked. The catalogue is built to answer them.
Where it helps
Vendor and model review
Developer and serving provider are separate fields, with a source link and verification date on every record.
Budget planning
Input, output and cache prices appear with unit and currency, so a cost model can be rebuilt from the page.
Data handling questions
Limitations and availability state what is known. What is not confirmed is marked, not guessed.
Available versus planned
Available
- Public catalogue with stable model pages
- Search, filters and price-position sorting
- Trilingual records (English, Traditional and Simplified Chinese)
- Enquiry channel for procurement questions
Planned
- Single contract covering multiple providers
- Per-key model allowlists and budgets
- Usage, billing and audit history
- SSO and team management
Talk to us about a pilot
Tell us which models and volumes you are considering and we will reply with what is actually available today, and what would need Phase 2.