# Agent Preflight — URL Access Check

> Agent Preflight — URL Access Check is a paid API for AI agents from preflight.lorensaisolutions.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Analyzes a URL to detect reachability, login walls, CAPTCHA challenges, and browser requirements before an agent attempts to access it

## Facts

- Endpoint: GET https://preflight.lorensaisolutions.com/v1/access-check
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-preflight-url-access-check-05eecdaf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YxZ6b8btVMLUU8fYBiqUQ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-preflight-url-access-check-05eecdaf
```

Example prompt: Before I try to scrape https://example.com/products, can you run a preflight access check on it with a 'scrape' intent so I know whether it has a login wall, CAPTCHA, or needs a real browser?

## When to prefer this

Use this endpoint when an AI agent needs to determine the feasibility of accessing a URL before committing resources — especially when you need to know upfront whether authentication, a headless browser, or CAPTCHA solving will be required. Ideal for agent pipelines that branch based on access difficulty, or for swarms doing pre-screening of many URLs before dispatching specialized workers.

## Known failure modes

- URL is malformed or not absolute HTTP/HTTPS — schema validation error returned
- Target URL is unreachable or returns a network error — reachable: false with no further analysis
- Rate limit or payment failure (x402) — 402 or 429 response before analysis begins
- Target URL returns non-standard response that reduces confidence score
- intent enum value not recognized — request rejected with validation error

## How this service works

Paid URL analysis, CAPTCHA and login detection, API discovery, product intelligence, change monitoring, and batch preflight for AI agents and agent swarms.

## Output

A JSON object with boolean flags for reachability, login requirement, bot challenge detection, and browser requirement, plus a recommended access method (e.g. 'browser_with_authentication'), automation difficulty rating, risk flags array, confidence score, HTTP status code, final resolved URL, latency in ms, robots.txt info, and a timestamp.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "finalUrl": "https://example.com/",
  "pageType": "website",
  "reachable": true,
  "riskFlags": [],
  "confidence": 0.92,
  "httpStatus": 200,
  "contentType": "text/html",
  "loginRequired": false,
  "captchaPresent": false,
  "browserRequired": false,
  "recommendedAction": "Use direct fetch",
  "botProtectionPresent": false,
  "directFetchSufficient": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-preflight-url-access-check-05eecdaf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from preflight.lorensaisolutions.com](https://www.zero.xyz/host/preflight.lorensaisolutions.com/llms.txt)
