TypeSafe

Fronts TypeSafe’s Jev model, which answers typed questions about state you supply instead of generating prose. You send a state and a map of questions; you get back one answer per question, each carrying a probability distribution and — for two of the three types — a confidence. One route is mounted:

POST /typesafe/v1/systemone   → https://api.typesafe.ai/v1/systemone

That single endpoint is TypeSafe’s whole billable surface, so it is mounted as a fixed literal route. Every other /typesafe/* path, and any method other than POST, draws the gateway’s own 404 without reaching the upstream.

Credential handling

TypeSafe reads its key from Authorization: Bearer — the same header that carries your gateway token — so the gateway replaces that header with its own TypeSafe key. Your gateway token stops at the gateway and never travels upstream. There is no query-parameter form of the key, so nothing is stripped from the query string.

The request

Three fields, all required:

The body is forwarded as you sent it. TypeSafe rejects any top-level field it does not recognize with its own 400, so the gateway adds no second policy of its own.

Question types

Every question carries a type and instructions; each type adds its own criteria.

{
  "type": "noul",
  "instructions": "Does this convey urgency?",
  "criteria": { "true": "Explicitly time-sensitive", "false": "No urgency expressed" }
}

{ "type": "noul", "noul": 0.95 }

Asking several questions at once

The state is read once no matter how many questions ride along, and every question is evaluated against it independently. Since you are billed on input tokens, a long state split across separate calls is paid for on every one of them — batching is the single biggest cost lever on this route, and it is also faster.

curl -X POST "$GATEWAY/typesafe/v1/systemone" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "Help! My payouts have been failing for 3 days.",
    "model": "jev-latest",
    "questions": {
      "is_urgent": { "type": "noul", "instructions": "Does this convey urgency?" },
      "department": {
        "type": "choice",
        "instructions": "Which team should handle this?",
        "criteria": { "billing": "Payments, invoicing, refunds", "technical": "Bugs, outages, integrations" }
      }
    }
  }'

TypeSafe’s answer comes back exactly as it arrived — status, headers, and body bytes:

{
  "model": "jev-1.13.0",
  "answers": {
    "is_urgent": { "type": "noul", "noul": 0.95 },
    "department": {
      "type": "choice",
      "choice": "billing",
      "probabilities": { "billing": 0.86, "technical": 0.14 },
      "confidence": 0.73
    }
  },
  "usage": { "input_tokens": 343, "output_tokens": 50 }
}

Models

The response always names the concrete version that answered, so sending jev-latest comes back as "model": "jev-1.13.0". An alias can move to a new model without notice, which is why pinning is worth it once your thresholds matter.

Limits

• 64,000 tokens per request for the state plus all questions combined, and 32,000 for the state plus the single longest question.
• Text only. A string, a JSON object, or an array of text values — no image, audio, or video input. Convert those to text or structured fields first.
• TypeSafe applies its own per-account rate limits and answers 429 when you exceed them; it publishes these as subject to change.

Billing

Billed on input tokens only — output tokens are free — at $0.042 per million input tokens, TypeSafe’s own published rate with no per-request markup. Every response reports what it consumed in usage.input_tokens, and that is what the charge is settled from. A typical single-question call runs a few hundred input tokens.

Because output is free and the state is read once, the cost of a call is essentially the size of your state plus your questions — which is why packing many questions into one request is so much cheaper than one call each.

Errors

Upstream statuses pass through untouched:

A 401 means the gateway’s own credential is the problem, not yours — your gateway token is checked before the upstream call and answers 401 separately if it is missing or revoked.

Field-level request and response detail lives in TypeSafe’s API reference; the gateway changes neither.