How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
The OpenAPI Overlay Standard cover

API Evangelist Paper · Standard Report

The OpenAPI Overlay Standard

122 stars, 21 contributors, two people writing four fifths of it — and Elastic, MongoDB, Cloudinary and Vercel running it in production. Attention and adoption have come apart.

Free Version 1.0 · August 2026
picture_as_pdf Formatted PDF, ~28 pages
description Editable Microsoft Word (.docx)
update Free updates to this report, for life
lock_open_right No signup, no checkout, no email required
How this report was made. This report is generated using artificial intelligence, from open-source data, scored on the public Kin Score rubric, and every company in it is named and banded rather than cherry-picked. If anything in it is wrong, tell me and it is corrected in the next version — and if it was not worth what you paid, I will refund it. Read how the reports are produced →

About this report

The OpenAPI Overlay Specification applies a repeatable list of changes to an OpenAPI document without editing that document. Strip internal endpoints. Inject examples. Fix a generated spec before codegen. The original stays canonical and the transformation becomes an artifact you can version and re-run.

It has 122 stars, against Arazzo’s 460 and OpenAPI’s 31,123 — and it is the most genuinely used of the three. Of the documents a public-index probe can enumerate, 63.4% sit at paths indicating real use, against 36% for Arazzo. An Arazzo document describes something for a reader; an Overlay document does something in a pipeline, and an artifact with a job in CI gets maintained because the build breaks when it is wrong.

Elastic, MongoDB, Cloudinary, Seqera and Vercel run it in production — nearly all doing the same job: a machine produced a specification, it is not good enough for the audience it must serve, and an overlay repairs it on the way out.

The largest single distributor is a code generator. Speakeasy emits a codeSamples.yaml overlay during SDK generation, into customer repositories that never chose Overlay — the same mechanism that distributes Arazzo. And the specification itself is two people: 21 contributors ever, the top two holding 81.2%.

What's inside

  1. Executive summary — attention and adoption have come apart
  2. What an Overlay is, and what it is not
  3. How adoption was measured, and where the method was capped
  4. What the documents are actually for
  5. Who is actually using it
  6. The generator is the distribution channel
  7. Why it is used, and what that says
  8. The body
  9. Conformance, tooling, and the one deliberate holdout
  10. The scoring caveat
  11. What would have to be true
  12. The investable thesis
  13. Where this is going

What you get

picture_as_pdf A print-ready, formatted PDF edition
description The editable Word (.docx) source
checklist The anti-patterns & self-assessment checklist
update Every future revision of this living report
Free PDF + Word, instant download

These reports are experience-based and vendor-neutral, distilled from the API Evangelist research at apievangelist.com. Every API Evangelist Standard Report is free to download. Found something wrong, or an artifact this report missed? [email protected] — pointing at an artifact is the fastest way to change the next version.

arrow_back All reports