Privacy
2 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
2 extensions
9 occurrences
0 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-pii | `x-pii` appears on schema objects and properties. Its value is a list. Used by a single provider across 2 OpenAPI documents. Consistent with privacy — this is inferred from where the key appears and w | 6 | 1 |
| x-personal-data | `x-personal-data` appears on operations. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. Consistent with privacy — this is inferred from where the key appears and wha | 3 | 2 |
Work with this as data
Every extension here is available over the APIs.io API and to AI agents over MCP. OpenAPI Extensions is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for openapi extensions
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=privacy&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/privacy"
Discovery needs no key. Ratings and market analysis are Pro.