Skip to content
cresvaDevelopers
Changelog

Protocol changelog. Every version. Every breaking change.

A complete history of Open Storefront Protocol versions. Each release includes what changed, why it changed, and how to migrate.

v3.0

CurrentAugust 2026

Escrow, Financing & Insurance Removed

OSP v3.0 removes the escrow, financing, and insurance concepts introduced in v2.0. Cresva never holds, receives, routes, finances, insures, or pays out funds; it facilitates discovery, negotiation, and order handoff, and payment happens directly between the buyer and the merchant on the merchant's own rails. v2.0's escrow endpoints and states described the platform as a fund custodian, which conflated a release-timing status with an actual holding of money the platform never had a license to hold. This release corrects that: the transaction lifecycle no longer has an ESCROWED state, and disputes are recorded, not adjudicated or settled by Cresva.

Changes

  • Added POST /transactions/{id}/confirmation-window/confirm and POST /transactions/{id}/confirmation-window/dispute to manage a transaction's optional confirmation window without implying Cresva holds or freezes funds(Spec Section 6)
  • Added an explicit statement to the Transactions section: Cresva never holds funds; payment happens between buyer and merchant on the merchant's rails(Spec Section 6)
  • Removed escrow, financing, and insurance from the spec, the SDKs, and this site(Spec Section 6)

v2.0

March 2026

Negotiation, Transactions & Trust

OSP v2.0 is a major release that extends the protocol from read-only product queries to full-lifecycle commerce. Agents can now negotiate prices, execute transactions, and assess brand trustworthiness through a structured trust score system. It is the first published specification: the public repository was created in March 2026 and this was its first spec commit. (This entry originally described a v2.0 escrow feature as holding funds; as of v3.0, that description is corrected. See the v3.0 entry above.)

Changes

  • Added negotiation protocol with typed offers, counter-offers, and state machine(Spec Section 5.1)
  • Added transaction protocol with full lifecycle management(Spec Section 6.1)
  • Added a release-timing status for conditional purchases (removed in v3.0; see above)(Spec Section 6.4)
  • Added trust score system with 7 components and tier classification(Spec Section 9.1)
  • Added webhook event types for real-time notifications. The union is 36 today(Spec Section 10.1)
  • Response envelopes settled per endpoint and are not uniform: POST /query answers with results, while GET /products and GET /search answer with products. A client reading one key across all three finds nothing on two of them(Spec Section 4.2)
  • Added HMAC signature verification for webhook security(Spec Section 10.3)
  • Added agent-exclusive offers and bundle endpoints(Spec Section 5.5)
  • Added price hold mechanism for time-limited pricing(Spec Section 5.3)
  • Added feedback endpoint for agent quality signals(Spec Section 9.4)
  • Added degradation headers for partial/stale data indication(Spec Section 7.5)
  • Enhanced product card format with comparison highlights and brand voice summary(Spec Section 4.3)
  • Enhanced query protocol with review and availability intents(Spec Section 4.1)
  • Improved error responses with detailed field-level validation(Spec Section 8.1)
  • Added dispute recording: a claim and its evidence are stored. Cresva does not adjudicate them(Spec Section 6.6)
  • Added protocol capability negotiation in discovery manifest(Spec Section 2.2)