metrUsage infrastructure
Live product · Access approved individually

TRUST MODEL / SECURITY

REAL VALUE NEEDSCLEAR BOUNDARIES.

See how authorization, funded balances, session states, receipts, and fail-closed behavior shape the Metr security model.

Read integration docs Request access
CONTROL BOUNDARYLIVE SYSTEM MAP
CONTROLPOLICYSTATE / ACTIVE
01IDENTITYauthenticate
02BALANCEverify funds
03LIMITenforce cap
04RECEIPTrecord close
VERIFIABLE INPUTEXPLICIT LIMITREADABLE OUTPUT
01 / DEFAULTFail closed
02 / FUNDSPrepaid
03 / LIMITExplicit
04 / TRAILAuditable

SECURITY MODEL / 01

No balance, no session.

The safest metered transaction starts with explicit authorization and ends with an explainable receipt. The service should not silently continue when the required state is unavailable.

CAPABILITY MAP04 SYSTEM PRIMITIVES
01IDENTITY
KEY

Server-side credentials

Keep business credentials outside public clients and rotate them when needed.

02FUNDS
BAL

Funded authorization

Check the available balance and spending ceiling before granting paid access.

03STATE
FSM

Explicit session states

Start, pause, resume, and close through constrained lifecycle transitions.

04AUDIT
LOG

Traceable settlement

Retain the identifiers and usage facts needed to investigate an unexpected charge.

WORKFLOW / 02

THE SYSTEM
IN MOTION.

Each stage has a visible input, an explicit state, and a result the next stage can verify.

  1. 01
    Authenticate

    Identify the integration and bind each request to an authorized business.

    credential = required
  2. 02
    Authorize

    Verify the customer balance, rate, and maximum before access begins.

    limit = enforced
  3. 03
    Observe

    Track usage updates and session state while the service is active.

    state = monitored
  4. 04
    Fail safely

    Stop accrual when the product cannot confirm the state needed to continue.

    default = closed

VISIBLE EVIDENCE / 03

MAKE THE STATE
READABLE.

Product activity should leave a trace a developer, operator, or customer can understand. The showcase uses realistic sample data where a live feed is not connected.

SOURCEDLABELEDREPRODUCIBLE
SESSION POLICY CHECK
010203040506api_key: validcustomer_balance: sufficientspending_cap: 25.00 USDCsession_state: activeusage_event: currentpolicy_result: allow
SYSTEM TRACEshowcase / deterministic

KEEP EXPLORING / 04

FOLLOW THE
SYSTEM.

01
FROM API KEY TO LIVE METER.

The full integration model for authentication, products, funded balances, session lifecycle events, route groups, billing logic, MCP tools, and final session records.

02
SHOW WHAT IS LIVE. SHOW WHAT IS NOT.

The status surface is designed to report API health, request latency, errors, and connectivity without replacing missing data with a fake zero.

03
TURN ACCESS INTO A MEASURABLE PRODUCT.

Set a rate, choose a billing unit, and collect from funded balances without forcing every customer into a monthly plan.

LIVE PRODUCT

BUILD WHAT
GETS METERED.

Metr is live. Access is currently approved individually for businesses, developers, and agent builders.

Request access