Public Dataset Endpoint Refresh Pack
Specification as of 2026-09-07: you send 3 inputs, you get back 3 sections.
Three exact-endpoint refresh receipts with prior/new UTC timestamps, HTTP status, byte count, SHA-256, transfer-cap comparison, payload shape, and CHANGED, UNCHANGED, or UNKNOWN.
$747
one-time
Request this →Checkout for this service opens by emailed invoice link. Tell us where to send it and we reply the same working day.
What you get
- Three receipts for pre-approved stable public federal HTTPS endpoints
- Prior and new UTC fetch timestamps, HTTP status, byte counts, and SHA-256
- Comparable byte-cap and payload-shape observations
- CHANGED, UNCHANGED, or UNKNOWN with the method boundary
- No new-release search, source-row redistribution, code execution, or monitoring
- Each accepted receipt within two business days; credits expire after 90 days
Free specimen and paid-delivery boundary
A completed miniature refresh receipt. It shows the latest adjacent Federal Register pair whose changed digests each identify exactly one retained source row, plus an independently recounted stability finding across the three named clock archives.
Specimen provenance: Captured: 2026-09-07 · Target: one adjacent before/after pair for the exact retained Federal Register newest-documents endpoint · Evidence method: read-only replay of two sealed successful receipts with independent row, response-body, and collection-batch hash checks
Proof scope: method boundary only. This free specimen does not demonstrate the full paid delivery.
What this free specimen actually shows
- One exact adjacent before/after receipt pair for the same URL
- Recomputed byte, content, row, and collection-batch seals
- A CHANGED byte/digest verdict and retained-window stability inventory
Paid outputs not demonstrated by this specimen
- The other two receipts in the paid three-receipt pack
- UNCHANGED receipt branch
- UNKNOWN receipt branch
Paid delivery contract
You send:
- One pre-approved stable public HTTPS endpoint
- Two adjacent retained successful receipts for that exact URL
- The three retained raw-fetch clocks used for the stability population
You get back:
- Prior and new UTC retrieval times, status, byte count, and SHA-256
- A CHANGED verdict with byte and payload-shape comparisons
- The number of comparable exact URLs whose digest stayed stable in-window
Limits: This specimen contains one of the three receipts in the paid pack. CHANGED means only that exact retained response bytes differed; it does not identify a new release, explain why upstream content changed, or redistribute source rows. It does not demonstrate the UNCHANGED or UNKNOWN receipt branches. The stability count covers only successful retained observations and never predicts future behavior.
Open the FDA, Federal Register, and agent-census SQLite stores read-only; recompute every raw-fetch row seal; group exact URLs having at least two successful receipts by distinct body digest; then choose the latest adjacent changed Federal Register pair whose two digests each occur in exactly one source row. For that pair, decompress both retained bodies, recompute byte counts and SHA-256 values, compare JSON shape, and verify each originating collection batch. This is bounded evidence of the dated method stated here; it does not establish affiliation, endorsement, authorization, or any current outcome beyond that scope.
View the full machine-readable specimen and evidence rows
US Tech Automations is a data and automation company. These are our own service terms, not a government fee, filing cost, or permit charge. Nothing on this page is legal, engineering, or financial advice.