DELXCOMMERCE Free guide

Guide · website inspection for agents

How to inspect a website before an AI agent relies on it

If an agent already has a URL, inspect only the public signal it needs: a compact site report, readable page text, domain data, or HTTP/TLS trust headers. Pay per delivered result after reading the exact contract.

website intelligencepage extractionHTTP headersTLSknown URLx402

The rule

Start with the URL you already have.

Website inspection and web search are different jobs. Inspection fetches a caller-supplied public URL and returns a bounded result. It does not discover URLs from a query, crawl an open-ended web, or make a private page public. When the URL is unknown, use an authorized search provider; do not treat a Delx extract route as search.

Choose by outcomeOne route at a time
You needStart hereWhy
Title, links, forms, contacts and feedsWebsite Intelligence ReportOne compact report for a known public URL.
Readable text from one pagePage ExtractBounded page content for routing, RAG prep or summarization.
Security, cache, redirect and server headersHTTP Headers InspectHeader-level preflight before an agent trusts a host.
Certificate and transport postureTLS InspectPublic TLS details without pretending to be a penetration test.
A/AAAA/MX/TXT or domain recordsDNS LookupStructured domain data for routing and verification.

Safe buyer flow

Discover → challenge → pay → verify.

Discovery is free. The payment challenge is the source of truth for the exact amount and resource; a challenge, crawler or index entry is not a sale.

# Free intent discovery
curl -sS 'https://api.delx.ai/api/v1/x402/start?q=inspect%20a%20website%20before%20relying%20on%20it'

# One bounded report after reviewing the live 402 challenge
npx agentcash@latest fetch https://api.delx.ai/api/v1/x402/website-intelligence-report \
  -m POST -H 'x-delx-source: guide-website-inspection' \
  --max-amount 0.01 -b '{"url":"https://example.com"}'

Recommended sequence

Use the smallest useful evidence.

  1. Orient for free. Ask the intent router or open the website pack; it returns governed paths, not unrelated substitutes.
  2. Inspect the contract. Check method, input schema, declared price, network, delivery and refund behavior in the paid OpenAPI and live 402 response.
  3. Pay one canonical route. Keep the request bounded to the URL and fields you need. Never send credentials or private tokens to a public inspection route.
  4. Verify before downstream use. Check status, final URL, returned fields and any receipt/hash before storing or acting on the result.

Evidence, not hype

Why this path is front-line for Delx.

Delx's sales-led report observed 11 external delivered sales in the web_inspection family through 2026-08-09, across DNS, email, headers, links, page extraction, TLS and URL-health routes. That is an internal delivery signal—not a market ranking, traffic forecast or guarantee. See the dated report and the honest market comparison.

Direct answers

Website inspection FAQ

02

Is this web search?

No. The caller supplies the URL. General web search remains a separate capability and is not sold by Delx without verified redistribution rights.

03

Does a 402 challenge prove delivery?

No. A challenge declares the payment contract. Delivery is proven only after the paid request returns the expected result and receipt.

04

Can I send a login or token?

No. Keep credentials and private data out of public routes. These pages describe bounded inspection of public URLs.