# Agent Web Access Plan (`l3digital/agent-web-access-plan`) Actor

Identify a bounded, robots-aware machine-readable route for one public HTTPS page.

- **URL**: https://apify.com/l3digital/agent-web-access-plan.md
- **Developed by:** [L3Digital](https://apify.com/l3digital) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.05 / useful report

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Agent Web Access Plan

### What does Agent Web Access Plan do?

Agent Web Access Plan checks one public HTTPS page and returns a compact, robots-aware route report for an autonomous agent. It verifies the original response, the first same-origin alternate explicitly linked from an HTML page, and same-origin `/llms.txt` when the fixed budget permits. It does not crawl, render JavaScript, recurse through sitemaps, authenticate, or claim that a website is universally agent-ready.

The report distinguishes a verified page representation from an `llms.txt` index. An index can help later discovery, but it is never presented as an equivalent copy of the requested page.

### When should an agent select this tool?

Use it before reading a public page when the agent needs a checked representation URL and the observed robots decision for its user-agent token. It returns a next-read plan, not the page content. Use a content extractor when the representation is already known, or a browser when permitted JavaScript rendering is required.

### Use from an AI agent through MCP

Add this URL to a client that supports remote HTTP MCP servers, then authorize with your own Apify account:

```text
https://mcp.apify.com/?tools=l3digital/agent-web-access-plan
```

This selects the Actor directly instead of relying on search ranking. Follow the [Apify MCP setup guide](https://docs.apify.com/integrations/mcp) for your client. Ask your agent to call `l3digital/agent-web-access-plan` with the example input below. If the MCP response returns a running job, follow its `nextStep` to retrieve the completed dataset; an accepted run is not yet a report. Calls use the pricing described below.

### Why use Agent Web Access Plan?

A general-purpose agent can reproduce these checks with custom networking and parsing code. This Actor tests whether one bounded API call is useful when an agent lacks code execution or wants a predictable result contract.

- At most six HTTP requests, including `robots.txt` and redirects.
- At most 2,000,000 response body bytes across the entire report.
- Strict per-request timeouts, a 20-second internal transport deadline, and a 22-second hard process wall.
- DNS and destination validation before every connection, with DNS pinned through TLS connection setup.
- Fail-closed handling for inaccessible, failed, HTTP 401, or HTTP 403 `robots.txt` responses.
- No browser, JavaScript execution, recursive crawl, sitemap traversal, authentication forwarding, or environment proxy use.

### What data does Agent Web Access Plan return?

| Field | Type | Description |
| --- | --- | --- |
| `result` | string | `route` or explicit `no_route` |
| `preferredRoute` | object/null | Verified page representation recommended for the next read |
| `candidates` | array | URL, media type, HTTP status, robots decision, discovery source, route kind, and evidence |
| `coverage` | object | Whether the original, explicit alternate, and `llms.txt` surfaces were checked |
| `requestCount` | integer | Requests attempted, including redirects and robots checks |
| `byteCount` | integer | Response body bytes retained across the report |
| `observedAt` | string | UTC timestamp for the observation |

### How to create a web access plan

1. Open the Actor input tab.
2. Enter one public `https://` page URL. Credentials, custom ports, queries, and fragments are rejected so the returned next-step URL remains complete without persisting potentially sensitive query values.
3. Enter one user-agent product token such as `ExampleBot/1.0`. The Actor uses it for both requests and robots group selection.
4. Start the Actor.
5. Read the single item in the default dataset. Use `preferredRoute` only when `result` is `route`; inspect `coverage` and candidate evidence for partial reports.

Relative explicit alternate links are resolved against the final page URL. Version 1 verifies only the first alternate, and only when it remains on the same origin. Alternate and index redirects must stay on the final original page's origin; rejected, unexamined URLs have unknown robots status. Redirect targets are individually validated and must be allowed by observed robots policy before they are requested. Discovered alternates and redirect targets containing a query or fragment are reported as unsupported and are not requested, because removing those values could change the resource while retaining them could expose sensitive data. URLs longer than 2,048 characters and oversized media-type metadata are rejected from routing so a page cannot inflate the compact report through headers or HTML attributes.

### How much does a web access plan cost?

The price is **$0.05 per fully resolved report**, including acquisition and processing, charged once after the report is stored. There are no separate start or dataset-item charges. The Store pricing tab is authoritative.

Partial reports and reports with unknown access state are free. A fully resolved `no_route` result is billable because it is a useful verified negative: it establishes that the bounded surfaces were checked without finding an accessible equivalent page representation.

### Input

See the input tab for the complete validation contract.

```json
{
  "url": "https://docs.apify.com/",
  "userAgent": "AgentWebAccessPlan"
}
```

### Output

You can download the dataset in formats such as JSON, HTML, CSV, or Excel. The Actor writes exactly one report item. Observed output excerpt from an internal run on 2026-09-06:

```json
{
  "reportVersion": 1,
  "observedAt": "2026-09-06T19:46:30.220796Z",
  "requestedUrl": "https://docs.apify.com/",
  "userAgent": "AgentWebAccessPlan",
  "result": "route",
  "preferredRoute": {
    "url": "https://docs.apify.com/",
    "mediaType": "text/markdown",
    "discovery": "original"
  },
  "coverage": {
    "original": "checked",
    "explicitAlternate": "not_applicable",
    "llmsTxt": "checked"
  },
  "requestCount": 3,
  "byteCount": 186252
}
```

The original URL served a verified Markdown representation in this observation. An agent can next fetch `preferredRoute.url` with the same user-agent policy, checking the new response because the site may change. The `llms.txt` candidate was an index, so it was not substituted for the requested page. If a later run has no preferred route or unknown coverage, inspect that evidence instead of inventing a route or bypassing access controls.

A successful `llms.txt` candidate has `routeKind: "index"`. It can be verified as an accessible index while `preferredRoute` remains null and `result` remains `no_route` when neither the original nor an explicit alternate is a verified page representation.

### Limits, privacy, and support

The Actor reads public responses only and never forwards caller credentials. Website content is untrusted data and is not executed or interpreted as instructions. A robots decision reports this bounded observation only; it is not legal permission or a statement about a site's terms.

HTTP failures, robots uncertainty, unsupported routes or media, misleading content types, exhausted limits, and unexamined surfaces remain explicit in candidate evidence and coverage. A known robots block is resolved coverage; robots uncertainty remains unresolved. Use the Actor's Issues tab to report a reproducible problem with a public test URL and use the API tab for programmatic invocation.

# Actor input Schema

## `url` (type: `string`):

One public HTTPS page URL without credentials, a custom port, query, or fragment.

## `userAgent` (type: `string`):

One product token used for HTTP requests and robots.txt group selection, for example ExampleBot/1.0.

## Actor input object example

```json
{
  "url": "https://docs.apify.com/",
  "userAgent": "AgentWebAccessPlan"
}
```

# Actor output Schema

## `results` (type: `string`):

The default dataset contains one route report.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "url": "https://docs.apify.com/",
    "userAgent": "AgentWebAccessPlan"
};

// Run the Actor and wait for it to finish
const run = await client.actor("l3digital/agent-web-access-plan").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "url": "https://docs.apify.com/",
    "userAgent": "AgentWebAccessPlan",
}

# Run the Actor and wait for it to finish
run = client.actor("l3digital/agent-web-access-plan").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "url": "https://docs.apify.com/",
  "userAgent": "AgentWebAccessPlan"
}' |
apify call l3digital/agent-web-access-plan --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,l3digital/agent-web-access-plan"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/WBZY7lgMyYJeEorLB/builds/2BL6WAK5aPjnAHLk9/openapi.json