Cohere does not create KPPs. Cohere does not build the experiences that use them. Cohere does one thing, in four parts: it makes KPPs trustworthy enough to use, and pays the people behind them when they're used.
01
Certification
The signed agreement is the spine.
Cohere holds the agreement that says the KPP is real, approved, and authorized for a specific scope. Provenance, ownership, and revocation terms travel with every KPP. Not "this is the person." Just — this is approved by the person.
02
Custody
The neutral vault.
The authoritative version of the KPP and its full version history live with Cohere — not inside whatever vendor built it. Version, scope, consent, owner identity, audit trail. Neutral governance is the infrastructure advantage.
03
Controlled Delivery
Tokens, not files.
A downstream app never receives a KPP file. It receives a time-limited, scope-limited, non-transferable token to use a KPP for a defined session. The token expires. The authorization does not remain indefinitely.
04
Settlement
The owner gets paid every time.
When a KPP is used, Cohere processes the fee, takes a small infrastructure margin, and routes the rest to the owner. Pennies per delivery, across millions of deliveries. Every line is on the ledger.