jkudish's Jev Agent Tools

A multi-provider Jev transport/provider layer with fail-closed validation, used by jkudish/jev-browser and jkudish/jev-mcp. One ask() call picks a carrier from the environment, sends your typed questions, validates the answers, and returns the answer plus usage and the effective model — or a typed rejection.

Auto-selection tries TypeSafe (TYPESAFE_API_KEY), OpenRouter (OPENROUTER_API_KEY), Cloudflare (JEV_CLOUDFLARE_API_TOKEN preferred, plus CLOUDFLARE_ACCOUNT_ID) and Vercel AI Gateway (AI_GATEWAY_API_KEY). Set JEV_PROVIDER to typesafe, openrouter, cloudflare, vercel or auto to select strictly; unknown names and missing credentials fail rather than falling through.

Invalid responses return specific codes such as answer_id_mismatch, invalid_distribution, invalid_noul, invalid_usage and invalid_model, while transport failures return request_failed, rate_limited or unavailable. ask() never throws a verdict, and the two consumers differ: jev-browser maps !ok to its own exception, jev-mcp maps it to invalid_response.

The TypeSafe transport retries 408/409/429/5xx up to three attempts, honoring Retry-After within the caller's abort signal. When 429 retries are exhausted it returns rate_limited, when 5xx retries are exhausted it returns unavailable, and results report the API's effective model rather than the requested alias.

`npm install @jkudish/jev-agent-tools`; it requires Node.js 22 or newer. The README's example imports ask, passes a state string, a questions object with a noul question, a model like jev-latest, and an AbortController signal.

Setting JEV_VERCEL_ZERO_DATA_RETENTION=1 or true requests Vercel's ZDR routing on every request; unset, empty, 0 or false leaves the request body unchanged, and any other value is a configuration error before a request is sent. Auto-selection prefers other configured carriers, so use JEV_PROVIDER=vercel when the restriction must hold.

It is a library, not an app: it transports typed questions and validates responses, leaving model choice and decision logic to callers — its two consumers are a browser tool and an MCP server. Our README copy ends mid-sentence in the provider-selection section, so the full diagnostics description is not covered here.