Agent Revenue Auditor

A small, agent-friendly product that turns a public website URL into structured conversion, trust, SEO, and agent-readiness opportunities. Sell the same capability through:

1. an Apify Actor using Pay Per Event; and
2. a standalone HTTP API protected by x402.

It intentionally does not scrape LinkedIn, collect personal profiles, send outreach, or claim unverifiable revenue losses.

Apify products

Choose analysisMode in the Actor input:

• audit — $0.02 per successfully audited domain.
• leadQualification — $0.08 per successfully qualified domain, including priority, evidence, contactability, and a suggested pitch angle.
• competitorComparison — $0.05 per successfully audited domain, followed by an uncharged ranked comparison row. Requires at least two domains.

Invalid URLs and failed fetches are returned transparently and are not charged. Use maxUrls to cap a run at 20 domains and combine it with Apify's maximum-charge control for a hard spending limit.

Output

Each result contains an opportunity score, evidence-backed issues, priorities, detected signals, a recommended next action, and an optional commercial offer. The JSON is designed for autonomous agent consumption.

Run locally as an Apify Actor

npm install
npm test
npm run demo -- https://example.com

The demo prints one audit to stdout. After installing the Apify CLI, use apify actor:run to exercise the full Actor locally; its output is written under local Apify storage.

Publish to Apify

npm install -g apify-cli
apify login
apify push

In Publication → Monetization:

• choose Pay per event;
• define website-audit, lead-qualified, and competitor-compared as the events;
• charge $0.02, $0.08, and $0.05 respectively;
• do not pass platform usage costs separately to users;
• keep permissions limited and do not enable Standby;
• complete developer KYC;
• publish a public Store listing.

Those settings are required for Apify's agentic/x402 eligibility. Raise price only after measuring completion rate and compute cost.

Suggested Store title: Website Opportunity Auditor for AI Agents

Suggested one-line description: Evidence-backed conversion and technical website audits as structured JSON—one URL in, prioritized opportunities out.

Run the standalone x402 API

Copy .env.example values into your deployment environment, using a dedicated receiving wallet. Start on Base Sepolia, then switch to a facilitator-supported Base mainnet network only after testing.

$PAY_TO_ADDRESS=0x... npm run start:x402

Endpoints:

• GET /health — free readiness and price check
• GET /.well-known/x402.json — discovery document used by x402 Detector and compatible crawlers
• GET /openapi.json — free machine-readable API contract
• GET /llms.txt — free agent-oriented product description
• GET /v1/preflight?url=https://example.com — free URL availability check
• POST /v1/metadata — $0.005, body: { "url": "https://example.com" }
• POST /v1/audit — $0.02, body: { "url": "https://example.com" }
• POST /v1/history — $0.10, body: { "url": "https://example.com" }
• POST /v1/competitors — $0.25, body: { "urls": ["https://a.example", "https://b.example"] }

The first unpaid request receives HTTP 402 with payment requirements. An x402-capable agent retries with a PAYMENT-SIGNATURE header and receives the result after verification and settlement.

Positioning and pricing

• Discovery price: $0.02 per basic audit
• Later: $0.10 for performance data; $0.50 for multi-page audits; $2–$5 for an LLM-enriched remediation plan
• Primary buyer: autonomous research, sales, web-development, procurement, and due-diligence agents

Do not add expensive APIs before payment verification. For variable-cost LLM calls, use x402's upto scheme or a separate fixed-price endpoint with a strict token budget.

Production checklist

• Deploy the API behind HTTPS.
• Use a dedicated wallet and never commit its private key.
• Add rate limits and request logs without storing page bodies.
• Publish an OpenAPI document and an agent-oriented llms.txt.
• Add x402 Bazaar discovery metadata when the final public URL exists.
• Visit the public domain with x402 Detector and submit it to a2alist.ai after validation.
• Review target-site terms before crawling and honor robots/access restrictions where applicable.