# REVU Developers

> Official documentation for the REVU SDKs. One-line autocapture, first-party identity, and durable batched transport. Built so any developer, LLM, or AI agent can integrate REVU effortlessly.

## Web SDK

- [Overview](https://developers.revu.ai/web/index.md): The reference manual for @revu-ai/core. The package README covers the pitch, install, and your first event in 60 seconds; this tree covers everything else.
- [Install](https://developers.revu.ai/web/install.md): Two paths, pick the one that matches how your site is built.
- [Concepts](https://developers.revu.ai/web/concepts.md): The mental model behind the SDK. Four ideas cover almost everything you will run into: identity, sessions, the canonical event shape, and the "interactions, never values" rule.
- [API reference](https://developers.revu.ai/web/api.md): The default export of @revu-ai/core is a singleton bound to a single client. Every public method is wrapped so internal errors are swallowed and (in debug: true) logged. The SDK never throws into...
- [Configuration](https://developers.revu.ai/web/configuration.md): Every option passed to revu.init({ ... }) is optional except apiKey. Defaults are tuned to be the right answer for a typical product surface.
- [Privacy and data](https://developers.revu.ai/web/privacy.md): The SDK captures interactions, not values. The boundary is deliberately broad and enforced at the source of capture, not at the ingest endpoint.
- [Transport and offline](https://developers.revu.ai/web/transport.md): Events do not get lost when the network is hostile or the page is closing. Three layers cooperate to make that true: a durable queue, a retrying transport, and two terminal flush paths for unload.
- [First-party ingest](https://developers.revu.ai/web/first-party-ingest.md): By default the SDK sends events to https://api.revu.ai. You can instead route them through your own domain so the requests are first-party. This is a data-completeness measure: some browser...
- [Plugins](https://developers.revu.ai/web/plugins.md): A plugin extends the SDK with new event types or behaviors without bloating the core. Every plugin implements the same minimal contract, regardless of how it is distributed.
- [Troubleshooting](https://developers.revu.ai/web/troubleshooting.md): The SDK fails closed and never throws into the host page, so most problems show up as "no events arrive" rather than as a stack trace. The flow below isolates the cause.
- [Changelog](https://developers.revu.ai/web/changelog.md): All notable changes to @revu-ai/core are documented here.

## Android SDK

- [Overview](https://developers.revu.ai/android/index.md): The REVU Android SDK - a Kotlin capture core mirroring the web SDK contract. In development.

## iOS SDK

- [Overview](https://developers.revu.ai/ios/index.md): The REVU iOS SDK - a Swift capture core mirroring the web SDK contract. In development.

## Ingest API

- [Overview](https://developers.revu.ai/api/index.md): The REVU behavior ingest contract every SDK targets - one endpoint that accepts batched behavioral events.
- [API reference](https://developers.revu.ai/api/reference.md): REVU SDKs capture behavioral events client-side, batch them, and POST them to this endpoint. The SDK only captures; the server validates, attributes, and stores. Authentication is a public,...