# Agent Preflight URL Inspector

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

Analyzes a URL to detect CAPTCHA/login barriers, page type, pricing, availability, automation difficulty, and bot-challenge presence before an agent acts on it

## Facts

- Endpoint: GET https://preflight.lorensaisolutions.com/v1/preflight
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-preflight-url-inspector-8e44e5b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LD9UtLlA_dDMkb6B4RrYV

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-inspector-8e44e5b0
```

Example prompt: Before I try to scrape https://shop.example.com/product/123 for price and availability, do a preflight check on it with intent 'purchase' — tell me if it's reachable, whether there's a CAPTCHA or login wall, and how hard it would be to automate.

## When to prefer this

Use this endpoint before your agent attempts to scrape, purchase, book, or monitor a URL — especially when you need to know upfront whether the page has bot defenses, requires authentication, contains structured pricing data, or will redirect. Prefer it over blind fetching when automation difficulty and bot-challenge risk matter for downstream decisions.

## Known failure modes

- URL is unreachable — reachable:false with no further data
- Malformed or non-URI input causes validation error
- Target site blocks the preflight request, yielding incomplete detection
- CAPTCHA detected but page metadata still partially returned
- Login wall prevents full page inspection, requiresLogin:true with limited signals
- Timeout on slow target pages increases latencyMs significantly

## How this service works

Single-fetch URL intelligence, access checks, commerce signals, and risk.

## Output

Returns a JSON object with reachability status, HTTP status code, final URL after redirects, detected page type (product/login/booking/pdf/api_docs/article/data/generic), whether login is required, whether a bot challenge was detected, automation difficulty rating, detected price and currency, availability, whether structured data is present, risk flags, a recommended action, a confidence score, and request latency.

## 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-inspector-8e44e5b0/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)