No free-form text generation. API examples still report nonzero usage.output_tokens for structured answers; free output does not mean an empty response.
Parameters
Not collected
No reviewed native model contract for this field. Unknown is not unsupported.
Release date
Not collected
No reviewed native model contract for this field. Unknown is not unsupported.
Knowledge cutoff
Not collected
No reviewed native model contract for this field. Unknown is not unsupported.
Tool calling
Not collected
No reviewed native model contract for this field. Unknown is not unsupported.
Bearer API key at POST https://api.typesafe.ai/v1/systemone. Organization rate limits apply.
Regions
No model-specific processing-region contract verified in the reviewed sources.
INPUT / 1M TOKENS$0.042
OUTPUT / 1M TOKENS$0.00
Per billed input token; output is free. The same rate applies with optional long context. Enter billed input for one question, including its state, instructions and criteria. Context validation and multi-question usage accounting are separate from this estimate. Cached input price: not collected.
The MCA excludes customer data from weight-training datasets without prior consent, but permits perpetual use for telemetry, fraud/abuse monitoring and legal compliance. Enterprise zero data retention is separately offered by contact; it is not the default. No universal request-retention period or region is verified. Separate agreements can govern customer access.
Moving alias; resolution recorded on the review date. Log the response model field to identify the serving version.
Access
Bearer API key at POST https://api.typesafe.ai/v1/systemone. Organization rate limits apply.
Regions
No model-specific processing-region contract verified in the reviewed sources.
INPUT / 1M TOKENS$0.042
OUTPUT / 1M TOKENS$0.00
Per billed input token; output is free. The same rate applies with optional long context. Enter billed input for one question, including its state, instructions and criteria. Context validation and multi-question usage accounting are separate from this estimate. Cached input price: not collected.
The MCA excludes customer data from weight-training datasets without prior consent, but permits perpetual use for telemetry, fraud/abuse monitoring and legal compliance. Enterprise zero data retention is separately offered by contact; it is not the default. No universal request-retention period or region is verified. Separate agreements can govern customer access.
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
TypeSafe API
jev-1.13.0
Not verified
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
How it works
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Minimum reusable input
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Lifetime & refresh
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
How to enable it
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Usage fields
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Billing rules
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Limits & data boundaries
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 16 Oct 2026
TypeSafe API
jev-latest
Not verified
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
How it works
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Minimum reusable input
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Lifetime & refresh
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
How to enable it
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Usage fields
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Billing rules
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
Limits & data boundaries
Not collected
No native inference-cache specification established. Shared request state, parallel questions and data retention are not prompt caching.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 16 Oct 2026
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
Provider-developed System One model served through a restricted commercial API. Current model docs describe shared trained weights, with no public checkpoint distribution in the reviewed sources; the MCA reserves the service technology.
