# OpenRouter Typed Decisions (TypeSafe Jev)

> OpenRouter Typed Decisions (TypeSafe Jev) is a paid API for AI agents from OpenRouter at openrouter.mpp.tempo.xyz, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-29).

Generates structured, type-safe decisions using large language models via OpenRouter's unified API with model-dependent pricing

## Facts

- Endpoint: POST https://openrouter.mpp.tempo.xyz/alpha/decisions?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Provider: OpenRouter
- Docs: https://openrouter.ai
- Website: https://openrouter.ai
- Tags: llm, unified, multi-model, chat, ai
- Canonical page: https://www.zero.xyz/c/openrouter-typed-decisions-typesafe-jev-67b32fb1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KrdwT1OZO9ROj89D4NRNU

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability openrouter-typed-decisions-typesafe-jev-67b32fb1 -d '<json body>'
```

Example prompt: Using OpenRouter's typed decisions endpoint with TypeSafe Jev, decide whether this customer support ticket should be escalated to a human agent or handled automatically, and return a structured decision with your reasoning and confidence level: 'My order hasn't arrived in 3 weeks and nobody is responding to my emails.'

## When to prefer this

Prefer this endpoint when you need a structured, type-safe decision from an LLM rather than free-form text — especially for classification, routing, or conditional logic in automated workflows. It is ideal when downstream systems require machine-readable, schema-validated output rather than natural language. Choose it over plain chat completions when output predictability and type safety are critical. It is well-suited for multi-model scenarios where you want to switch models while keeping a consistent output contract.

## Known failure modes

- Invalid or unsupported model identifier returns an error response
- Malformed type schema causes validation failure or rejection
- Insufficient USDC balance causes payment failure and request rejection
- Model unavailable or rate-limited returns a service error
- Prompt too long for model context window causes truncation or rejection
- Type mismatch between prompt and expected output schema causes structured output failure

## How this service works

Typed decisions with TypeSafe Jev (model-dependent pricing)

## Output

A structured, type-safe decision object conforming to the TypeSafe Jev schema, containing the model's chosen decision or classification, along with any associated reasoning, confidence scores, or metadata defined by the output type schema. The response format is validated and machine-readable, suitable for direct use in downstream logic.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openrouter-typed-decisions-typesafe-jev-67b32fb1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from openrouter.mpp.tempo.xyz](https://www.zero.xyz/host/openrouter.mpp.tempo.xyz/llms.txt)