Embedded/OEM usage unit

The problem it solves

A product that embeds Arbiter state should not rebuild a bespoke integration per release. It needs one stable usage unit with versioned schemas and a predictable meter.

What a result looks like

A versioned usage unit of embedded state, schema-pinned to the canonical catalog, metered per use and reconciled against the same settlement records as every other product.

Plain price

From $0.001 per usage unit

Entitlement anchors ($49-$99 developer, $199-$499 embedded) are configuration, not list prices; larger SLA and volume accounts quote upward.

Freshness and evidence promise

Embedded state is versioned, schema-stable and cache-friendly; a release that changes the contract is a new version, never a silent mutation of the one you integrated.

Try it with x402 / the API

Machines call the canonical payable endpoints - discovery starts atFor Machines, the live contract at /openapi.json, and the catalog at /catalog. Every inbound route resolves to the canonical x402 Revenue Collection Wallet; the address is advertised by the canonical surface, never copied onto this page.

Schema and docs

The result schema, examples, errors and payment semantics are compiled from the canonical catalog: see /catalog and the operation definitions in /openapi.json.

Related products

• Protocol 360
• Stablecoin/depeg watch

Monitoring and OEM path

This is the OEM path: larger deployments move from per-use embedding to volume and SLA terms quoted from settled usage.