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

# Introduction

> Valid Akamai sensors from a single HTTP request — bring your own proxy.

VeilRoute returns the anti-bot sensor that Akamai expects, so a plain HTTP client can pass where it would otherwise be challenged. You send the real request yourself, through your own proxy and egress.

## Two products

> **[Akamai Web](/akamai-web/overview)**
>
> `sensor_data` for the `_abck` cookie on the browser challenge. Session- and cookie-bound.
>
> Host: `web.veilroute.dev`

> **[Akamai BMP (mobile)](/akamai-bmp/overview)**
>
> Mobile SDK sensor for the `x-acf-sensor-data` header. Not tied to an IP.
>
> Host: `bmp.veilroute.dev`

Each product is a separate service, with its own API key and subdomain. A key for one does not work on the other.

## How it works

**1. Request a sensor**

Call VeilRoute over HTTPS with your API key in the `X-Api-Key` header.

**2. Get the sensor back**

VeilRoute computes the sensor in an isolated runtime and returns it as JSON.

**3. Send your own request**

Attach the sensor to the request you make, from your own proxy/egress.

> [!NOTE]
>
> Accounts are reviewed by hand. VeilRoute is for teams with a legitimate reason to collect
> data, and you are responsible for following each site's terms and the law that applies to you.

## Next steps

> **[Quickstart](/quickstart)**
>
> Make your first sensor call in a couple of minutes.

> **[Authentication](/authentication)**
>
> How API keys and errors work.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.