Fact Verification API for market data
SCRIPTMASTERLABS Fact Verification cross-checks a market-data claim or ticker reading against configured provider evidence — the route independently attempts Tradier, Alpaca, and Polygon, per the page's provider-scope section. The displayed verification price is $0.005 USDC per the page's pricing section, on Base mainnet (eip155:8453) via x402 v2; accepted delivery returns provider readings, spread, variance, a proof hash, and signed evidence.
SCRIPTMASTERLABS Fact Verification cross-checks a market-data claim or ticker reading against current configured provider evidence. Missing evidence stays missing; provider failure is not replaced with synthetic consensus. A 402 challenge is not proof of payment or verified evidence delivery.
Cross-check a ticker against available independent market-data providers instead of treating one reading as unquestionable truth. SML Truth Verify is built for agents that need evidence density, disagreement visibility and a machine-verifiable proof package before a downstream decision.
How do I quickstart and verify readiness without paying?
Start with the two free curl commands: the verify route and the free provider-status route — provider status costs nothing before payment.
curl -i 'https://squeezeos-api.onrender.com/api/truth/verify/AAPL'
# free provider status
curl 'https://squeezeos-api.onrender.com/api/truth/providers'A ready verification returns HTTP 402 with fresh payment terms. If adequate real evidence is unavailable, the contract is designed to stop before settlement instead of inventing a result.
What evidence is returned on accepted delivery?
Where available, the product exposes the component provider readings, source count, consensus price, spread, variance, a transparent confidence heuristic, proof hash and signed evidence. Downstream software can preserve the underlying readings rather than storing only an opaque score.
Which providers does Truth Verify use?
The verification route independently attempts Tradier, Alpaca, and Polygon when each is configured and available. Provider-status may expose other market-data services used elsewhere in SqueezeOS, but they are not automatically part of this verification consensus. A failed provider is skipped rather than replaced with synthetic data.
What is the exact response shape after accepted delivery?
The numeric values below are placeholders. The field names and meanings mirror the live implementation so developers can wire parsers without pretending a historical market value is current.
What are the HTTP and payment states?
The five states: 400 for an invalid symbol, 503 when the service is unavailable, 503 when no live data exists, 402 when payment is required, and 200 after valid payment delivers the evidence package.
| State | Meaning | Payment boundary |
|---|---|---|
400ERR_INVALID_SYMBOL | The ticker is not alphanumeric. | charged:false; the paid guard is not reached. |
503ERR_SERVICE_UNAVAILABLE | The market-data service is not initialized. | charged:false; the paid guard is not reached. |
503ERR_NO_LIVE_DATA | No configured verification provider returned a usable live reading. | charged:false; no fabricated price is returned. |
| 402 | At least one real provider reading passed preflight and the endpoint is presenting fresh x402 terms. | Payment required; a 402 is not settlement proof. |
| 200 after valid payment | The requested evidence package is delivered. | Settlement evidence plus accepted delivery are required before calling it a completed paid verification. |
What is the truth boundary of this API?
This is market-data evidence verification for ticker symbols. It does not claim to fact-check every statement on the internet, predict price direction or guarantee that every upstream provider is correct. The design goal is to make corroboration and disagreement observable.
When should I use Truth Verify?
Use Truth Verify when a downstream action deserves multiple readings and evidence. Use Quick Quote when one current provider-backed reading is enough. Use Provider Trust when the question is whether the provider itself should be relied on before connection or spend.
What is the pricing and x402 contract?
The displayed verification price is $0.005 USDC. Current canonical payment network is Base mainnet eip155:8453, Base USDC, x402 v2, canonical SqueezeOS payTo 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2. The fresh target challenge controls exact payment terms immediately before spend.
What are the machine endpoints?
Four machine endpoints: verify, provider state, OpenAPI, and x402 discovery.
Verify: https://squeezeos-api.onrender.com/api/truth/verify/{symbol}
Provider state: https://squeezeos-api.onrender.com/api/truth/providers
OpenAPI: https://squeezeos-api.onrender.com/.well-known/openapi.json
x402: https://squeezeos-api.onrender.com/.well-known/x402What questions do people ask about the Fact Verification API?
Common questions: why not use one stock API, what HTTP 402 proves, and whether confidence is a forecast probability.
Why not use one stock API? One feed is sufficient for many low-stakes reads. This route exists when the caller wants corroboration and an explicit view of feed disagreement.
Does HTTP 402 prove evidence exists forever? No. It describes the current request state. Provider readiness is live and can change.
Is confidence a forecast probability? No. It is a transparent agreement heuristic tied to observed provider spread, not a prediction of future price.
Stock Quote API → · Provider Trust → · Buyer evidence →
What did a live probe measure on 2026-10-15?
On 2026-10-15, ScriptMasterLabs' fact-verification route reported 5 of its 6 configured market-data providers live — Alpaca, FRED, Massive, Polygon and Tradier answering; Alpha Vantage not configured — and quoted $0.005 for a cross-check, all before any payment.
GET /api/truth/providers→ HTTP 200, free:{"alpaca": true, "alphavantage": false, "fred": true, "massive": true, "polygon": true, "tradier": true}.GET /api/truth/verify/AAPL→ HTTP 402 in 0.95 s; the accepts array quotes 5,000 atomic USDC = $0.005 on Base mainnet (eip155:8453).
Method: unauthenticated GET probes from an external client on 2026-10-15. An HTTP 402 response is the live x402 payment challenge — the price quoted is read from its accepts array; no payment was made and nothing was charged for these probes. Response times are single measurements, not averages.
How is this different from a general fact-checking service?
The results that currently own the query "fact verification API for AI agents" are Webcite and probator.ai (ScriptMasterLabs authority watch, 2026-10-15) — general claim- and citation-checking services. SML Truth Verify is deliberately narrower: it verifies market-data claims. Send a ticker and the route cross-checks the reading across independent market-data providers, returning the provider readings, spread, variance and a proof hash — disagreement is shown, never averaged away, and a provider failure is reported as missing evidence rather than replaced with synthetic consensus.
Claim receipts
Every factual claim on this page, atomized for machines: what is asserted, where the evidence lives, when it was verified.
| CLAIM | EVIDENCE | VERIFIED |
|---|---|---|
| FACT VERIFICATION API · MULTI-PROVIDER MARKET EVIDENCE · X402 | Evidence | 2026-09-27 |
| SCRIPTMASTERLABS Fact Verification cross-checks a market-data claim or ticker reading against current configured provider evidence. Missing evidence stays missing; provider failure is not replaced with synthetic consensu | Evidence | 2026-09-27 |
| Live probe 2026-10-15: /api/truth/providers answered HTTP 200 free showing Alpaca, FRED, Massive, Polygon and Tradier live (Alpha Vantage not configured); /api/truth/verify/AAPL answered HTTP 402 in 0.95 s quoting $0.005 (5,000 atomic USDC, Base mainnet). | Evidence | 2026-10-15 |