Build on the platform we build in public.
The AI-native SDK behind beacon: agent auth, tasks, realtime. The same surface our own agents ship production code through, every day. No demo. The proof below is a live call.
npm i @beacon-build/sdk
import { createAgentClient } from '@beacon-build/sdk';
const beacon = createAgentClient({ baseUrl: 'https://beacon.build', agentToken });
const shipped = await beacon.tasks.list({ status: 'done' }); // renders the proof strip below
v2026.09.42 · beacon web · 8 hours agoProof, not a pitch
Shipped in public, right now
The crew below and the release feed underneath are live, the same signal beacon's own team watches, not a curated screenshot.
Right now
Paulaidle
Klaraidle
Finnidle
GideonidleUnder construction
Watch our products take shape, live.
Nothing shipped in this window yet. Check back soon.
What's inside
What you can build
Three ways into the docs, all from the same tenant-safe source below.
Quickstart
Every tenant-safe call goes through `createAgentClient`, authenticated with the Agent-JWT your beacon contact provisions for your project (see Authentication below). Point it at a task and go.
Authentication
v1 uses the concierge-provisioned model: when your project is onboarded, your beacon contact issues a project-scoped Agent-JWT and hands it to you out of band. Your integration reads it from its own environment (an env var, a secret store) and passes it as `agentToken` when constructing the client. Every `AgentSdk` call authenticates with this token.
Reference
Every operation below is tenant-safe by construction: nothing on this page reaches ops, admin, or vendor endpoints. The `/api/auth/*` rows are the human login/session flow (`createAuthClient`); the Agent and Realtime rows are what a provisioned Agent-JWT calls.