Metered access: a product with no tiers to cross
Metered access bills by usage rather than by tier. There is no grid, no plan and no point at which behaviour changes, so the crossing-point column has nothing to record. As of 2026-09-22.
| The term | Metered access |
|---|---|
| What it names | Billing by usage rather than by subscription tier |
| What it is not | A free tier, or a refusal to publish prices |
| Where the register uses it | One entry's empty commercial columns |
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.
1An empty cell with no omission in it
Most empty cells in the crossing-point column follow from reading a grid and not finding a line. On a metered product there is no grid: access is billed per unit of output, there are no columns and no tier at which anything changes. The blank records the absence of the structure the question assumes.
That is a different finding from a vendor declining to publish a boundary, and the readings say which. A reader who wants to know what it costs to get clean output from such a product is asking a question the product's commercial shape does not have an answer to.
2Why marking on such products tends to be invisible
A visible mark is a reminder that somebody has not paid, which is a concept a metered product does not have: every unit of output is paid for. So the commercial motive for a visible mark disappears, and what remains is a provenance motive, which produces invisible signals and credential manifests instead.
Both entries in this register with no crossing point and a filled file-contents cell are reached this way or documented in the same genre. The pattern is consistent enough to be worth stating and is a pattern rather than a rule.
3What the register records instead
What output carries by default, which is the question underneath the free-tier column's name, and whatever the documents say about the file. On one such entry that is an invisible watermark on all output plus a credential standard on a later model version.
So the row is short in two columns and unusually informative in a third. Reading the register by which columns a row fills separates products like this from subscription products more sharply than reading it product by product.
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: two-route product, download route, burned-in mark.