Tokenokio for government
AI token spend, accounted for — without sending a single prompt off-site
Public sector teams are being asked what AI actually costs, by programme, before the next budget cycle — and most can only produce a vendor invoice. Tokenokio turns usage into an auditable record without introducing a new data processor: nothing is uploaded, so the assessment surface stays close to zero.
What this fixes
- No line of sight on what AI costs per programme or team
- Usage is attributed by project, team and machine, priced at published provider rates, and exported as a showback CSV or GL journal your finance team can post.
- A new cloud tool means a new data-protection assessment
- There is no data to assess. Scans parse in the browser and stay on the device; no prompts, outputs or keys ever reach us, so there is no processor holding your content.
- Shadow AI usage nobody can quantify
- Local scans read the usage history that assistants and coding agents already write to disk, so unofficial usage shows up in the same ledger as sanctioned spend.
- Runaway automated agents burning budget overnight
- Agent Guardian baselines your normal burn rate and can stop a process before a loop compounds — the failure mode behind widely reported overnight blowouts.
- Evidence needed for procurement and audit
- Every figure is labelled provider-reported or estimated at list price, with the method shown. Nothing is a black box, and the full history exports.
Before you ask procurement
No data egress
Usage data is parsed in your browser and stored on your device. We never receive your prompts, outputs, API keys or payment details, and there is no user database to breach. Independent certifications (SOC 2 Type II, ISO/IEC 27001) are on the roadmap and not yet held; what exists today is an adversarial security review with findings remediated and security behaviour enforced by automated tests on every change.
No vendor lock-in
Tokenokio runs on the AI accounts and keys you already hold. We never resell tokens, hold credits, or take custody of your payments, so there is no new financial relationship in the supply chain.
Transparent method
Costs are token counts priced at published provider rates, or the provider's own reported figures where an admin key is connected. Each row says which, so an auditor can trace any number.
Questions we get asked
Does our data leave the agency network?
No. Scans run in the browser and results are stored in that browser's local storage on the officer's own device. Prompts, outputs and files are never transmitted to Tokenokio, and we hold no copy of your usage.
Do you hold SOC 2 or ISO 27001 certification?
Not yet — both are on the roadmap and we will not claim them before they are issued. What exists today is a local-first architecture that minimises what could be exposed, an adversarial security review with findings remediated and re-verified, and automated security tests that run on every change. We will share the review summary and our responsible-disclosure policy on request.
Can it cover usage across several machines and teams?
Yes. Each machine scans locally and exports a file; merged together they form one ledger with per-machine and per-project attribution. Where you connect a provider admin key, that account's usage is covered centrally across every device.
How does it reduce spend rather than just report it?
It classifies each task and routes it to the cheapest model that clears a quality bar for that work, escalating to a stronger model if an answer comes back weak. Heavy work can run on subscriptions you already pay for at no extra marginal cost.
See your own numbers in 60 seconds — nothing uploaded, no account required.