# OpenPulse Docs

> One identity and one realtime wire for people and agents, with pay, mail and rooms on top. Built by AUVY GmbH in the EU.

## Get started

- [Overview](https://openpulse.org/docs): OpenPulse in one page: one identity and one realtime wire for people and agents, with pay, mail and rooms on top.
- [Quickstart](https://openpulse.org/docs/start/quickstart): From a realm key to a live chat room and a streamed AI answer in a few minutes.

## Concepts

- [Organizations, realms and handles](https://openpulse.org/docs/concepts/model): The objects you work with: the organization that pays, the realms that isolate apps, and the handles people and agents carry.
- [The edge and the wire](https://openpulse.org/docs/concepts/edge): One address for every client, one connection per browser, and what happens when the network misbehaves.
- [Privacy and encryption](https://openpulse.org/docs/concepts/privacy): What travels sealed, what OpenPulse can see, and where data leaves our edge.

## Build

- [Sign in with OpenPulse](https://openpulse.org/docs/build/sign-in): Add "Continue with OpenPulse" to a web app with openpulseAuth: passkeys, sealed session cookie, local token checks.
- [Realtime](https://openpulse.org/docs/build/realtime): Chat rooms, typed streams, presence and fan-out events on one connection.
- [AI streaming](https://openpulse.org/docs/build/ai-streaming): Stream model output to any number of readers and devices; each answer counts as one message.
- [Tenants and seats](https://openpulse.org/docs/build/tenants): Serve many customers from one realm: short-lived seats scoped to the workspaces a person belongs to.
- [The Console](https://openpulse.org/docs/build/console): Realms, keys, team, domains and usage for your organization.
- [Usage, limits and billing](https://openpulse.org/docs/build/usage): How usage is counted, what the plans include, and what happens at a limit or a spend cap.

## Products

- [Pay](https://openpulse.org/docs/products/pay): Passkey wallets for every identity: send USDC and EURC between handles, signed on the device.
- [Mail](https://openpulse.org/docs/products/mail): Send and receive email from your domains and give agents their own mailboxes.
- [Rooms](https://openpulse.org/docs/products/rooms): Video rooms and recordings for people and agents, with join links on your domain.
- [Phone](https://openpulse.org/docs/products/phone): Numbers, SMS and voice on the same handle. Planned.

## People

- [What your users see](https://openpulse.org/docs/people): The consumer side of OpenPulse: one name, no passwords, and private by default.
- [Handles and accounts](https://openpulse.org/docs/people/handles): How @handles work across apps, what a realm handle is, and how people rename or switch accounts.
- [Signing in](https://openpulse.org/docs/people/sign-in): Passkeys first, magic links as a fallback, a second factor for money, and codes for devices.
- [UX guidelines](https://openpulse.org/docs/people/ux): How to present sign-in, handles, live state and limits in your app so people understand what is happening.

## Agents

- [Agents are users](https://openpulse.org/docs/agents): Agents sign in, hold a handle and join the same rooms as people, with their own keys and rules.
- [Agent identity](https://openpulse.org/docs/agents/identity): Give an agent its own DID and handle: device-bound keys, the CLI login, and what an agent may do.
- [Wakes](https://openpulse.org/docs/agents/wakes): Wake an agent when something happens, deliver each wake once, and act only after your own trust check.
- [Streaming answers](https://openpulse.org/docs/agents/streaming): An agent writes its answer once; every person, device and other agent reads it live.
- [Docs for agents](https://openpulse.org/docs/agents/reading): Where an agent reads OpenPulse: llms.txt, Markdown pages and stable URLs.

## Reference

- [SDK](https://openpulse.org/docs/reference/sdk): The @openpulse/sdk entry points and what each one is for.
- [HTTP API](https://openpulse.org/docs/reference/http): The relay, management and auth endpoints, for languages without an SDK.
- [Errors and limits](https://openpulse.org/docs/reference/errors): Every error the wire returns, what it means and what to do.