# Brivo API - LLM Documentation Router
# https://apidocs.brivo.com/llms.txt
# Generated: 2026-05-12

> This site documents two distinct, independent APIs. Most tasks involve only one.
> All documentation files are public and require no authentication. A 403 means the path is wrong.
> This site documents the APIs - it is NOT the runtime API. Do not send API requests to https://apidocs.brivo.com.

## IMPORTANT: Choose One API Before Fetching Any Files

Read the decision rule below and fetch ONLY the sub-guide that matches your task.
Do NOT fetch resources from both `access/` and `video/` in a single task
unless the user has explicitly confirmed their task spans both APIs.

## Decision Rule

**Access API** - fetch `https://apidocs.brivo.com/access/llms.txt` when the prompt mentions API-specific nouns like:
doors, sites, credentials, schedules, cards, readers, panels, locks, entry points,
access control, occupancy, or access events.

**Video API** - fetch `https://apidocs.brivo.com/video/llms.txt` when the prompt mentions API-specific nouns like:
cameras, recordings, streams, EEN, Eagle Eye, footage, live view, motion events,
video analytics, or camera health.

**Generic terms only** (events, users, alerts, permissions, groups, sites without an API-specific
noun like door or camera) - STOP. These are conceptual to both APIs and cannot disambiguate.
Ask the user before fetching anything.

**Unclear / both / neither** - STOP. Ask the user:
"Are you working with the Brivo Access API (doors, credentials, events) or
the Brivo Eagle Eye Video API (cameras, recordings, streams)?"
Do not fetch any further documentation until the user answers.

## API Sub-Guides

Fetch ONE of the following - never both unless the user confirms cross-API scope.

- https://apidocs.brivo.com/access/llms.txt - Brivo Access API (doors, credentials, events, users)
- https://apidocs.brivo.com/video/llms.txt  - Brivo Eagle Eye Video API (cameras, recordings, streams)