opbox

Charges (company registers)

All 2 verbs in the `charge.*` family - what each does, who can call it, and its inputs.

The charge.* family (2 verbs). Every verb enters through the one front door: it is capability-checked, permission-checked, scope-checked and audited before it runs (see Security & permissions). Each entry below lists its capability, risk class (which fixes the minimum autonomy level), the minimum caller permission, its availability tier, whether it is idempotent, and any outbound egress.

Listcharge.list

PropertyValue
Capabilityparty.read
Risk classRead - autonomy L0
Min. permissionMember
AvailabilityCore - always on (MCP tier 1)
IdempotentNo
EgressNone - in-box (pure Postgres, no outbound call)
Render schemaYes - drives an inline chat artefact and a GUI panel

([2026] CC-OPBOX 28). The company charges register: the rows charge.register writes. Slim standing, optional { companyPartyId?, status? }, paginated, RLS-scoped. No PII.

Call POST /v/charge.list with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool charge.list.

Registercharge.register

PropertyValue
Capabilityparty.write
Risk classWrite - autonomy L1
Min. permissionMember
AvailabilityCore - always on (MCP tier 1)
IdempotentNo
EgressNone - in-box (pure Postgres, no outbound call)

([2026] CC-OPBOX 28 gate-(c) writer over the new charge store). Register a company charge (a security interest over the company’s assets). { companyPartyId, chargeeName, chargeType?, amount?, currency?, assetDescription? }. The named writer in the schema-consolidation ledger.

Call POST /v/charge.register with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool charge.register.