Security
How we protect your key and your money
These are the controls actually in place, described plainly. If a claim isn’t on this page, we aren’t making it.
Keys
- Closed by default. Every model call needs a valid key. Only health checks answer without one.
- Fingerprints, not secrets. We store a SHA-256 hash of your key, never the key itself. The readable key exists exactly once, when it’s issued to you.
- One answer for bad keys. Unknown, revoked and malformed keys all get the same
401, so nobody can probe which keys used to be valid. - Rotate or revoke at any time. Rotation is atomic: the old key stops working the moment the new one is issued. See the auth docs.
- If a key touches a log, a screenshot or a repo, treat it as burned and rotate it. Keys never travel in URLs, and we never write key values to our logs.
Spending
- Prepaid only. Calls draw down credit you’ve already bought. There’s no invoice and no surprise bill.
- Fail closed. If your balance can’t cover a request, it’s refused with a
402before the model is called. Requests for new API keys (no card needed to create one) are rate-limited per day and get a429past the limit. - Billed at the provider’s reported cost. Each request is charged what the upstream provider reports for it, with zero markup.
Payments
- Card data never touches us. Checkout runs on Stripe’s hosted page, and we never see, receive or store card numbers.
- Signed confirmations only. Credit is added only when Stripe sends a correctly signed payment notice, and each payment is credited once, even if the notice is repeated.
What we don’t claim
TokenCenter currently holds no SOC 2, ISO 27001 or similar certification, has had no third-party penetration test, and runs no paid bug-bounty program. This page will say so when that changes.
Report a vulnerability
If you’ve found something that puts keys, accounts or payments at risk, please tell us before anyone else:
- Contact us through SolaroLabs.com with “TokenCenter security” in the subject.
- Describe what you found, which page or endpoint is affected and, if you can, how to reproduce it.
- Test only against your own key and account, and give us reasonable time to fix the issue before disclosing it.