Skip to content

Agents

Use TypeFuse from your coding agent.

Claude Code, Codex and claude.ai can build, test and call your Decisions. Install the skill, add the TypeFuse tools, then sign in in your browser when the agent asks.

You need an invite to use TypeFuse. Join the preview

Claude Code

In your terminal, with the TypeFuse skill and tools.

  1. Install TypeFuse

    This installs the skill, which teaches Claude Code how to build, test and call Decisions, and adds the TypeFuse tools.

    In your terminal
    curl -fsSL https://typefuse.dev/install | sh

  2. Sign in

    In Claude Code, run /mcp, choose typefuse and then Authenticate. Your browser opens TypeFuse so you can confirm.

  3. Ask your agent

    A first prompt
    Use TypeFuse to build a Decision that judges <what you want decided>. Write three to five Examples, evaluate it, and tell me before you publish.

The install script writes only under ~/.claude and ~/.codex. View the script before you run it.

Any agent

Or let your agent set itself up.

Paste this into any coding agent. It reads the same steps as Markdown and tells you when it needs you.

Paste into your agent
Install the TypeFuse skill and MCP server from https://typefuse.dev/agents.md, then ask me to sign in.
The steps as Markdown
https://typefuse.dev/agents.md

Automation

Run it from CI.

A job or an agent that runs without you can't sign in with a browser. It uses a personal access token instead: give it the least access the job needs (Read, Run or Full), keep it in the job's secrets, and revoke it when the job no longer needs it.

API reference

  1. Create an access token

    Never paste it into a conversation with an agent.

    Open Access tokens

  2. Use it from the CLI or the SDK

    Set it in the job's environment. TYPEFUSE_TOKEN wins over a stored sign-in; typefuse login --token stores it instead.

    In the job's environment
    export TYPEFUSE_API=https://api.typefuse.dev
export TYPEFUSE_TOKEN=tf_pat_…
# or: typefuse login --token tf_pat_… --api https://api.typefuse.dev

  3. Or give an agent the TypeFuse tools with the token

    The MCP server takes the token as a bearer header, so no browser is needed. The install script does this for Claude Code when TYPEFUSE_TOKEN is set.

    In the agent's terminal
    claude mcp add --transport http --scope user typefuse https://api.typefuse.dev/v1/mcp --header "Authorization: Bearer $TYPEFUSE_TOKEN"
codex mcp add typefuse --url https://api.typefuse.dev/v1/mcp --bearer-token-env-var TYPEFUSE_TOKEN

From your application

Calling a Decision from your app.

Every Decision is answered by TypeSafe, the AI model provider TypeFuse runs on. The three ways differ in whose TypeSafe key answers and who sends the request.

  • BYOK

    Default

    Your app sends its own TypeSafe key with each call; TypeFuse uses it for that call and never stores it.

    createRuntime({ apiKey, typesafeKey })

  • Relay

    For a key that must never leave your systems. TypeFuse prepares the request, your app sends it to TypeSafe and hands the response back. A little slower, no shadows, and the audit marks responses as reported by your app.

    add route: "relay"

  • Managed

    Enterprise

    TypeFuse's own key answers and the usage is billed; Enterprise, by contract.

Connect your first agent.

Create an account