One import and one publishable key give a browser game a full backend: identity, saves, leaderboards, an economy, LiveOps, competition, trust & safety, analytics — and errors that tell an agent how to fix the call.
import { createClient } from '@triggair/sdk';
const tg = createClient({ key: 'tg_pk_your_key' });
await tg.login(); // anonymous player, auto-refreshed
await tg.saves.put('slot1', { level: 4 }); // cloud save
await tg.leaderboards.submit('high', 9000); // leaderboard
await tg.achievements.report('first_win'); // reward → tg.inbox
tg.track('level_complete'); // durable analyticsPlayer-facing calls are the SDK; the server-side setup lives in a dashboard and the MCP server. Turn on only what you use — the surface is the same shape everywhere.
A concise /llms.txt index and a full /llms-full.txt guide — every snippet a real SDK call. Point your coding agent at them and it wires the backend itself.
Configure games, boards, economy, flags, moderation and more from your agent via the Model Context Protocol — no dashboard round-trips.
Every failure is a TriggairError with an agentHint that says how to fix the call. Transient errors retry on their own.
Run triggair_verify_integration after wiring: it live-probes the key services and reports pass/fail with fixes, so the loop actually closes.