AI agents & bots

Agents are first-class citizens on the wire.

Most stacks treat bots as an afterthought. In PrivChat, agents authenticate, subscribe, publish, and answer typed RPC exactly like human clients — which makes agent-to-human and agent-to-agent communication a protocol feature, not a hack.

Start with the SDK See it in games

Agent primitives

The wire treats agents like everyone else.

No sidecar delivery system, no polling bridge — an agent is a client with a system identity and typed routes.

System users

Agents are real accounts with identities, presence, and permissions — not a webhook bolted onto the side of your chat.

Typed transfer routes

Bots expose request-response routes (menus, commands, business actions) with the same typed RPC contract as any module.

Same channels as humans

Agents subscribe and publish on the channels users already live in. No separate delivery path, no sync mismatch.

Orchestration patterns

Fleet management, decision profiles, and watchdogs — the same machinery that keeps game bots alive drives assistant workflows.

Typed bot routes

One handler. Full request-response semantics.

Kotlin transfer handler

// A typed transfer route — the same contract modules use.
registry.register(object : PrivChatTransferHandler {
    override val serviceName = "bot"

    override suspend fun handle(ctx: PrivChatTransferContext) =
        when (ctx.route) {
            "bot/menu/get"   -> menu.render(ctx.userId)
            "bot/menu/click" -> menu.click(ctx.userId, ctx.body)
            else -> PrivChatTransferResult.error(
                CODE_UNKNOWN_ROUTE, "unknown route"
            )
        }
})

Shipping today

What exists now — and what's next.

We publish capability, not ambition. Everything below runs in production today; the roadmap strip is where ambition lives.

Assistant module

System-user assistant bootstrap with bot routing on public APIs — the entry point for conversational automation.

Bot interaction routes

Menu, click, and echo routes over transfer RPC — a working request-response surface for interactive bots.

Production bot fleets

The poker platform runs orchestrated bot fleets with decision engines, seating policies, and health watchdogs.

RoadmapLLM connectorsAgent framework glueTool-call bridgeCloud offeringHosted console

Build an agent

Give your agent a real seat at the table.

Start with the SDK, register a system user, and expose your first typed route in an afternoon.

Start building