Openverse
Openverse is a search engine providing programmatic access to the world's largest openly-licensed media catalog, covering 800M+ images and audio tracks from cultural institutions, museums, and creative commons sources including Flickr, Wikimedia Commons, iNaturalist, Europeana, Freesound, Jamendo, and more. Built by WordPress/Automattic under Creative Commons licensing principles.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Openverse the way a machine reads it — 88 machine-readable artifacts across 3 APIs, 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 — Openverse scores 42.0/100 (thin), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Openverse
Each block below is one kind of artifact we hold for Openverse. 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 3
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.
Openverse audio API
These are endpoints pertaining to audio files.
Openverse auth API
Openverse provides free and open access to the Openverse API to anonymous and registered users. [Refer to the API documentation site for information on how to register](https://...
Openverse images API
These are endpoints pertaining to images.
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 six things the Kin Score reads for commercial clarity.
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.
context Context
JSON-LDOpenverse 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.
Openverse API Rules
SPECTRALJSON Schema 26
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.
APIException
JSON SCHEMAAudio
JSON SCHEMAAudioAltFile
JSON SCHEMAAudioReportRequest
JSON SCHEMAAudioSet
JSON SCHEMAAudioWaveform
JSON SCHEMAAuthenticationFailed
JSON SCHEMAGrantTypeEnum
JSON SCHEMAImage
JSON SCHEMAImageReportRequest
JSON SCHEMANotAuthenticated
JSON SCHEMANotFound
JSON SCHEMAOAuth2Application
JSON SCHEMAOAuth2KeyInfo
JSON SCHEMAOAuth2Registration
JSON SCHEMAOAuth2Token
JSON SCHEMAOAuth2TokenRequest
JSON SCHEMAOembed
JSON SCHEMAPaginatedAudioList
JSON SCHEMAPaginatedImageList
JSON SCHEMAReasonEnum
JSON SCHEMASource
JSON SCHEMATag
JSON SCHEMATypeEnum
JSON SCHEMAValidationError
JSON SCHEMAVersionEnum
JSON SCHEMAScroll within the panel for all 26 ·
Examples 50
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.
Audio_Detail_200
EXAMPLEAudio_Detail_401
EXAMPLEAudio_Detail_404
EXAMPLEAudio_Related_200
EXAMPLEAudio_Related_401
EXAMPLEAudio_Related_404
EXAMPLEAudio_Report_201
EXAMPLEAudio_Report_400
EXAMPLEAudio_Report_401
EXAMPLEAudio_Report_404
EXAMPLEAudio_Search_200
EXAMPLEAudio_Search_400
EXAMPLEAudio_Search_401
EXAMPLEAudio_Stats_401
EXAMPLEAudio_Thumb_401_Stub
EXAMPLEAudio_Thumb_404_Stub
EXAMPLEAudio_Waveform_200
EXAMPLEAudio_Waveform_401
EXAMPLEAudio_Waveform_404
EXAMPLEImages_Detail_200
EXAMPLEImages_Detail_401
EXAMPLEImages_Detail_404
EXAMPLEImages_Oembed_200
EXAMPLEImages_Oembed_400
EXAMPLEImages_Oembed_401
EXAMPLEImages_Oembed_404
EXAMPLEImages_Related_200
EXAMPLEImages_Related_401
EXAMPLEImages_Related_404
EXAMPLEImages_Report_201
EXAMPLEImages_Report_400
EXAMPLEImages_Report_401
EXAMPLEImages_Report_404
EXAMPLEImages_Search_200
EXAMPLEImages_Search_400
EXAMPLEImages_Search_401
EXAMPLEImages_Stats_401
EXAMPLEImages_Thumb_401_Stub
EXAMPLEImages_Thumb_404_Stub
EXAMPLEKey_Info_200
EXAMPLEKey_Info_401
EXAMPLEKey_Info_429_Stub
EXAMPLEKey_Info_500
EXAMPLERegister_201
EXAMPLERegister_400
EXAMPLERegister_401_Stub
EXAMPLERegister_429_Stub
EXAMPLEToken_200
EXAMPLEToken_400_Stub
EXAMPLEToken_401
EXAMPLEScroll within the panel for all 50 ·
Security 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 Openverse — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/openverse · machine-readable index on apis.io