GateTrue

What each generator documents about marking its output

API surface: where marking becomes an input

An API surface is a documented programmatic route into a model. Where a marking answer exists there, it takes the form of a field with a published default or a sentence among the things a caller cannot change. As of 2026-09-22.

Where a marking statement sits inside a referenceAmong the request parameters, with a name, a type and a default, the mark is an input the caller decides. Under a heading collecting properties a caller works around, it is a fact about the output. The same genre of document produces opposite values in the control column.Where does the reference put its marking statementAmong the requestparametersAn inputA boolean with a publisheddefault, so the callerdecides what outputcarries.Among the limitationsA propertyThe output carries themark whatever the callersends; no parameter isoffered.Nowhere at allA strong silenceAbsent from the documentwhose purpose is to listwhat a caller sends andreceives.The genre does not decide the answer; the placement does
Fig. 1 A provenance field missing from a reference is missing from the place it would be defined, which is a stronger silence than on a price list.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termAPI surface
What it namesA documented programmatic interface into a model
What it is notA plan, or the vendor's own web interface
Where the register uses itTwo entries' control and file-contents values

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1Two grammars, in the same genre of document

One reference here lists a boolean watermark field among the request parameters, with a default and a description of the stamp it produces. Another names its mark under a heading collecting properties a caller works around, with no parameter at all. Both are developer documentation.

So the genre does not determine the answer; the placement within it does. A field among the inputs means the caller decides. A sentence among the limitations means the output carries the mark whatever the caller sends.

2Why an absence here weighs more

A reference exists to enumerate what a caller sends and what comes back. A provenance field missing from that list is missing from the place it would be defined, which is a stronger silence than the same absence on a pricing page where it never belonged.

One entry demonstrates both halves of that: its reference specifies the text and corner of a visible stamp and names no metadata field anywhere. One document, two opposite levels of detail, and the contrast is the finding.

3What it changes about who holds the decision

On a plan-gated entry the person who can change the mark is the person who pays. On an interface the person is whoever maintains the integration, which in most organisations is neither the same person nor the same department.

A marking policy enforced through a plan is enforced by procurement and changes slowly. One enforced through a request field is enforced by whoever last edited the call, which is easier to change and harder to notice.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: request parameter, documented default, limitations section.