Documentation & DX

x-portone-category

`x-portone-category` appears 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 `b2b.taxInvoice`, `payment`, `platform.policy`, `platform.partner`. 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.
126 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 126

What its value looks like

Value shapeOccurrences
string126

Observed values

Sampled from the specifications, most frequent first.

b2b.taxInvoicepaymentplatform.policyplatform.partnerb2b.counterpartyplatform.transferpayment.billingKeyidentityVerification

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.