data.world
Collaborative data catalog platform with REST APIs for accessing public and private datasets, running SQL and SPARQL queries, managing metadata, and integrating data across projects and organizations. Provides enterprise data governance, lineage, and business glossary capabilities.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles data.world the way a machine reads it — 80 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 — data.world scores 54.3/100 (strong), with a separate agent-readiness read of 32/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 data.world'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/data-world/"
title="data.world on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/data-world.svg"
alt="data.world Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/data-world/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/data-world/"
title="data.world on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/data-world/card.svg"
alt="data.world 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 data.world
Each block below is one kind of artifact we hold for data.world. 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 37
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.
data.world Datasets API
Create, retrieve, update, delete, and download datasets. Manage dataset metadata, links, contributors, and access permissions.
data.world Projects API
Create, retrieve, update, and delete projects. Link datasets to projects, manage contributors and access controls.
data.world SQL Query API
Execute SQL queries against datasets and projects, describe columns, manage saved queries, and retrieve results in multiple formats.
data.world SPARQL Query API
Execute SPARQL queries via GET or POST against datasets. Supports multiple output formats for semantic data querying.
data.world Metadata Management API
Create, search, update, and delete catalog resources by IRI. Manage tables, columns, relationships, collections, business glossaries, and data quality badges.
data.world Webhooks API
Subscribe to dataset, project, and account events to automatically respond to activity on data.world.
data.world Answer API
Ask natural language questions against structured data and receive answers. Enables AI-powered data exploration within the catalog.
data.world catalog relationships API
Manage relationships between catalog resources
data.world catalog resources API
The catalog resources API from data.world — 7 operation(s) for catalog resources.
data.world connections API
The connections API from data.world — 3 operation(s) for connections.
data.world data quality API
Manage data quality of metadata resources
data.world datasets API
The datasets API from data.world — 5 operation(s) for datasets.
data.world DOIs API
The DOIs API from data.world — 2 operation(s) for dois.
data.world experimental API
This API is in active development. Its definition may change frequently and without notice.
data.world files API
The files API from data.world — 7 operation(s) for files.
data.world insights API
The insights API from data.world — 3 operation(s) for insights.
data.world instance admin API
The instance admin API from data.world — 3 operation(s) for instance admin.
data.world legacy catalog - analysis API
The legacy catalog - analysis API from data.world — 3 operation(s) for legacy catalog - analysis.
data.world legacy catalog - collections API
The legacy catalog - collections API from data.world — 2 operation(s) for legacy catalog - collections.
data.world legacy catalog - data API
The legacy catalog - data API from data.world — 8 operation(s) for legacy catalog - data.
data.world legacy catalog - glossary API
The legacy catalog - glossary API from data.world — 3 operation(s) for legacy catalog - glossary.
data.world legacy catalog - properties API
The legacy catalog - properties API from data.world — 1 operation(s) for legacy catalog - properties.
data.world legacy catalog - relationships API
The legacy catalog - relationships API from data.world — 4 operation(s) for legacy catalog - relationships.
data.world organizations API
The organizations API from data.world — 2 operation(s) for organizations.
data.world projects API
The projects API from data.world — 4 operation(s) for projects.
data.world queries API
The queries API from data.world — 14 operation(s) for queries.
data.world requests - authorization API
Manage authorization requests
data.world requests - resource API
Manage resource requests
data.world search API
The search API from data.world — 2 operation(s) for search.
data.world serviceaccount API
The serviceaccount API from data.world — 3 operation(s) for serviceaccount.
data.world streams API
The streams API from data.world — 3 operation(s) for streams.
data.world tables API
The tables API from data.world — 1 operation(s) for tables.
data.world telemetry API
The telemetry API from data.world — 1 operation(s) for telemetry.
data.world topics and comments - resource API
The topics and comments - resource API from data.world — 7 operation(s) for topics and comments - resource.
data.world user API
The user API from data.world — 8 operation(s) for user.
data.world users API
The users API from data.world — 1 operation(s) for users.
data.world webhooks API
The webhooks API from data.world — 4 operation(s) for webhooks.
Scroll within the panel for all 37 ·
Open Collections 31
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 COLLECTIONdata.world Public catalog relationships API
OPEN COLLECTIONdata.world Public catalog relationships connections API
OPEN COLLECTIONdata.world Public catalog relationships data quality API
OPEN COLLECTIONdata.world Public catalog relationships datasets API
OPEN COLLECTIONdata.world Public catalog relationships DOIs API
OPEN COLLECTIONdata.world Public catalog relationships experimental API
OPEN COLLECTIONdata.world Public catalog relationships files API
OPEN COLLECTIONdata.world Public catalog relationships insights API
OPEN COLLECTIONdata.world Public catalog relationships instance admin API
OPEN COLLECTIONdata.world Public catalog relationships organizations API
OPEN COLLECTIONdata.world Public catalog relationships projects API
OPEN COLLECTIONdata.world Public catalog relationships queries API
OPEN COLLECTIONdata.world Public catalog relationships search API
OPEN COLLECTIONdata.world Public catalog relationships serviceaccount API
OPEN COLLECTIONdata.world Public catalog relationships streams API
OPEN COLLECTIONdata.world Public catalog relationships tables API
OPEN COLLECTIONdata.world Public catalog relationships telemetry API
OPEN COLLECTIONdata.world Public catalog relationships user API
OPEN COLLECTIONdata.world Public catalog relationships users API
OPEN COLLECTIONdata.world Public catalog relationships webhooks API
OPEN COLLECTIONScroll within the panel for all 31 ·
Pricing 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.
Plans
PLANSRate 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.
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.
Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Api Context
JSON-LDcontext Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
data.world API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
data.world API Schemas
JSON SCHEMAExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Api Examples
EXAMPLESecurity 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 data.world — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/data-world · machine-readable index on apis.io
This is an independent, third-party profile of data.world, 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.