Metering & settlement

Shared services record what each community uses. The metering service collects those records, aggregates them per community, and produces statements an operator can reconcile line by line. It also records creator payouts, which settle through the community's own wallet.

Only shared-service usage is metered. Chat, wallet and DApps run entirely inside the operator's deployment and produce no usage records.

Metered unitsCopy Anchor Link

These are the units defined in the SDK's module catalog. A deployment plan lists the units each shared service will record for that manifest.

symorva plan

Shared services
  Real-time media                  used by Meetings & live rooms · metered in participant-minutes, broadcast-viewer-minutes
  AI inference & generation        used by AI & creator studio · metered in ai-tokens, images, video-seconds
  Resource metering & settlement   used by Creator economy · metered in settled-payouts

This output is for the creator template, which enables the creator economy.

Usage recordsCopy Anchor Link

Every shared service emits usage records to the metering service.

Records contain no content and no member identities. Where an operator needs per-member attribution — for example to apply member quotas in the AI studio — that attribution is kept in the operator's own deployment.

QuotasCopy Anchor Link

Quotas are enforced per community at the shared service that serves the request. A community that reaches a quota receives a quota error for further requests of that kind; other communities are unaffected. Operators can subdivide their community's AI quota per member in the studio service. The reference deployment's AI control plane works the same way: no account receives quota by default, and requests without an active quota policy are refused before any model call.

Statements and reconciliationCopy Anchor Link

• Statements aggregate usage records by community, module, unit and period.
• Every statement line can be traced back to the records that make it up, through GET /usage on the Server API.
• Records are idempotent by recordId, so retries between services cannot inflate a statement.
• Commercial terms — prices, included volumes, billing periods — are set in each operator's agreement and are not part of these docs.

Settlement of creator payoutsCopy Anchor Link

The creator economy settles payouts through the community's wallet service, not through Symorva:

1. The rewards service in the operator's deployment computes what each creator is owed under the community's published rules.
2. It instructs the community's wallet service to pay out. The wallet service applies its own confirmation, idempotency and ledger rules.
3. When a payout settles, the metering service records one settled-payouts unit.

Symorva records that a payout settled; the value moves only inside the community's own wallet. The creator economy module is planned; see Creator economy.

Paid features inside a communityCopy Anchor Link

Operators can charge members for paid features — for example AI generation or meeting packages — through their own wallet. The reference deployment handles such charges with a server-side quote, an admission step that reserves the job and debits the member in a single database transaction, and settlement when the result arrives; replaying a command never charges twice. These charges are between the operator and its members and are separate from metered shared-service usage.