> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reflecto.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

The Reflecto API is the public HTTP front door for sending notifications to
your own paired devices — your Android phone and any browser extensions you've
paired with it. It's designed for the same job as Pushover or the old
Pushbullet API: a single HTTPS call from a script, cron job, or webhook puts
a notification on every screen you own.

Reflecto is **end-to-end encrypted by default**. Notifications you mirror from
your phone never reach the server in plaintext. The public API is a small,
deliberate exception: payloads sent through `/v1/send` live in server RAM
only long enough to be encrypted to each recipient device, then are
discarded. See [Encryption](/guides/encryption) for the full trust
posture.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/guides/quickstart">
    Send your first notification with one curl command.
  </Card>

  <Card title="Authentication" icon="key" href="/guides/authentication">
    How `rfk_live_…` tokens work and where to get one.
  </Card>

  <Card title="Rate limits" icon="gauge" href="/guides/rate-limits">
    Per-token, per-IP, and per-receiver quotas.
  </Card>

  <Card title="Pushover compatibility" icon="arrow-right-arrow-left" href="/guides/pushover-compatibility">
    Drop-in shim — change one URL.
  </Card>
</CardGroup>

## Who this is for

* **Self-hosters** wiring up Pi-hole, Uptime Kuma, Home Assistant, or any
  service that can hit a generic webhook.
* **Developers** who want a notification channel for shell scripts, CI runs,
  cron jobs, or backup pipelines.
* **Pushover and Pushbullet refugees** looking for a privacy-first
  replacement with a familiar surface area.