Skip to main content
Install the Flint AI TypeScript SDK to route your LLM traffic through the guardrails proxy. The SDK wraps your existing LLM client with a single function call — no code changes needed beyond the initial setup.

Flint AI on GitHub

Source code, example agents, and issue tracking

​
Requirements

  • Node.js 18 or later
  • npm, pnpm, or yarn

​
Install the SDK

The base package has no runtime dependencies. Each provider library is an optional peer dependency, loaded only when you route through that provider — install the ones you use:
For LangChain chat models, install the matching LangChain package (@langchain/openai, @langchain/anthropic, or @langchain/google-genai).
Every peer is optional and loaded dynamically, so a missing one surfaces only when you route through that provider — with a clear “install X” error — not at install time. For the three LLM SDKs, wrap() also enforces the range at runtime and throws if the installed version is below the minimum or above the maximum supported major.

​
Verify your installation

You should see the installed version number (such as 0.3.1).

​
Module formats

The SDK ships both ES module and CommonJS builds with TypeScript types, so it works in either module system:
The Google ADK plugin is a subpath export:
Cannot find module '@sandboxaq/flintai-sdk-ts'Confirm the install completed in the same project where you import it, and that your package.json lists it under dependencies.Cannot find module 'openai' (or another provider) at runtimePeers are loaded dynamically, so a provider you route through must be installed. Add the peer for that provider — see the table above.Provider version warning or error from wrap()wrap() reads the installed provider version and rejects one outside the supported range. Install a version within the range shown above:
Provider auto-detection fails when multiple provider keys are setIf more than one provider API key is present in your environment (OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY), the SDK cannot tell which provider you mean, so auto-detection fails. This is common in local development. Call init() with an explicit provider before wrapping:

​
Next steps

Configuration

Set up gateway URL, API keys, and environment variables

Monitor agents at runtime

Get your first traces in less than 10 minutes