For AI agents.
Built into the platform.

One file, every snippet

docs.synq.id/llms.txt is the canonical machine-readable index of every doc page, install command, and copy-pasteable snippet on the docs site. Claude Code, Cursor, Windsurf — any agent that respects the convention can resolve "how do I ship Synq on Next.js?" with one HTTP fetch.

Fetch llms.txt

# from the agent
GET https://docs.synq.id/llms.txt

# returns: a single Markdown file with every doc page, install command,
# and drop-in snippet for the React / Next / RN / Solana Mobile SDKs.

Device flow — auth without a browser

CLIs, assistants embedded in other products, and headless tooling cannot pop a webview. Device flow is the OIDC grant designed for exactly this — the agent surfaces a URL + short code, the user opens it on a phone or laptop, grants consent, the agent polls until the session lands. RFC 8628.

Device flow in five lines

@synqid/js exports createDeviceFlow with built-in polling.

import { createSynqClient } from '@synqid/js'

const synq = await createSynqClient({
  issuer: 'https://api.synq.id',
  clientId: process.env.SYNQ_AGENT_CLIENT_ID!,
})

const flow = await synq.createDeviceFlow({
  scope: 'openid profile offline_access',
})

// Show the user where to authorize you
console.log(`Open ${flow.verification_uri_complete}`)

// Poll until the user completes consent
const session = await flow.poll()
// session.user, session.accessToken, …

The azp claim is the agent identity

Every access token carries an `azp` claim identifying the client App that authorized it. Your backend can branch on it to distinguish a request from your web app, your mobile app, and your AI agent — and the audit log surfaces it with every entry. Useful for rate limits, abuse detection, and audit trails that need to know which actor was responsible.

Pair it with

Common questions