REST API live today; Delta Sharing + Snowflake Secure Data Share Q3 2026; S3 + Databricks Marketplace Q4 2026; Salesforce Data Cloud + SFTP available on request. Every entry below is dated and verifiable. Procurement teams: see /trust/data-provenance for the upstream license posture.
NDJSON streaming export with field allowlists and a metadata header is documented at the OpenAPI route. Dataset availability, delta coverage, and delivery cadence are source-specific; a daily count observation is not an upstream refresh.
Per-customer SFTP delivery available on request for partners whose internal compliance review prohibits API consumption. Cadence aligned with manifest snapshot frequency (see /sources/cadence). Encrypted at rest + in transit.
Sprint 2 priority — target Q3 2026. Native Delta Sharing endpoint exposes audit-pack-aligned tables with field-level provenance preserved as metadata columns. Partners can consume via Databricks, Apache Spark, pandas, or any Delta Sharing client without custom integration.
Sprint 2 priority — target Q3 2026. Same data surface as Delta Sharing, exposed natively in Snowflake's secure-share mechanism. Zero-copy share — partners read live from Fonteum's Snowflake account on subscription, no replication or staging required.
Q4 2026 target. S3-bucket-listed datasets with bucket-policy-based access control + Databricks Marketplace listing for one-click subscription by Databricks customers. Same audit-pack provenance contract; partners pay Fonteum directly, marketplace handles billing handshake.
Available on request for partners with active Salesforce Data Cloud licensing. Same data surface as Delta Sharing, exposed natively as a Data Cloud ingestable. Zero-copy — partners query live from Fonteum without replicating into Data Cloud storage.
REST, Delta Sharing, Snowflake Secure Share, S3, and Salesforce Data Cloud all expose the same Fonteum audit-pack-aligned schema. Field-level source / last-checked-date / limitations metadata travels with the data — partners never receive an unannotated row. The methodology version is pinned per delivery; the Audit Pack PDF + JSON ship alongside every customer-scoped delivery for compliance attachment.
Partner inquiries: /pilot-intake — name your preferred integration in the role field. Active engagement on Q3 2026 Delta Sharing pilots; reach out for early-access slots.
What’s on file, by the numbers
Platform snapshot · 2026-08-11
Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.
Source authority is record-specific
Use the issuer named on the record.
Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.
Reproducible by design
Inspect the evidence each published figure actually supplies.
Source and date
Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.
Available derivation
Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.
Daily observations
Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.
Named medical review
Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.