The next action deserves better evidence.
An evolving library of first-party data with provenance, version history, and developer access. Built toward a future where software—and the agents operating it—must know what the evidence actually supports.
When source evidence is missing, absence of events does not prove that everything is healthy.
See where it came from.
Inspect source ownership, licensing status, observed fields, and available first-party records before building against a feed.
Browse the library ↗Go back to a version.
Versioned snapshots and content hashes make published observations reproducible. A hash alone is not an independent attestation.
Open developer access ↗Know what you don't know.
Our research is focused on the gap between a successful API response and a proven business outcome. Verification beyond today's feeds is still under development.
Explore the approach ↗A green HTTP check. A stalled data pipeline.
In a November 2026 internal audit, a monitored site returned HTTP 200 while its background data ingestion had not completed for more than 76 hours. A reachability check alone missed the distinction.
Inspect the supply.
Real metadata, real previews, and published versions. Restricted and proposed datasets are labeled honestly. No checkout is active.
DATA RIGHTS MATTER. Public feeds are first-party and downloadable. Restricted feeds require explicit approval. Under-review feeds are not offered for commercial distribution. How evidence is handled ↗
What does “success” prove?
Not everything that returns HTTP 200 has completed its job. Explore an illustrative version of the failure we documented internally.
GET /health 200 OK Last HTTP check recent Business effect not established Data producer not verifiedHTTP 200 / OBSERVED
The endpoint responds.
A successful network response proves the endpoint is reachable. It does not prove that a background job ran or that its output was committed.
Identity & rights
Know who owns an observation and whether redistribution is actually permitted.
Immutable versions
Compare published snapshots and source timestamps. Versioning alone is not truth.
Freshness context
Separate data age from endpoint availability and detect missing source coverage.
Approval boundaries
High-impact automated actions require real permissions, not persuasive text.
The trust layer is a hypothesis, not a finished guarantee.
We're validating whether independent business-effect verification adds value over existing monitoring and simple downstream readbacks. The current public product is a working first-party dataset library.
Built to be used.
Public API endpoints and real first-party records, without a login. Try the catalog or retrieve a stored snapshot in a few lines.
Small surface.
Explicit contracts.
Read the catalog, inspect a preview, or retrieve a version. Protected datasets require authorized tenant keys. Paid checkout and self-serve account creation are not yet enabled.
GET /v1/catalogPUBLICGET /v1/feedsPUBLICGET /v1/feeds/:id/versions/latestPUBLIC*POST /mcpPROTOCOL
* Public data only. The same endpoint enforces restrictions for protected feeds. OpenAPI specification ↗
Open live API ↗curl -sS \
https://core.datasupply.shop/v1/catalog
# Read an immutable public snapshot
curl -sS \
https://core.datasupply.shop/v1/feeds/qira-site-status/versions/latestSee the system.
These are real service responses, not simulated telemetry. An API being reachable doesn't establish that every downstream workflow is healthy.
Connecting to core.datasupply.shop
Counting rights-cleared feeds
Checking first-party signed receipt
What we're willing to claim.
| Public REST data | Available |
| Versioned feeds | Available |
| First-party signed transfer | Demonstrated |
| Public checkout | Disabled |
| Self-service accounts | Not enabled |
| External webhook delivery | Restricted |
What a green light can't tell you.
A responding endpoint is not a guarantee of fresh information. An earlier internal audit documented an upstream Sitemapper pipeline outage while the website itself continued to return HTTP 200. This page reports what each check actually measures; it does not certify the whole system.
Our roadmap prioritizes independently verified downstream outcomes, source rights, and real buyer validation over cosmetic uptime metrics.
Examine the method ↗Privacy & scope.
This page describes the limited public preview experience, not a full commercial service agreement.
Browsing this preview
The current public site loads dataset metadata and samples from DataSupply's Cloudflare-hosted API. It doesn't include customer registration or payment forms, and it doesn't intentionally set advertising cookies. Cloudflare and infrastructure providers may process ordinary request information, including IP addresses and technical logs, to provide security and hosting.
Access and data
Only explicitly public first-party feeds are downloadable here. Restricted datasets and third-party feeds under rights review are not offered. Public samples can include published first-party URLs and monitoring records.
Contact
Contacting the team uses your own email application; this site does not silently submit or store a contact form. For questions, email the existing business contact.
Site notice updated November 2026. Before customer onboarding, a full privacy policy and service terms will be required.