Jev API bulk imports
Bulk import means you hydrate one state per row from a file and call the official evaluation endpoint. There is no documented CSV ingest on api.typesafe.ai.
This page is for builders who searched an extra “endpoint” name. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell or issue keys. Confirm first-party routes on docs.typesafe.ai/api.
The public API reference documents one evaluation route — POST https://api.typesafe.ai/v1/systemone — plus GET /v1/models. This title is not a separate first-party URL in that reference. Treat the capability as something you implement around the official call.
Steps
- Freeze a
questionsmap and pinjev-1.13.0(or the current versioned id). - Map each row → filtered text/object state.
- POST one evaluation per row (or pack many questions about that one row).
- Checkpoint the cursor. A 422 on one row must not abort the file.
- Honor 429/529 backoff — vendor defaults 1,200 RPM / 250k tok/s can change.
Request / response shape
Each official request still has one state. Reuse the same questions object. Persist response.model and usage per row.
Pitfalls
- Inventing
/v1/imports. - Sending the entire CSV as one state (distractors + token bill).
- Mixing
jev-latestmid-file.
See also
FAQ
Can I attach a multipart file?
Not in the public System One contract we read. JSON body only.
Batch vs bulk?
Batch often means many questions / one state. Bulk means many states. Both are your workers.
Does jev.pro host an importer?
No.
What this page does not claim
- Official TypeSafe status, logos, or support.
- That jev.pro sells, issues, or proxies API keys.
- Extra first-party HTTP routes beyond
POST /v1/systemoneandGET /v1/modelsunless the API reference lists them. - Invented latency SLOs, search volume, or unofficial prices. List price and rate limits are vendor claims — confirm on models.
- That a schema-constrained answer is automatically factually correct.
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.