Provider · Federation
Handshakes across orgs.
Each request terminates a service against a peer account, with a single-use consent token and an A/Z billing split fixed at the handshake. Cross-org, consent-gated, and dual-billed: the federation differentiator, surfaced as a first-class object.
Cross-org
Terminates against a peer account, not a subnet inside your own tenant. The A-side and Z-side each keep their own books.
Consent-gated
A single-use token authorizes exactly one activation. It resolves on approval and cannot be replayed.
Dual-billed
The A/Z revenue split is recorded at the handshake, not reconciled later. Each side invoices against its declared share.
Inbound, pending 0 peers waiting on us
Outbound, pending 0 awaiting peer consent
Active 0 handshakes carrying traffic
Total volume 0 all directions, all states
Inbound
peer requested to connect to us| ID | A-side (peer) | Route | Service profile | Consent token | Billing split | Requested | Status |
|---|
Outbound
we requested to connect to a peer| ID | Z-side (peer) | Route | Service profile | Consent token | Billing split | Requested | Status |
|---|