BUYER EVIDENCE · LIVE CONTRACTS · NO KEYWORD THEATER

AI Agent API Evidence: Proof Before Payment

Free agent-to-agent discovery: Agent Commerce Engine accepts a job intent and a caller budget, routes against the canonical MCP inventory and can probe an exact server's live tools/list. No subscription, automatic wallet spend or made-up paid-delivery receipt. Remote MCP endpoint https://scriptmasterlabs.com/agent-commerce/mcp · Machine capability card.

New free tool: Inspect an x402 PAYMENT-REQUIRED quote locally to compare chain, token, receiver and budget without wallet access or signing. A matching quote is not payment evidence.

ScriptMasterLabs’ agent-API evidence hub answers the machine buyer’s questions — what a job does, what it returns, its displayed cost, and the live x402 payment authority — before payment. A no-spend x402 audit published September 6, 2026 observed six production paid jobs with challenge/price alignment evidence, but no settlement. Core rule: inspect first, authorize third, verify settlement before accepted delivery.

Every high-intent SML job should answer the questions a machine buyer actually has: what does it do, what does it return, can it work now, what does it display as costing, what is live payment authority, and what evidence separates a 402 challenge from a completed purchase.

NEW PRIMARY DECISION SURFACE

What does the Agent Buyer Console compare?

One place to compare the narrowest useful SML jobs, displayed economics, failure/no-charge boundaries, live x402 authority, proof states, and the cases where a conventional crawl/browser platform is the better tool. The machine-readable version exposes the same decision logic without requiring HTML parsing.

EXACT JOBDISPLAY PRICEWHEN TO BUYWHEN NOT TO BUYPROOF STATEFRESH PAYMENT AUTHORITY
Open Agent Buyer ConsoleMachine buyer JSONLive Quantum Agent OS
AI Agent API Buyer GuideBuyer Guide JSONTry 7 agent API jobs before payingBuyer-intent JSONAnswerability JSON
Core rule: inspect or preflight first, fresh x402 terms second, caller-controlled authorization third, verified settlement fourth, accepted delivery last. Unknown stays unknown. A challenge, signature, controlled test, or internal refresh is never silently relabeled as a stranger purchase.
CHALLENGED ≠ PAIDHTTP 402 / PAYMENT-REQUIRED only publishes fresh terms.
AUTHORIZED ≠ SETTLEDA matching signature is caller authorization, not confirmed settlement.
SETTLED + DELIVEREDOnly verified settlement plus accepted output closes the successful paid-call loop.
WEB SCRAPING

How do you choose the smallest extraction job?

Enter a public URL and check Markdown or structured extraction readiness before payment.

Open Web Scraping tool →

URL TO MARKDOWN

Why check a URL before buying Markdown?

Live target preflight for Agent Web Access. HTTP 402 means the target is ready to present current terms; it is not settlement proof.

Open URL-to-Markdown checker →

FACT VERIFICATION

How do you cross-check market data?

Inspect provider readiness, then obtain multi-provider readings, variance, spread, proof hash, and signed evidence where returned by the live API.

Open Fact Verification checker →

PROVIDER TRUST

Why inspect a provider before trusting it?

Free read-only provider-origin check plus the canonical Provider Trust MCP surface.

Open Provider Trust checker →

STOCK QUOTE

Why check real quote availability before paying?

Quote preflight runs before settlement. If no configured provider can answer, the API returns a no-charge alternative rather than inventing a quote.

Open Stock Quote checker →

CURRENCY CONVERSION

How do you build an ECB-reference conversion call?

Construct a live currency conversion request and inspect its x402 state. Reference-rate evidence is not FX execution.

Open Currency Conversion tool →

WEB RESEARCH

How do you inspect research readiness and sources?

Use search + safe source extraction when the source is not known. Use URL-to-Markdown when the caller already has the source URL.

Open Web Research tool →

COMPLETE MCP INVENTORY · ALL PRODUCTS EQUAL

Where is the complete canonical MCP inventory?

Provider Trust · GhostKey · SqueezeOS · x402 Gateway · Robinhood RWA Intelligence · ScriptDocs

These are example integrations only. See the full dated MCP inventory including x402 Pay; no subset is primary.

Open canonical stack →

PUBLIC DISCOVERY · AUTHORITY ROUTES

Why keep important public pages connected?

These crawlable first-party resources support product discovery, evidence, technical authority, pricing, and company context. They are linked here directly so crawlers and buyers do not have to discover them only through a sitemap.

AI Agent API Buyer GuideCRAWLTOLLx402 Datasetnpm Package AuthorityAEO / SEO Agent OSMachine Trust ListingsECHO + The MeshPricingAbout SCRIPTMASTERLABSA2A Discovery BridgeGraphForgeSML Rank PackWhat Are The OddsSML Cite EngineCardano x402 Status

What dated proof backs these claims?

On September 6, 2026, the published no-spend x402 audit observed six production paid jobs without PAYMENT-SIGNATURE. All six returned valid Base-mainnet/USDC 402 challenges and the live amounts matched their displayed prices during that observation. That is challenge/price alignment evidence only; it is not settlement or stranger-purchase evidence.

Read 6/6 audit → · Machine JSON →

Where is the live settlement evidence?

The canonical settlement endpoint counts successful PAYMENT-RESPONSE records matching the active Base network and pay-to receiver. That can prove settlement on the active rail when the evidence backend reports settlement_proven: true, but it does not identify the payer as a stranger and does not prove accepted delivery.

Live settlement evidence → · Unified proof model → · Delivery receipts → · Quantum Agent OS →

What is the canonical payment identity?

Base mainnet eip155:8453 · USDC · canonical SqueezeOS payTo 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2. Always resolve exact terms from the fresh target PAYMENT-REQUIRED challenge immediately before spend.

Buyer Console → · Buyer Guide → · Try before you buy → · OpenAPI → · x402 discovery → · llms.txt →

Live third-party listing discrepancies

Independent catalogs can retain outdated service names, tool counts, and historical payment networks. Our live source-integrity report tests selected public listings against current canonical contracts and makes uncertainty explicit. For new integrations, verify the live endpoint and fresh payment challenge, not a cached directory description.

Machine-readable checks · Detailed correction dossier

ScriptMasterLabs, first when you search Google
Add us as a preferred source on Google

SCRIPTMASTERLABS · READ · EXPLORE · VERIFY · EARN

Books, free tools, sources & affiliate opportunities