Farther ShoreDocs
Go to Farther Shore
Getting startedCore conceptsLaunch checklist
ProductsUpstream routingEnvironmentsDeveloper portals
Billing strategiesPlans and limitsSubscribersAPI keys
Gateway enforcementUsage meteringLimits and creditsGateway sharding
Launch a request-counted product15mAdd monthly included usageAdd subscription plus overageCreate a prepaid credits productMeter AI token usageAdd a custom meterIssue and test an API keyDebug a denied requestUpdate product docsPrepare for launch
TroubleshootingGateway response codesMeter namingPlatform docs publishing
Status
Docs/Operate/Meter naming

Meter naming

Name usage meters consistently so billing stays understandable.

PreviousGateway response codesNextPlatform docs publishing

On this page

Naming rulesUnit clarityProduct docs languageChanging meter names

Meter names appear in plans, usage, billing, support workflows, and sometimes product docs. Choose names that will still make sense months later.

Naming rules

Use:

  • lowercase
  • snake case
  • plural nouns for countable units
  • product-specific names only when needed

Good examples:

requests
input_tokens
output_tokens
images
document_pages
records_enriched

Avoid:

RequestCount
tokens-in
usage1
things
billing_units

Unit clarity

Every meter should answer:

  • What increments it?
  • When is it counted?
  • Is it estimated or actual?
  • Does it reset by billing period?
  • Does it map to money, credits, or a hard limit?

Product docs language

Explain custom meters in subscriber terms:

A document_page is one processed page in an uploaded document. A 12-page PDF
counts as 12 document_pages.

Changing meter names

Avoid renaming live meters unless necessary. Meter names connect configuration, usage events, billing, and subscriber expectations.

If you must rename a meter:

  1. Test in stage.
  2. Update plans.
  3. Update product docs.
  4. Confirm usage events use the new name.
  5. Confirm billing calculations remain correct.