NeuroLink
NeuroLink (neurolink.
Overview
NeuroLink is Juspay's open agent SDK (neurolink.ink). It adds a third inference type, decide, exposed as tryDecide() in application code. Under the hood that path uses TypeSafe Jev via documented gateway wiring so you get calibrated Choice, Score, and boolean answers for routing without inventing another HTTP client.
Problem: Agent frameworks treat chat and embeddings as the only inference modes, so routing, budgeting, and tool picks still devolve into JSON parsing games.
Built for: Teams building on NeuroLink who want decide() beside generate and embed, with typed booleans and choices in production control flow.
First indexed on Jev Directory: 2026-09-22
Creator and team
- Name
- Juspay
- Organization
- Juspay
- Handle
- @juspay
How Jev is used
- Role in the product flow
- Structured decide inference for routing, budgeting, compaction, and tool selection
- Primitives
- ChoiceScoreNoul
- State in
- Typed decide inputs per NeuroLink schema: candidate sets for Choice, rubric state for Score, yes-no propositions for boolean/Noul paths.
- Decision out
- Calibrated structured results consumed directly in TypeScript control flow (pick model, drop context chunk, allow tool, etc.).
- Configure TYPESAFE_API_KEY and gateway per NeuroLink docs
- Call tryDecide() with the schema for your routing or gate question
- NeuroLink forwards to TypeSafe Jev semantics
- App thresholds probabilities; on missing key the SDK fail-opens per README
NeuroLink is not wrapping Jev as a chat persona. decide is a first-class inference type next to chat and embed, which matters for payment-grade agents that cannot afford ambiguous prose. Documented uses include picking among models, trimming context when relevance scores fall, compacting transcripts with structured keep or drop signals, and routing tools. tryDecide() returns the same primitive families you would hand-roll against System One, but with NeuroLink's agent lifecycle and observability hooks. If the TypeSafe key is absent, the framework is explicit about failing open so dev laptops still run; production should set keys and monitor decide latency like any other dependency.
Features and stack
Features
- tryDecide() third inference type beside chat and embed
- Choice, Score, and boolean/Noul schemas in one SDK
- Documented model routing and context budgeting patterns
- Fail-open behavior without TYPESAFE_API_KEY
Stack
- TypeScript
- NeuroLink SDK
- Vercel AI Gateway
- TypeSafe System One
Pricing: Jev decide calls bill through your TypeSafe or gateway account; NeuroLink itself is open source.
Links
FAQ
- Is decide separate from chat completions?
- Yes. NeuroLink docs describe decide as its own inference type with tryDecide(), not a prompt hack on top of generate().
- What happens without a TypeSafe key?
- README documents fail-open behavior so local dev does not hard crash; production agents should configure TYPESAFE_API_KEY.
Related learn guides
Original Jev guidance that pairs with this product pattern.
- Vercel AI Gateway Jev
Try typesafe-ai/jev through Vercel's gateway and the AI SDK evaluate path.
- Jev & TypeSafe
A primer for builders who need to know what Jev is, who it is for, and when TypeSafe docs should take over from this directory.
Related products
Hand-picked neighbors with rich profiles or overlapping tags.