API· Last updated 2026-09-21

Jev API Metadata Fields

The public API reference documents one evaluation route — POST https://api.typesafe.ai/v1/systemone — plus GET /v1/models. This page title is not a separate first-party URL in that reference. Treat the capability as something you implement around the official call.

You may put named fields inside state (ticket id, tenant, locale) so questions can refer to them — those are state, billed as input, and they can distract jev-1.13 if unused. This site does not sell, issue, or proxy TypeSafe keys. Authenticate with a credential you already have from the console or a documented gateway.

Related search language: Jev API metadata fields, TypeSafe Jev, Jev decision model, decision automation.

See also the api hub.

Jev API Metadata Fields: context

Do not assume an official top-level metadata object is ignored-but-echoed unless TypeSafe documents that behavior.

Jev API Metadata Fields: inputs

Prefer storing tenant and experiment ids in your logs keyed by a request id you generate. Send Jev only what the question needs.

Jev API Metadata Fields: decision logic

If a field is not for the model, keep it out of state to save tokens and accuracy.

Jev API Metadata Fields: implementation notes

Confirm new official echo fields on the API page. jev.pro will not invent them.

FAQ

Is this a documented TypeSafe URL?

No. The public reference lists POST /v1/systemone and GET /v1/models. This title is an application pattern around that contract — not a cloned rival endpoint list.

How should I implement it?

Keep one evaluation POST. Put batching, jobs, search, or policy in your code. Do not invent /v1/batch or similar unless TypeSafe documents it.

Does jev.pro issue keys or OpenAPI?

No. Use official SDKs and docs.typesafe.ai. We do not sell credentials.

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/systemone and GET /v1/models unless 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.

Primary documentation: https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.