Composio
Composio agent SDK with an optional TypeSafe provider that uses Jev to shortlist and pick tools and closed-set arguments.
Overview
Composio is an SDK monorepo that gives AI agents more than 1000 pre-authenticated toolkits, per-user sessions, authentication, triggers and a sandbox, with TypeScript and Python SDKs, a CLI and adapters for many agent frameworks. Its provider list includes a TypeSafe (Jev) adapter, published as @composio/typesafe and composio-typesafe.
The Jev provider is an optional decision layer. According to the list summaries, it uses Jev to shortlist tools, select one from a bounded set, map closed-set arguments, and expose confidence plus a gate for destructive actions. Most of Composio is unrelated to decision models; the relevant piece is this provider, which lets an agent choose a tool without an LLM writing a tool call. Composio also exposes every session as a hosted MCP endpoint, so the same tools can be reached from MCP clients.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which tool from the shortlist should handle this request?(inferred) | — |
| Choice | Which allowed value should this closed-set argument take?(inferred) | — |
| Yes / no | Is this action destructive enough to require confirmation?(inferred) | yes · no |
How it works
- Create a Composio session and attach the TypeSafe provider
- Jev shortlists and selects a tool for the user's intent
- Closed-set arguments are mapped with confidence
- Destructive actions are gated before execution
Strengths
- Tool selection over a large catalogue without loading every definition into an LLM
- Confidence values per selection
- Part of a widely used integration SDK
Caveats
- The Jev provider is a small optional part of a large SDK
- Needs both a Composio and a TypeSafe key
- Provider behaviour described from list summaries, not the main README
Getting started
npm install @composio/core plus the @composio/typesafe provider (or pip install composio composio-typesafe), with COMPOSIO_API_KEY set.At a glance
- Type
- Project
- Status
- production
- Language
- TypeScript
- Runtime
- Node / Python SDK
- Has code
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
An optional TypeSafe provider for Composio that uses Jev to choose among tools and bounded argument options.
logicrw/awesome-jev-projectsTypeSafe provider that shortlists tools, selects one from a bounded set, maps closed-set arguments, and exposes confidence and destructive-action gates.
cobanov/awesome-jev
Frequently asked questions
Where does Jev fit in Composio?
As an optional provider adapter that chooses tools and closed-set arguments with Jev.
Is Composio itself a decision model?
No, it is a tool integration platform; Jev is one of many providers.
Which languages have the Jev provider?
Both TypeScript (@composio/typesafe) and Python (composio-typesafe).
Related projects
Six-file DSPy coding agent where Jev answers closed questions (safety, tool fit, history, delegation) and Python owns policy.
ProjectprototypePythonPython multi-agent runtime with native Jev support: agents ask typed questions via a decision client separate from the text model.
LibraryproductionPythonLangChain's Python framework, which includes an optional TypeSafeClassifier runnable plus model-routing and risky-tool middleware using Jev.
PluginproductionPythonLangChain.js, which includes an optional TypeSafeClassifier runnable and middleware for bounded routing and tool-call checks with Jev.
PluginproductionTypeScriptClaude Code mod that adds $.jev to the engine interface so other plugins and hooks can ask Jev typed questions through six providers.
ServicebetaTypeScriptUnofficial, read-only MCP server exposing Jev as four advisory tools: decide, route, risk score and yes/no gate.
MCP serverbetaTypeScript