Soda
Soda is a data quality and data observability platform for the modern data stack. Its core abstraction is the data contract — a declarative YAML source of truth that defines the checks a dataset must pass — extended by organization-wide data standards, ML-based metric monitors for anomaly detection, record-level diagnostics, lineage and impact analysis, and AI-assisted contract generation (Contract Autopilot and Copilot). Soda ships an open-source engine (Soda Core), a Go CLI for the whole platform (sodacli), a 103-operation Soda Cloud v4 REST API, a webhook event surface, and a first-party MCP server that exposes 78 tools so agents can manage data quality directly. Soda Data Inc. is headquartered in Belgium.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Soda the way a machine reads it — 32 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Soda scores 71.6/100 (exemplar), with a separate agent-readiness read of 36/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Soda's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/soda-data/"
title="Soda on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/soda-data.svg"
alt="Soda Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/soda-data/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/soda-data/"
title="Soda on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/soda-data/card.svg"
alt="Soda Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Soda
Each block below is one kind of artifact we hold for Soda. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Soda Cloud API v4
The Soda Cloud public REST API (v4). 103 operations across 15 resources — datasources, datasets, discovered datasets, data contracts, checks, data standards, monitors, scans, in...
Soda Attributes API
The Attributes surface of the Soda Cloud v4 API — 4 operation(s) across 2 path(s).
Soda Checks API
The Checks surface of the Soda Cloud v4 API — 2 operation(s) across 2 path(s).
Soda Contracts API
The Contracts surface of the Soda Cloud v4 API — 10 operation(s) across 8 path(s).
Soda Data Standards API
The Data Standards surface of the Soda Cloud v4 API — 13 operation(s) across 10 path(s).
Soda Datasets API
The Datasets surface of the Soda Cloud v4 API — 24 operation(s) across 17 path(s).
Soda Datasources API
The Datasources surface of the Soda Cloud v4 API — 18 operation(s) across 11 path(s).
Soda Discovered Datasets API
The Discovered Datasets surface of the Soda Cloud v4 API — 1 operation(s) across 1 path(s).
Soda Incidents API
The Incidents surface of the Soda Cloud v4 API — 5 operation(s) across 3 path(s).
Soda Licensing API
The Licensing surface of the Soda Cloud v4 API — 1 operation(s) across 1 path(s).
Soda Notification Rules API
The Notification Rules surface of the Soda Cloud v4 API — 4 operation(s) across 2 path(s).
Soda Runners API
The Runners surface of the Soda Cloud v4 API — 4 operation(s) across 2 path(s).
Soda Scans API
The Scans surface of the Soda Cloud v4 API — 3 operation(s) across 2 path(s).
Soda Secrets API
The Secrets surface of the Soda Cloud v4 API — 5 operation(s) across 3 path(s).
Soda Users API
The Users surface of the Soda Cloud v4 API — 8 operation(s) across 4 path(s).
Soda Utility API
The Utility surface of the Soda Cloud v4 API — 1 operation(s) across 1 path(s).
Scroll within the panel for all 16 ·
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONSoda Cloud REST Attributes API
OPEN COLLECTIONSoda Cloud REST Attributes Authentication API
OPEN COLLECTIONSoda Cloud REST Attributes Checks API
OPEN COLLECTIONSoda Cloud REST Attributes Contracts API
OPEN COLLECTIONSoda Cloud REST Attributes Datasets API
OPEN COLLECTIONSoda Cloud REST API
OPEN COLLECTIONScroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Soda MCP Server
soda-mcp is Soda's first-party Model Context Protocol server for Soda Cloud. It runs as a LOCAL stdio process started by the MCP client (Claude Code, Cursor, Codex, GitHub Copil...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Soda Data Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Soda Data Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Soda Data Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Soda — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/soda-data · machine-readable index on apis.io
This is an independent, third-party profile of Soda, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.