Zenodo
Zenodo is a free, open research data repository operated by CERN and co-developed under the European OpenAIRE program. It enables researchers to deposit, share, and preserve any research output — including datasets, software, papers, preprints, presentations, and multimedia — regardless of format, size, or discipline. Every upload receives a Digital Object Identifier (DOI) for persistent citation and discoverability. Zenodo provides a REST API for programmatic deposit management, record search and retrieval, and file management, as well as an OAI-PMH endpoint for metadata harvesting. The platform is built on InvenioRDM and stores all data at the CERN Data Centre with replicas and nightly tape backups.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Zenodo the way a machine reads it — 60 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 — Zenodo scores 50.6/100 (developing), with a separate agent-readiness read of 24/100 (agent aware). 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 Zenodo'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/zenodo/"
title="Zenodo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zenodo.svg"
alt="Zenodo Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zenodo/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zenodo/"
title="Zenodo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zenodo/card.svg"
alt="Zenodo 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 Zenodo
Each block below is one kind of artifact we hold for Zenodo. 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 25
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.
Zenodo OAI-PMH API
Open Archives Initiative Protocol for Metadata Harvesting endpoint that allows bulk harvesting of Zenodo metadata in formats including oai_dc, marcxml, and oai_datacite4. Suppor...
Zenodo Access API
Access control and sharing
Zenodo Audit Logs API
Audit log entries and search
Zenodo Avatars API
User and group avatars
Zenodo Comments API
Request comments and discussions
Zenodo Communities API
Community management endpoints
Zenodo Communities Invitations API
Community invitation management
Zenodo Communities logo API
Community logo management
Zenodo Communities Members API
Community membership management
Zenodo Drafts API
Draft record management
Zenodo Drafts Files upload API
Draft file upload workflow
Zenodo Export API
Record export functionality
Zenodo Featured Communities API
Featured communities management
Zenodo Groups API
Group management endpoints
Zenodo OAI-PMH API
OAI-PMH protocol endpoints
Zenodo OAI-PMH Sets API
OAI-PMH set management
Zenodo Records API
Record and draft management endpoints
Zenodo Records Files API
File management operations on published records
Zenodo Records Versions API
Record version management
Zenodo Request Actions API
Request actions and lifecycle management
Zenodo Requests API
Request management endpoints
Zenodo Statistics API
Statistics and analytics endpoints
Zenodo Timeline API
Request timeline and history
Zenodo Users API
User management endpoints
Zenodo Vocabularies API
Vocabulary and controlled terms endpoints
Scroll within the panel for all 25 ·
Open Collections 25
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 COLLECTIONZenodo REST Access API
OPEN COLLECTIONZenodo REST Access Audit Logs API
OPEN COLLECTIONZenodo REST Access Avatars API
OPEN COLLECTIONZenodo REST Access Comments API
OPEN COLLECTIONZenodo REST Access Communities API
OPEN COLLECTIONZenodo REST Access Communities Invitations API
OPEN COLLECTIONZenodo REST Access Communities logo API
OPEN COLLECTIONZenodo REST Access Communities Members API
OPEN COLLECTIONZenodo REST Access Drafts API
OPEN COLLECTIONZenodo REST Access Drafts Files upload API
OPEN COLLECTIONZenodo REST Access Export API
OPEN COLLECTIONZenodo REST Access Featured Communities API
OPEN COLLECTIONZenodo REST Access Groups API
OPEN COLLECTIONZenodo REST Access OAI-PMH API
OPEN COLLECTIONZenodo REST Access OAI-PMH Sets API
OPEN COLLECTIONZenodo REST Access Records API
OPEN COLLECTIONZenodo REST Access Records Files API
OPEN COLLECTIONZenodo REST Access Records Versions API
OPEN COLLECTIONZenodo REST Access Request Actions API
OPEN COLLECTIONZenodo REST Access Requests API
OPEN COLLECTIONZenodo REST Access Statistics API
OPEN COLLECTIONZenodo REST Access Timeline API
OPEN COLLECTIONZenodo REST Access Users API
OPEN COLLECTIONZenodo REST Access Vocabularies API
OPEN COLLECTIONScroll within the panel for all 25 ·
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.
Zenodo Plans Pricing
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.
Zenodo 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.
Zenodo Finops
FINOPSSemantic Vocabularies 1
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.
Zenodo 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.
Zenodo 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.
Zenodo Record
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.
Zenodo Create Record Example
EXAMPLESecurity Posture 2
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 Zenodo — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
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/zenodo · machine-readable index on apis.io
This is an independent, third-party profile of Zenodo, 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.