Sub2API TypeSafe Gateway
An API gateway forwards native Jev System One requests with account isolation, usage billing and bounded account failover.
Added to Jevfast
How it uses Jev
Sub2API exposes TypeSafe System One through POST /v1/systemone for TypeSafe API-key accounts. The README shows a state string and a Noul safety question; Sub2API retains the native System One request and successful response structure.
What Jev decides
Safety check (illustrative request shape)Example answers · not a recorded Jev response · Source ↗
Question 1 · safety
YOUR APP
INSTRUCTION
Evaluate whether the text is unsafe.
STATE
A text value to evaluate, supplied as the System One state; one question named safety asks whether the text is unsafe.
JEV · NOUL
YesNo
App workflow
- Configure a TypeSafe account
Add a TypeSafe API-key account and configure its upstream; the public endpoint is /v1/systemone.
- Submit native System One request
A client sends model jev-latest, state, and typed questions to the endpoint with a Sub2API bearer key.
- Forward the result
Sub2API preserves the native JSON structure in successful responses and applies existing gateway account error and failover policy.
Why it is interesting
It routes a typed Jev protocol through an API gateway with account authentication and the gateway’s existing billing, error handling, and account failover behavior.