Commerce infrastructure
for the agentic era.

Merchants define pricing, options and constraints. Zolofy resolves buyer requests into offers their business can stand behind.

Vibe Shopping with a resolved offer: the merchant's own imagery, the buyer's configuration, an itemised total and the action to continue.

Merchants define the rules. Zolofy resolves the offer.

A fixed SKU already has its price. A room for three nights does not: it depends on dates, occupancy, minimum stay and add-ons. The agent structures the request. The merchant’s logic determines the answer.

  1. Agent requestDates, occupancy, options, quantity, urgency.
  2. Merchant contractPricing logic, constraints, eligibility, approval rules.
  3. Resolved offerPriced, versioned and bound to the contract it came from.

Three surfaces.

Merchant Lab with a merchant's pricing and rules open for editing.

Merchant Lab

Define offerings, variables, pricing logic, constraints and approval rules. Publishing is blocked until every commercially influential value is merchant-confirmed.

Vibe Shopping mid-conversation, with the buyer's request taking shape beside the merchant's commerce canvas.

Vibe Shopping

A buyer-facing conversational surface, deployed per merchant. It renders only from that merchant’s published contract and business profile.

A Commerce Trace timeline listing the events a Session appended, in order, with the authority each came from.

Commerce Session

Holds the state from request to outcome. Merchant approval, buyer authorization, mandate lifecycle and execution are separate states. Commerce Trace records how a request became an approved transaction.

Architecture.

  1. 01Merchant Commerce Contractcontract_id · version · contract_hash
  2. 02Deterministic Resolutionresolve(inputs, contract) → line_items
  3. 03Quote / E-SKUquote_id · total · expires_at
  4. 04Commerce Sessionstate: resolving | open | needs_input
  5. 05Merchant Approvalquote_approved
  6. 06Buyer Authorizationquote_accepted
  7. 07Signed Mandatebody_digest · merchant_authorization
  8. 08Lifecycleactive | consumed | expired | revoked
  9. 09ExecutionExecutionAttempt · adapter_id
  10. 10Commerce TraceCommerceEvent[] · append-only

Zolofy does not move money. It resolves and governs the commercial state that approved systems act on.


This is the spine the reference implementation runs today. Support for specific agent protocols is not claimed beyond what the repository actually contains.

Build your commerce.

Open source. Read the reference implementation or run it yourself.

  • Technical preview.
  • Synthetic demo data.
  • Mock execution.
  • No real payments.