> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/scout/agent/axis-agent.md).

# Axis Agent

## Overview

The Rekor Axis Agent is a lightweight on-camera ACAP application that turns any supported Axis IP camera into an ALPR capture device for the Rekor Cloud. It captures H.264 video, runs motion detection locally, records motion-triggered clips to the camera's SD card, and uploads them to Rekor Cloud where the heavy license-plate-recognition and vehicle-detection work runs. The agent itself does **no** plate recognition on the camera — it is a thin edge client.

### Supported Hardware

| ARTPEC chip | Architecture | Examples                       | Agent architecture string |
| ----------- | ------------ | ------------------------------ | ------------------------- |
| ARTPEC-8    | 64-bit ARM   | \[TODO: list models]           | `aarch64`                 |
| ARTPEC-9    | 64-bit ARM   | P1485-LE, \[TODO: more models] | `aarch64`                 |

**Older silicon:** ARTPEC-6 and ARTPEC-7 (`armv7hf`) were supported through 2.0.1 but were dropped from 2.0.2 per the Q2 2026 PRD. Cameras already running 2.0.1 on those chips will keep working; new deployments target ARTPEC-8/9 only.

### Firmware Requirements

| Firmware         | Status                                                            |
| ---------------- | ----------------------------------------------------------------- |
| 10.x and earlier | **Not supported**                                                 |
| 11.0.x           | Known issues with reverseProxy manifest — upgrade recommended     |
| 11.11 LTS        | **Recommended**, fully tested                                     |
| 12.x             | Partial — `axstorage` and `axhttp` DBus issues (see Known Issues) |

### Supported Features

| Feature                    | Supported | Notes                                   |
| -------------------------- | --------- | --------------------------------------- |
| License plate recognition  | ✅         | Processed in Rekor Cloud, not on camera |
| Vehicle detection          | ✅         | Via uploaded clip processing            |
| Motion-triggered recording | ✅         | RAPP-based on-camera detection          |
| Real-time event emission   | ⚠️        | Events flow through cloud after upload  |
| Local LPR inference        | ❌         | Not available — upload-only model       |
| On-camera models / OTA     | ❌         | Agent is stateless beyond settings.json |
| Cloud archive-only mode    | ✅         | `skip_processing` flag                  |

#### Differences vs. Other Rekor Agents <a href="#differences-vs.-other-rekor-agents" id="differences-vs.-other-rekor-agents"></a>

| vs.                         | Key difference                                                                            |
| --------------------------- | ----------------------------------------------------------------------------------------- |
| **Rekor Scout on a server** | No local inference; cloud does all LPR work. Lower CPU/RAM, higher bandwidth.             |
| **Rekor Edge box**          | No dedicated GPU; motion detection is pixel-diff, not DNN. Suitable for low-volume sites. |

***

### 2. Prerequisites <a href="#id-2.-prerequisites" id="id-2.-prerequisites"></a>

#### Camera hardware <a href="#camera-hardware" id="camera-hardware"></a>

* Axis camera with ARTPEC-8 or ARTPEC-9 chipset
* **SD card or network storage** mounted and writable (agent refuses to record without usable storage)
* Firmware **11.11 LTS or newer** strongly recommended
* Minimum \~80 MB free on storage (per `MIN_STORAGE_SPACE_TO_WRITE_BYTES`)

#### Licensing <a href="#licensing" id="licensing"></a>

* A Rekor Cloud account with LPR entitlements enabled for the target site
* A per-camera license slot in the Rekor Cloud dashboard. \[TODO: describe license provisioning flow and how many slots per tier]

#### Network <a href="#network" id="network"></a>

Outbound (from the camera):

| Protocol    | Destination                        | Purpose                                                            |
| ----------- | ---------------------------------- | ------------------------------------------------------------------ |
| HTTPS (443) | `cloud.openalpr.com`               | Default Rekor Cloud endpoint. Configurable via `remote_server_url` |
| HTTPS (443) | \[TODO: staging URL if applicable] | Staging/pre-prod                                                   |
| NTP (123)   | Camera's configured NTP servers    | Video timestamps and heartbeat timing                              |
| DNS (53)    | Camera's configured DNS servers    | Resolve cloud hostname                                             |

Inbound to camera (for admin/operator):

| Protocol | Port | Purpose                                                            |
| -------- | ---- | ------------------------------------------------------------------ |
| HTTPS    | 443  | Camera web UI and VAPIX — used to access the agent's settings page |

No direct inbound connection to the agent is required; the cloud never initiates requests to the camera. All communication is push from the agent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rekor.ai/scout/agent/axis-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
