# keeps

> Observability for generative media — capture an asset, append events.

## Docs

- [API reference](https://docs.keeps.dev/api-reference.md): Every public function in the keeps SDK — exact signatures, parameters, return values, and examples.
- [Core concepts](https://docs.keeps.dev/core-concepts.md): The data model behind keeps — immutable events, assets, properties, and how the backend folds them into one row per generation.
- [HTTP ingestion API](https://docs.keeps.dev/http-api.md): Send events as raw JSON over HTTPS — the full POST /v1/events contract for Node, Go, or any stack without the Python SDK.
- [Introduction](https://docs.keeps.dev/introduction.md): PostHog for generative media — a side-band observability layer for apps that generate images, video, and audio with models.
- [Privacy & safety](https://docs.keeps.dev/privacy-and-safety.md): Why keeps is safe to drop into a production app — references not bytes, server-derived tenancy, never in the request path, and fail-open by design.
- [Quickstart](https://docs.keeps.dev/quickstart.md): From zero to a generation event on your dashboard in about five minutes.
- [Recording provider calls](https://docs.keeps.dev/recording-provider-calls.md): Instrument fal, Replicate, and OpenAI calls by hand — submit, run, finish — all on one asset_id.
- [Reliability & delivery](https://docs.keeps.dev/reliability.md): How Lens delivers events: fail-open, best-effort, and the one call you must make in short-lived processes.