jev.proField guide · curious → Pro

Open · Last updated

Jev API reading guide

Read their API reference first. This page is a field-guide to how to read it without inventing routes rivals list as if they were TypeSafe’s.

Unofficial reading order — jev.pro is not the API reference and we do not host a forked OpenAPI. Canonical: docs.typesafe.ai/api. We do not sell or issue keys. Replicas are not Jev and not endorsed.

What exists

What to watch

jev-1.13 vs jev-1.13.0; aliases vs pins; Noul vs Vercel boolean; 64k vs door-specific 32k cards.

What not to invent

/v1/batch, webhook products, or extra verbs because a handbook named them.

Read order

API ref for fields → models page for pins/price/limits → jaggedness for what not to ask → SDK only for retries and types. Our /api/* pages are unofficial restatements. If they drift, docs win.

How to walk the official ref without inventing routes

Open docs.typesafe.ai/api and read it as a small surface:

  1. One evaluation POST — POST https://api.typesafe.ai/v1/systemone. If a handbook lists /v1/batch or a webhook product, treat that as the handbook’s invention until TypeSafe documents it.
  2. One models GET — GET /v1/models. Useful as a canary and as a pin check, not as a marketplace catalog of other vendors.
  3. Auth — official SDKs expect TYPESAFE_API_KEY (or the door’s name). Keys come from TypeSafe’s console or a documented marketplace. Never from jev.pro.
  4. Errors — public docs we used include 401, 422, 429, 529. Marketplace extras (402, customer verification) are callouts, not retries of the same body. Official SDKs retry 429/529 only.

Then leave the API ref. Price, context cards, and alias policy live on the models page. What not to ask lives on jaggedness. SDK pages are for types and retries, not for a second set of routes.

Our /api/* pages — including decision endpoint and request schema — are unofficial restatements. If they drift, docs win. The documentation map shows which pillar to open next.

Pins, aliases, and door-shaped traps

Read jev-1.13 vs jev-1.13.0 as different strings until the door’s card says otherwise. Pin jev-1.13.0 if floors exist; jev-latest can move. Some gateways use typesafe/jev-1.13. Do not paste a first-party noul example into a Vercel boolean schema.

Context-length cards also differ by door (64k vs a 32k card is a real class of bug). Believe the door you call for that traffic. Vendor list price $0.042 / M input (output free per models page — vendor claim, confirm) is not in the API ref; do not scrape it from a blog into your client.

When not to use this page’s advice

Do not treat jev.pro as docs. Do not generate an OpenAPI fork “for convenience” and let it rot. Do not assume SemIf/OpenJev speaks the same HTTP — those projects are not Jev and not endorsed. Do not retry 401/422. Schema-safe ≠ factual correctness: a 200 with a Choice is not a true statement about the world.

What this page does not claim

FAQ

SDK or raw HTTP? SDKs retry 429/529. Raw HTTP means you own backoff.

Where is OpenAPI? Follow TypeSafe if they publish one. We do not host a fork.

Is /v1/batch missing from my client? Do not invent it. Queue in your workers; one POST per state unless they document otherwise.

Can I copy a rival handbook’s route list? No. Cover the intent; cite the official ref.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: api decision endpoint, api request schema, documentation map. Canonical: https://docs.typesafe.ai.

Sources