Documentation & DX

x-portone-title

`x-portone-title` appears on schema objects and properties and on operations. 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 `테스트 모드 여부`, `성공 응답`, `사업자등록번호`, `세금계산서 문서 번호`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX x-portone- namespace derived 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.

1124 occurrences

1 documents

1 providers

vendor-named

Where it appears

Location in the document	Occurrences
operation	368
response	51
requestBody	3
schema	702

What its value looks like

Value shape	Occurrences
string	1124

Observed values

Sampled from the specifications, most frequent first.

테스트 모드 여부성공 응답사업자등록번호세금계산서 문서 번호문서 번호 유형결제 건 아이디상점 아이디파트너 아이디

Providers publishing it

All 1.

portone

Why this is not in OpenAPI

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 documentation & dx job.