SCRIPTMASTERLABS
AGENT BUYER CONSOLE · DECIDE BEFORE SPEND

Know exactly what your agent is buying before it signs.

Most API pages tell a human what a product does. This console is for the machine buyer: which job fits, what it currently displays as costing, where live payment authority comes from, what failure looks like, and what evidence must exist before the call counts as paid success.

Try jobs before payingMachine buyer JSONRead 6/6 price audit
Free discovery firstUnderstand the job and inspect readiness before authorizing spend.
Fresh terms winThe target PAYMENT-REQUIRED challenge overrides cached display price.
Failure can be no-chargeWhere preflight exists, unusable upstream data or targets fail before accepted paid delivery.
Delivery closes the loop402 or signature alone never counts as a successful purchase.
BUY THE NARROWEST USEFUL OUTCOME

Decision matrix.

Displayed prices below are discovery aids from current SML public contracts/pages on September 6, 2026. They are not final spending authority. An agent must resolve the fresh target challenge immediately before payment.

JOB
DISPLAY
BUY WHEN
DO NOT BUY WHEN
URL → MarkdownOne safe public HTTPS page into compact LLM-ready Markdown.Open job →
$0.001USDC / accepted read
You already know the source URL.Best small primitive for a known page.
You need browser interaction or whole-site crawl.Use a browser/crawl platform for that class of work.
Structured Web ExtractionOne public page into structured machine output.Open job →
$0.005USDC / accepted extraction
You know the URL but need structured fields.Use instead of research when discovery is unnecessary.
You need to discover which sources matter.Use Web Research first.
Web ResearchSearch the live web and extract source evidence.Open job →
$0.003USDC / accepted one-shot
You do not know the source URL yet.Search plus evidence extraction in one job.
You already have the exact URL.URL → Markdown is smaller and cheaper.
Quick Stock QuoteOne current provider-backed US equity quote.Open job →
$0.001USDC / accepted quote
Speed and low cost matter most.Good for watchlists and lightweight routing.
You need independent-feed agreement.Use Fact Verification.
Fact VerificationMulti-provider readings, spread, variance, proof hash and signed evidence where returned.Open job →
$0.005USDC / accepted verification
You need stronger market-data evidence.Expose provider disagreement instead of hiding it.
One fast quote is enough.Quick Quote is the smaller job.
Currency ConversionECB-reference conversion for machine workflows.Open job →
$0.001USDC / accepted one-shot
You need a deterministic reference-rate conversion.Useful for budgets, normalization and reporting.
You need executable FX or a tradable quote.This is reference-rate data, not execution.
Provider TrustRead-only origin and provider evidence before dependency or spend.Open checker →
FREEorigin-level preflight
You need to inspect an unfamiliar provider.Use before adding a service to an automated chain.
You want an irreversible trust decision.The caller keeps policy authority.
PROOF-STATE MODEL

A payment has states. Do not collapse them.

SML deliberately separates requirement, authorization, settlement and delivery. That makes it harder for agents, dashboards, crawlers, or humans to accidentally count a challenge as revenue.

1
DISCOVEREDThe job and machine contract can be found. No payment event exists.
2
PREFLIGHTEDInputs/upstream readiness pass where the route supports preflight. Still no payment.
3
CHALLENGEDHTTP 402 / PAYMENT-REQUIRED publishes fresh terms. Not payment proof.
4
AUTHORIZEDThe caller signs matching terms under its own policy. Authorization is not settlement.
5
SETTLEDPayment settlement is verified. Delivery must still succeed.
6
DELIVEREDThe requested accepted output exists. Only settled + accepted delivery is paid success.
SML purchase law: CHALLENGED ≠ PAID. AUTHORIZED ≠ PAID. SETTLED + ACCEPTED DELIVERY = successful paid call. Buyer origin is a separate fact; controlled validation traffic must not be relabeled as a stranger purchase.
FIT BOUNDARY

Use the right class of tool.

A trustworthy buyer guide should tell an agent when to walk away. SML is not trying to pretend a tiny pay-per-call primitive is the same product as a full web-data platform.

Choose SML when…

  • You want a narrow outcome rather than a subscription.
  • The caller should inspect price and terms before every spend.
  • You do not want to provision another SML API key or billing account for the cold-start purchase.
  • Sub-cent or small one-shot machine purchases fit the workflow.
  • You care about explicit no-charge alternatives and accepted-delivery semantics.
  • You want MCP/x402 discovery with caller-controlled wallet policy.

Choose a conventional platform when…

  • You need whole-site crawling or massive indexing.
  • You need heavy JavaScript interaction or browser automation.
  • You need an enterprise SLA, dedicated high-throughput plan, or large reserved capacity.
  • You need one vendor to provide broad search/crawl/browser infrastructure as a single large platform.
  • Your workload is continuous bulk collection rather than small outcome-priced calls.
LIVE AUTHORITY DECK

Marketing is not payment authority.

Machine buyer contract

https://scriptmasterlabs.com/.well-known/agent-buyer-console.json

Decision matrix, proof-state semantics, fit boundaries and evidence references in one machine-readable surface.

Payment discovery

https://squeezeos-api.onrender.com/.well-known/x402

Discover current x402 resources, then fetch the selected target immediately before spend.

OpenAPI

https://squeezeos-api.onrender.com/.well-known/openapi.json

Inspect current inputs and route contracts rather than inferring tool shape from marketing prose.

Buyer intent map

https://scriptmasterlabs.com/.well-known/buyer-intent.json

Maps common buyer questions to the exact canonical job, contract and execution surface.

Dated no-spend x402 price audit — 2026-09-06Six production paid jobs returned valid Base/USDC 402 challenges and matched their displayed amounts during the recorded audit. This proves challenge/price alignment for that observation; it does not claim settlement or a stranger purchase.
6 / 6 AUDIT →
Machine audit projectionUse the JSON evidence when a crawler or agent needs the same dated fact set without parsing HTML.
JSON →
Answerability mapCanonical machine answers for high-intent buyer questions, without inventing rankings or demand.
OPEN →
BUYER QUESTIONS

Fast answers for humans and agents.

How should an agent decide what to buy?

Choose the narrowest job that directly produces the needed outcome. Use free discovery/readiness first, resolve fresh payment terms next, then let the caller's own wallet policy decide whether to authorize.

Is the displayed price final?

No. It is useful for discovery. The target resource's fresh PAYMENT-REQUIRED challenge is final authority for exact amount, asset, network and receiver immediately before spend.

Does a 402 prove somebody paid?

No. A 402 is a requirement. A signature is authorization. Only verified settlement plus accepted delivery is a successful paid call.

Why expose when SML is not a fit?

Because the buyer should optimize for task fit, not vendor lock-in. SML is intentionally strongest at narrow, inspectable, outcome-priced agent jobs. Whole-site crawl, browser automation and massive indexing are a different product class.

Browse exact jobsBuyer evidenceMCP stack