Terms of service

The terms of service in short

The sections below are the terms themselves; this list only points to them, so if the two ever read differently, the section wins.

• This site is independent. It is not TypeSafe AI and is not endorsed by it, and where it disagrees with the official documentation, the documentation is correct.
• Every account gets 5 credits a month with no card. Credit packs are one-time payments with no renewal, taken through a merchant of record, Waffo or Creem.
• Packs are final sale. A duplicate charge, or credits that never arrived, is always put right, and a refund right given by the law where you live still applies.
• There is no uptime promise and the API can be withdrawn; each ruleset publishes the official call it makes, so you can leave without rewriting anything.
• Do not send other people's personal data through the API. Keys that are plainly being abused can be revoked.
• The measurements can be quoted freely, nothing here is advice, and all of it is provided as-is.

The API and its monthly allowance

Anyone can get a key. It is 5 credits a month, free, with no card and no waitlist. In exchange, the honest terms are:

• No uptime promise, at all. This runs on one site's budget, on top of an early-access model that can change or go away without telling us. Do not put it on a path where an outage costs you something.
• It can be withdrawn. If the upstream key stops working or the bill stops making sense, the endpoint goes away. Every ruleset publishes the exact official API call it makes at GET /api/v1/rulesets/<id>, specifically so that you can leave without rewriting anything.
• Do not send other people's personal data through it. Your text is forwarded to TypeSafe. That is a decision you can make about your own data and not about somebody else's.
• Keys can be revoked if one is obviously being abused — scraping the quota with throwaway addresses, or running something the free tier was plainly not meant to carry. There is no appeals process, because there is no process at all.

Refunds

Starting with an account costs nothing. No card is taken to get an API key, and the 5 credits a month cost nothing in the ordinary sense of the word — they do not turn into a bill and no payment method is stored to run them.

Beyond that there are credit packs, and they are the only thing sold here. One payment, no subscription, no renewal date: see Plans for the current packs and prices. Payments go through a merchant of record, Waffo or Creem, which is then the seller and the name on your statement. Some earlier packs were paid through Stripe, where the seller was the business that runs this site. The checkout page shows which before you enter anything, and card details never reach this site. Both are named because routing is ours and can move, so naming only one would be wrong for some buyers the moment it did.

Credit packs are final sale. Purchased credits are not refunded, used or unused, and that includes a pack bought by mistake or for a different service. The 5 monthly credits exist so the API can be tried before anything is bought, and every page of this site says it is independent of TypeSafe: a key from here does not work on TypeSafe's API.

Two things are always put right: a duplicate charge for one order, and a payment whose credits never arrived. Write to the address in Contact and the credits are added or the duplicate refunded. Failed requests are never charged — the cost is settled from the token count in a successful response, so there is nothing to bill when there is no response. Where the law where you live gives you a right to a refund, that right applies regardless of this section.

What you are buying is this endpoint, its rulesets and its quota — not Jev itself. TypeSafe bills separately if you hold your own key, and refunds there are between you and them under their customer agreement. OpenRouter likewise, if you route through the gateway yourself. A charge from either of those is not one of ours.

Contact

Questions about these terms of service, corrections, takedowns, billing problems and complaints all go to the same place: support@jev-agent.com. It is one person, so expect a human reply rather than a fast one.

The measurements

Every benchmark figure on this site may be quoted, reproduced and argued with, freely, including commercially. Attribution to jev-agent.com is appreciated and not required. The code behind the numbers is MIT-licensed at jev-measured, and the code samples on the site are free to copy without attribution.

What they are not is a guarantee. They were measured on particular days from a particular machine against a model that is still in early access, and at least three published conclusions here have already been corrected after re-measurement — those corrections are left visible on the benchmarks page rather than edited away, and every correction is listed with its date on the sources page. Re-run them yourself before betting anything on them. That is what the repository is for.

Nothing here is advice

Technical, legal, financial or otherwise. It is one developer's notes on an API, published because the notes were useful. Decisions about your own architecture, your own vendors and your own compliance obligations are yours.

Liability

The site and the API are provided as-is, with no warranty of any kind. To the extent the law allows it, nothing here comes with liability for what happens if you rely on it. Given that the content is one person's notes and the API sits on an early-access model, this is less a disclaimer than a description.

Changes to these terms of service, and how to complain

These terms of service can change; the date below is when they were last reviewed and material changes get a line in the commit history rather than a silent edit. If something here is wrong, unfair, or describes the site inaccurately, email support@jev-agent.com. That is also the route for a takedown, a correction or a billing problem, and the fastest one.

Last reviewed 2026-10-03.