Agent Commerce Scanner — x402, MCP & AI Monetization Kit

Audit any public website for AI-agent commerce readiness. Detect MCP, x402, llms.txt, OpenAPI, AI crawler permissions, machine-readable pricing, licensing signals, and structured data—then identify monetization opportunities and generate a ready-to-deploy agent commerce kit.

Use it for one domain or a batch of domains when you need to answer three questions:

1. Can AI agents access and understand this site?
2. What could an agent plausibly buy from it?
3. What infrastructure is missing to make that commerce machine-readable and payable?

What this Actor does

1. Commerce scan

Checks public signals including:

• robots.txt and common AI crawler rules
• Cloudflare-style Content-Signal
• llms.txt / llms-full.txt
• sitemap availability
• JSON-LD / schema types
• OpenAPI / Swagger discovery
• MCP clues and endpoints
• x402 v2 402 Payment Required and PAYMENT-REQUIRED signals
• machine-readable pricing
• TDMRep headers and /.well-known/tdmrep.json
• common technology signals such as Cloudflare, WordPress, Shopify, PHP, Node, and Next.js

Each scan includes a structured agent-commerce readiness score and the evidence behind it.

2. Monetization analysis

Maps plausible machine-purchasable resources such as structured search, datasets, content retrieval, inventory lookup, or API/tool access.

For each opportunity, the Actor can suggest:

• resource type
• endpoint idea
• pay-per-request model
• starting price
• rationale
• confidence level
• recommended launch order

3. Deployment kit

In full mode, the Actor generates a downloadable ZIP with starter infrastructure such as:

• llms.txt
• llms-full.txt
• robots.txt.patch
• .well-known/tdmrep.json
• .well-known/agent-commerce.json
• openapi.json
• Node x402 payment sidecar
• Bazaar discovery metadata starter
• WordPress discovery helper
• PHP discovery helper
• deployment README

The kit is a starting point. Connect generated endpoints to your real data, content, service, or tool before production use.

Input

{
  "domains": [
    "https://example.com",
    "another-site.com"
  ],
  "mode": "full",
  "maxConcurrency": 4,
  "requestTimeoutSecs": 12,
  "generateLlmsFull": true
}

Modes

• scan — technical commerce-readiness audit only
• analyze — scan + monetization opportunity map
• full — scan + analysis + downloadable deployment kit

Output

The default dataset contains a separate record for each completed stage:

• recordType: "scan"
• recordType: "analysis"
• recordType: "deployment_kit"
• recordType: "error" for inaccessible or invalid targets

For a successful full run on one domain, expect three dataset records: scan, analysis, and deployment kit.

Generated ZIP files are stored in the run's default key-value store using flat keys such as:

kit-example.com-agent-commerce-kit.zip

Pricing

This Actor uses Pay Per Event pricing:

Event	Price
Commerce scan	$0.02
Monetization analysis	$0.10
Deployment kit	$0.25

A complete full run for one successfully processed domain triggers all three product events.

Platform usage is included rather than charged separately.

Who this is for

Useful for:

• AI-agent and MCP developers
• API and data-product builders
• website owners exploring machine-to-machine monetization
• teams evaluating x402 readiness
• platforms auditing large domain sets for agent accessibility and commerce signals
• developers preparing existing websites for autonomous-agent discovery and payment

Security behavior

The Actor performs read-only public HTTP requests. It limits response sizes and redirects, rejects localhost/private/reserved IP targets, and re-validates redirected destinations.

It does not:

• log in to target sites
• submit forms
• bypass access controls
• scrape private data
• claim that an undocumented service does not exist

Accuracy notes

Detection is evidence-based. Some websites expose APIs, MCP servers, payment flows, or commercial resources only after authentication or at non-obvious URLs.

Suggested opportunities and prices are starting-point heuristics, not guarantees of demand or profitability. Validate rights, data provenance, customer value, operating cost, and unit economics before deploying generated monetization infrastructure.

Local development

npm install
export APIFY_LOCAL_STORAGE_DIR=./storage
npm start

When running outside Apify, billing events may not be recorded, but the scan, analysis, and kit-generation logic can still be exercised locally.