Public Versions and Endpoints
| Model ID | Endpoints | Price | Catalog |
|---|---|---|---|
jev-latest
|
/api/v1/typesafe/system_one
|
$0.05 / 1M tokens | Model detail |
Verify
Poll until the task reaches a terminal status
POST /api/v1/typesafe/system_one. Verify the synchronous response matches the endpoint API reference.Configuration
Guide endpoint: /api/v1/typesafe/system_one
export RUNAPI_API_KEY=your_api_key
curl -X POST https://runapi.ai/api/v1/typesafe/system_one \
-H "Authorization: Bearer $RUNAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"state": {
"candidate": "Option A"
},
"model": "jev-latest",
"questions": {
"recommendation": {
"type": "choice",
"instructions": "Choose the matching candidate.",
"criteria": {
"Option A": "The candidate is Option A.",
"Option B": "The candidate is Option B."
}
}
}
}'Get Started in 3 Steps
-
Choose a model ID
Select a public catalog model ID and review its endpoint and current starting price.
-
Configure RunAPI
Set RUNAPI_API_KEY before making the endpoint request.
-
Verify the result
For asynchronous endpoints, poll the same endpoint until the Task reaches a terminal status.
What to Build with OpenClaw + Jev
-
Structured results for your code
Get machine-readable output instead of chat text, so your application can store it, compare it, or act on it directly.
-
Enriching your own data
Run documents, images, or records through the model and keep the results next to the source data for later steps.
-
High-volume processing
Send large batches of inputs with the same RunAPI key and collect the results programmatically.
Why Use Jev Through RunAPI + OpenClaw
-
1 variants, one API key
Use one RunAPI connection to choose among the live model variants without changing your integration.
-
Clear usage pricing
See current catalog pricing before you send a request, with no subscription or minimum spend required.
-
Direct responses
Synchronous calls return the result in the same response, so your agent can use it immediately without task polling.
OpenClaw + Jev Questions
How is Jev different from a chat model?
Chat models generate text for people. Jev returns typed decisions, probabilities, and confidence that software can branch on, sort, and route with.
What can I use Jev for?
Classification, intent routing, scoring, extraction, guardrails, and other software decisions where handwritten rules are too brittle.
What question types does Jev support?
Choice picks one option from a set you define. Score rates the state against an ordered rubric. Noul answers a yes-or-no question with a probability.
What input does Jev accept?
Text only — a string, JSON object, or array. Pre-process images, audio, or video into text before sending them as state.
Which model identifier should I use?
Use jev-latest. RunAPI maps it to the current TypeSafe Jev release.
Which model ID should I use?
Choose a public model ID from the version table. Each ID exposes the endpoints shown for that version.
Does this guide configure a chat model?
No. This Model Line uses the endpoint workflow shown here and is not presented as an agent chat model.