2 items
Copy a single OpenAPI endpoint — with its schemas — to the clipboard. Swagger UI renders an operation as nested HTML. There’s no useful way to copy the whole thing, so you end up pasting a 300 KB spec into your LLM just to ask about one endpoint. Most of that context is for endpoints you’ll never call. OpenAPI Copy adds a Copy button to every operation in Swagger UI. One click gives you a compact, self-contained OpenAPI document for that endpoint. It keeps the required $refs, collects referenced schemas transitively, and includes the security scheme used by the operation. The result is usually 1–3 KB instead of 100–500 KB. Copy an entire endpoint, just the request body, successful and default responses, or the full spec. Choose YAML or JSON. - Works with Swagger UI and bare openapi.json or /api-docs pages - Supports Swagger 2.0 and OpenAPI 3.x - Handles recursive schemas and preserves every allOf branch - Lets you filter and select multiple endpoints from the popup - Accepts a spec URL when one cannot be detected on the page - Marks the toolbar icon when the page you’re on has a spec behind it No account, analytics, or backend. Specs are processed locally in your browser. Open source under the MIT license: https://github.com/GusevP/openapi-copy-extension OpenAPI Copy requests no access to websites when installed. It can read the current tab only after you click its toolbar icon. If you’d rather not click, “Always on this site” grants one origin, and “On every site” grants all of them — both at runtime, both revocable, neither required.
Aug 28, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.