Set up Blazing Agents
Get an API key, install the SDK, and confirm your backend can reach Blazing Agents.
Get an API key, install the TypeScript or Python SDK, and run a short check that proves your code can talk to Blazing Agents. You use the same project folder in the quickstart.
Before you begin
You need a Blazing Agents account and either Node.js 24 or later, or Python 3.11 or later. The SDKs run on your backend, never in a browser or mobile app.
Create an API key
Open API keys in the dashboard and create a key. Copy the full ba_... value right away: you see it only once.
Put the key in your shell environment. Both SDKs send it with every request.
export BLAZING_AGENTS_API_KEY="ba_..."Your terminal now has BLAZING_AGENTS_API_KEY set. Open a new terminal later and you need to export it again, or load it from your usual secret store.
Install the SDK
Create a project folder and install the SDK for your language.
mkdir blazing-quickstart && cd blazing-quickstart
npm init -y
npm pkg set type=module
npm install @blazingagents/sdk aiThe TypeScript SDK needs the ai package alongside it. When the install finishes, you have an empty project with the SDK ready to import.
Check the connection
Save this file in your project folder. It creates a client and lists the agents in your tenant, which changes nothing.
import { BlazingAgents } from "@blazingagents/sdk";
const client = new BlazingAgents({
apiKey: process.env.BLAZING_AGENTS_API_KEY!,
});
const { agents } = await client.agents.list();
console.log(`Connected. Your tenant has ${agents.length} agents.`);Run it with node check.ts or python check.py. The Python client reads BLAZING_AGENTS_API_KEY on its own; the TypeScript client takes it as apiKey. Neither needs a URL, because both point at https://api.blazingagents.com by default.
You see Connected. Your tenant has N agents. The count includes your admin agent, so a new tenant sees 1. If you see an authentication error instead, check that the key is exported in the same terminal and was copied in full. The errors reference explains every error code.
Keep your API key on the backend
Keep credentials on the backend
Never put an API key in a browser bundle, mobile app, log, or URL. Keep it in backend configuration only.
One key can reach every agent in your tenant. It identifies your backend, not your users. Your app still signs users in and decides what each one may do before it calls Blazing Agents.