Jev API metadata fields
You may put named fields inside state (ticket id, tenant, locale) so questions can refer to them. Those fields are state, billed as input, and they can distract jev-1.13 if unused. There is no documented sibling metadata object that is free.
This page is for builders who searched an extra “endpoint” name while wiring Jev / System One. 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
- Include identifiers the question needs.
- Keep transport ids (OTel) in your logs, not necessarily in state.
- Filter unused keys.
- Do not send raw auth tokens as “metadata.”
Map onto the official POST
State: string, object, or array of text. Point instructions at backtick paths such as `ticket.id`. Question ids are not sent to the model and are not a hidden metadata channel. There is no documented unbilled meta bag and no x-typesafe-meta billing bypass.
Vendor-claimed list price meters input tokens ($0.042 / million; output free). Vendor-claimed context: 64k for state + all questions; 32k for state + the longest question. Duplicating the whole CRM record “for context” burns both. Pin jev-1.13.0 when unused fields already change your floors; aliases currently resolve there — confirm.
Questions see state and instructions, not HTTP headers. Tenant isolation is your IAM. Documented errors: 401, 422, 429, 529. Official SDKs retry 429/529. Schema-safe inclusion of a locale field does not make the model fluent in that locale — English is primary.
When not to put it in state
Trace ids, retry counters, and webhook signatures belong in your logs or verify step. Signing secrets must never enter state. If a field cannot change the answer to an atomic question, leave it out.
Pitfalls
- Duplicating the whole CRM record “for context.”
- Inventing
x-typesafe-metaas a billing bypass. - Putting OTel spans in state and wondering why Noul drifted.
- Assuming headers are visible to Choice/Score/Noul.
See also
- API hub — required body fields
- State — what the model evaluates
- Trace identifiers — ids that stay in logs
- Request format —
model,state,questions
FAQ
Is this a documented TypeSafe URL?
No.
Can questions see headers?
They see state and instructions.
Tenant isolation?
Your IAM — permissions.
Are unused keys free?
No. They meter as input (vendor claim) and can distract jev-1.13.
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.