Connect data you can hold someone to.
Every distribution channel uses one schema, uniform across providers. This page is about how easy it is to plug in; the full technical reference lives in the API documentation.
Every distribution channel uses one schema, uniform across providers. This page is about how easy it is to plug in; the full technical reference lives in the API documentation.
Token auth, pagination, and filtering. The version is explicit in the URL — never swapped silently.
CSV, Parquet, and GeoJSON/GeoPackage for spatial data — via presigned URLs.
Webhook, object storage, SFTP, or online spreadsheet, with a delta option: changed rows only.
A DataDiti endpoint in front of third-party APIs: normalised responses, TTL-based caching, per-tier quotas.
An API wrapper around script products: synchronous or asynchronous (job + completion webhook), with per-call resource limits.
A thin layer over an API that is already clean — positioning DataDiti as a source of facts for AI agents.
Visualisations published as a public or tokenised URL, without releasing the underlying rows.
Connect the data you subscribe to into an AI agent or assistant through your account’s MCP endpoint. Agent credentials are issued separately from ordinary API tokens, scoped per dataset or endpoint. What an agent can reach still follows your subscription, quota, transfer eligibility, and access class — exactly like every other channel.
A customer’s integration breaks the moment a column is renamed without warning — the most preventable way to kill an API business.
Every data product uses a semantic version. Versions are never swapped silently.
Breaking changes are announced at least 90 days ahead through the changelog, notifications, and email.
Old versions are served for at least 180 days after the new one ships, then retired with staged reminders.