A lead-time claim matters
A fictional supplier page says:
Lead time: 7 daysYour sourcing workflow uses that statement when recommending a supplier.
For sourcing workflows that need a source record · v0.7.0
Keep a record of the page behind your supplier recommendation.
When a decision depends on a public supplier page, DELTA can capture that page and return a timestamp, content hashes and a proof reference to keep beside the recommendation.
Public pages only. The public proof contains metadata and hashes; original text and screenshots are private and are not available to reviewers through this link.
A recommendation should have a source record beside it.
This is an illustrative workflow. No live capture or payment has been made for this supplier example.
Record the public source
Submit the public page URL to Capture. Store the returned proof reference with your own decision ID and rationale.
No invented timestamp, hash, receipt or verdict is shown here.
Identify the observation you used
If the fictional page later says 14 days, the saved reference identifies the earlier DELTA observation and its hashes.
The public verifier cannot show the original “7 days” text. Keep any authorized source material your reviewer needs separately.
What can the reviewer actually inspect?
The proof URL exposes source metadata, application-recorded capture times, artifact hashes and a manifest-integrity status. Capture times are not independently anchored. It does not expose captured HTML, Markdown or screenshots, independently attest when the decision happened, or verify that a supplier statement is true.
If your customer needs the original captured page, the current DELTA public proof is not a complete review package.
Inspect an existing proof before paying
The available historical example captured example.com, not a supplier. Its integrity status is legacy_unverifiable and its attestation is not_anchored. It demonstrates the public metadata format; it is not customer adoption or current-format verification evidence.
Choose the smallest check that answers your question
Capture
1 USDC
One public page observation. Receive a timestamp, content hashes and proof references.
Review a Capture requestPreflight
5 USDC
One fresh observation compared with prior hashes or literal text rules you supply.
Review a Preflight requestGuarded-Action Pilot
10 USDC
1–3 public HTTPS pages and one optional deterministic check. It does not perform an order or other downstream action.
See the Pilot requestPer request, paid in USDC on Base mainnet. No subscription. Opening a link does not make a payment. Review the current quote and authorize payment in your own wallet.
Before you use DELTA
Do I need Capture or Preflight?
Use Capture to record an observation. Use Preflight only when you have explicit expected text, expected hashes or a prior DELTA proof to compare. A matching condition is not an approval to purchase.
Will it read my logged-in supplier portal?
No. DELTA captures public pages in its own browser. It does not inherit your login, cookies, shopping cart or negotiated terms.
What does “verified” mean?
For current-format proofs, it means the manifest bundle-root hash is internally consistent. It is not an independent timestamp, supplier endorsement, signature, or guarantee of legal admissibility.
Can my agent call it?
Use the HTTP JSON API with an x402-capable client. Read the API guide for the no-payment first step, response handling and retry limitations.