Endpoint
Send a JSON POST request to https://jev-typesafe.pro/v1/decide. Authentication uses your account API key as a Bearer token.
curl https://jev-typesafe.pro/v1/decide \
-H "Authorization: Bearer jv_live_your_key" \
-H "Content-Type: application/json" \
-d '{"model":"jev-latest","state":"Customer asks for a refund","questions":{"route":{"type":"choice","instructions":"Which team should handle this?","criteria":{"billing":"Payments and refunds","technical":"Bugs and outages"}}}}'Question types
Choice
Provide finite option keys with clear descriptions. Handle uncertain outcomes with application-specific thresholds and a fallback.
Score
Define an ordered rubric and validate boundary examples against your expected labels.
Noul
Phrase a yes/no statement precisely. Verify the exact response field and meaning against current official documentation.
Credits and errors
Each accepted request reserves one credit. The credit is restored if the upstream request fails or returns a server error. Invalid API keys receive HTTP 401; insufficient balance receives HTTP 402.
Security
- Keep API keys on a trusted server. Never embed them in browser JavaScript.
- Keys are shown only once and stored as hashes. Revoke a key immediately if it is exposed.
- Send only the state needed for the decision and avoid unnecessary personal data.
- Confirm the exact request and response schema in the official API documentation before production use.