`x-portone-description` appears on operations and on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-portone-` namespace, so its meaning is defined by portone tooling rather than by OpenAPI. Observed values include `테스트 모드 여부를 결정합니다. true 이면 테스트 모드로 실행됩니다. Request Body에도 isForTest가 있을 수 있으나, 둘 다`, `날짜를 나타내는 문자열로, `yyyy-MM-dd` 형식을 따릅니다.`, `true 이면 테스트 모드로 실행되며, false 이거나 주어지지 않은 경우 테스트 모드를 사용하지 않습니다.`, `query 파라미터로 전달된 문서번호 유형. 기본 값은 TAX_INVOICE_ID이며 SUPPLIER, RECIPIENT, TAX_INVOICE`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.
Data & schema semanticsx-portone- namespacederived description
How this description was produced. It is assembled from what was
measured in the corpus — where this key appears in a document, what shape its value
takes, the values observed, and how many providers use it. It is not taken
from a published definition, because for most extensions none exists. Read it as
evidence, not as a specification. If you own this extension and want it described
properly, tell us.
456 occurrences
1 documents
1 providers
vendor-named
Where it appears
Location in the document
Occurrences
operation
272
response
69
schema
115
What its value looks like
Value shape
Occurrences
string
456
Observed values
Sampled from the specifications, most frequent first.
테스트 모드 여부를 결정합니다. true 이면 테스트 모드로 실행됩니다. Request Body에도 isForTest가 있을 수 있으나, 둘 다날짜를 나타내는 문자열로, `yyyy-MM-dd` 형식을 따릅니다.true 이면 테스트 모드로 실행되며, false 이거나 주어지지 않은 경우 테스트 모드를 사용하지 않습니다.query 파라미터로 전달된 문서번호 유형. 기본 값은 TAX_INVOICE_ID이며 SUPPLIER, RECIPIENT, TAX_INVOICE성공 응답으로 세금계산서를 반환합니다.접근 권한이 있는 상점 아이디만 입력 가능하며, 미입력시 인증 정보의 상점 아이디를 사용합니다.성공 응답으로 예약된 계약 객체를 반환합니다.성공 응답으로 예약된 추가 수수료 정책을 반환합니다.
Extensions exist because a provider needed something the specification would not
carry. Most of what they hold is not the API contract at all — it is operational
metadata about the contract: documentation, lifecycle, policy, provenance,
and now agents. That metadata is usually better placed alongside the contract, in an
Overlay or an
APIs.json index, than crammed inside it.
See everything else doing the
data & schema semantics job.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.