For platform leads
Add a counterparty once, not a bespoke build each time.
Each new external counterparty otherwise means another point-to-point integration to commission and maintain. Configure a counterparty once against one standard — and keep binding authority with a named person.
Why it matters
What changes when counterparties share one standard.
Configure once, transact repeatedly
From a single integration to the protocol, transact with any other adopting party — with no new connector wired for each relationship.
Binding authority stays with a person
No agreement binds until a named human clears the approval gate. Agent autonomy runs inside limits you set beforehand and can evidence afterwards.
A human-governed protocol, not a ledger
Subchain is not a blockchain, a token or a consensus network. It governs agent authority, approval-gating and the record of who agreed what.
Useful from the first pairing
It works between any two adopting parties from the first relationship, and accrues value as more of your counterparties standardise on it.
The path
How a counterparty joins, then transacts.
Integrate once to the protocol
The counterparty builds one integration to the shared standard, instead of a bespoke connection wired for your relationship alone.
Agents negotiate on shared templates
Agents from both companies exchange offers and counters against machine-readable term templates, within the authority limits you configured first.
The gate holds material terms
Any proposal above a value, risk or irreversibility threshold halts and routes to the accountable governor before it can bind.
The record captures who authorised
Every proposal, revision, approval and acceptance is written to an immutable log, producing a defensible account of what was agreed.
Why counterparty count should not drive your integration bill.
The cost that scales with every relationship
When your agents transact with counterparties outside your own organisation, each new relationship is wired by hand. A connector is designed, built and tested for one counterparty's message formats and negotiation logic, and then the next counterparty arrives and the work begins again.
The bill does not amortise. It recurs for every partner, and the maintenance load on those brittle one-off connectors rises faster than the number of counterparties you add. For a platform lead answerable for both delivery and cost, that is a line growing in the wrong direction.
One integration, not one per counterparty
Subchain replaces the N-by-N problem with a single shared standard. Agents from different companies propose, counter and accept machine-readable terms against one common vocabulary and one deterministic lifecycle. A counterparty integrates once to the protocol, and from that single integration it can transact with any other adopting party on the standard.
You stop reconstructing ad hoc formats per relationship and start configuring a counterparty rather than building for it. Where a term is unusual, it is proposed inside the same lifecycle, not through a separate bespoke channel.
Useful from the first relationship
The protocol is designed to be useful between any two adopting parties from the first relationship, and to accrue value as more of the ecosystem standardises on it. It does not require universal adoption to function. For a shared dependency at this stage, that matters: you are not waiting for a network to form before the first pairing pays off.
What we are honest about
We separate what is observed from what we are still confirming with customers. The integration pain above is well understood from real deployments. Demand for a governed-negotiation layer is something we are working to confirm with early design partners now — which is why we are looking for them.
Read us plainly: Subchain governs agent authority, approval-gating and the record of who agreed what. The name should not lead you to file it as crypto infrastructure.
What a platform lead asks before adopting.
Follow the standard as counterparties come on board.
Occasional updates on the runtime, the term-template library and the first design partners. No noise.