> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/router-agents.md).

# Router Agents

The router agent allows you to embed our testing software directly inside your fleet of routers, and measure performance in excess of 2.5 Gbps for tens of millions of homes. You can then use the results to demonstrate that you’re delivering on your promises.

## Agent Features

* Test scheduling – Different schedules may be configured for different tests. Different devices may have different schedules. Multiple instances of a single test may be configured.
  * [Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests) – We measure multiple network layers and different applications to assure your users' connection health and quality of experience.
* LMAP ([RFC 7594](https://datatracker.ietf.org/doc/rfc7594/)) client for remote configuration updates – The test schedule and device configuration can be remotely configured via your account, and internally uses the LMAP configuration protocol.
* Instant testing – Allows the remote execution of the download, upload and latency/loss measurements, with the real-time reporting of the results back to the caller.
* Cross-traffic detection – Defines the maximum amount of cross-traffic that you will allow when running tests. If this is exceeded, the tests will not run. The thresholds for this may be configured remotely.
* CPU load detection – A CPU usage threshold can be configured (and updated remotely) to set a maximum CPU load under which you will conduct tests.
* Test server discovery – The agent can determine the best server to use if provided a list of on-net or off-net servers via a short latency check to each.

## Where the Agents Test To

The router agent can execute tests to servers on your private on-net network and to any of our off-net servers (see [Test Server Methodology](https://docs.thousandeyes.com/product-documentation/connected-devices/test-management/test-targets/test-server-methodology) to learn more about on-net and off-net test servers). Agents can also execute tests to many application servers to simulate a real-world experience of a user accessing those applications. See [Dynamic Application Test Suites](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/dynamic-application-test-suites) for more information about some of our application server tests.

## How You Access Agent Data

We provide our ISP, government, and enterprise users with a user interface to access the measurement results and manage their devices, as well as several APIs (see [Accessing Your APIs](https://docs.thousandeyes.com/product-documentation/connected-devices/usage-guides/accessing-your-apis) for more information about the APIs we provide).

## Measurement Data Caching

The router agent caches measurement data locally when it cannot submit results to the ThousandEyes backend. When connectivity is restored, the agent submits the cached data.

The local cache has the following limits:

* **Maximum size:** 2 MB
* **Maximum retention period:** 24 hours


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/router-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.