Open Commerce Graph

Why an Open Commerce Graph

1. 1. Why directories are not enough

   Traditional directories were built for people skimming pages. They list names, addresses, and hours, but they do not expose a machine-readable structure that AI agents, marketplaces, or commerce rails can act on. Directory listings drift, get scraped out of context, and rarely carry the proof or payment endpoints a system needs to route a transaction. The Open Commerce Graph is not a prettier directory — it is the structured, owner-controlled layer underneath.

2. 2. Why payment rails need business context

   A payment rail can settle dollars in seconds. It cannot, on its own, tell a buyer that the merchant on the other end is real, currently operating, accepting the right asset, or authorized to fulfill the order. Stablecoin checkouts, agent-driven payments, and on-chain commerce all need to read business context before they hand over money. Routing money without business context routes money to noise.

3. 3. Why AI systems need current business identity

   AI assistants and agents answer questions about real businesses every day — hours, services, locations, payment options, who to contact. They are only as accurate as the business identity they can read. Stale scraped data leads to wrong answers and lost transactions. The Open Commerce Graph gives AI systems a current, owner-maintained source of truth so the answers they generate reflect what the business actually does today.

4. 4. Why owner control matters

   If a business does not control its own record, third-party aggregators, scrapers, and platforms control it instead. Updates are slow, corrections are political, and the business cannot decide how it is represented. Owner control is the prerequisite for trust: the entity accountable for the business must be the entity who maintains the record. The graph is open for reading, but writes belong to the owner.

5. 5. What a node contains

   A node in the Open Commerce Graph represents one business. It carries the business's identity (legal name, jurisdictions, owner attestations), structured understanding (services, categories, audiences), proof (credentials, verifications, attestations), activity (current operating state), locations, payment endpoints (where supported), reputation signals, and the commerce actions the business is prepared to fulfill. Each field is structured so that a reader — human or machine — can act on it without guessing.

6. 6. How Known Businesses become graph-ready

   A Known Business is a business whose record is structured, current, proven, and consistent enough that commerce systems can route to it with confidence. Becoming graph-ready means publishing an owned identity object, supplying the structured understanding fields, attaching the proof a reader needs, and keeping the record current. The Known Business Check on this site is the diagnostic that scores readiness across Identity, Understanding, Proof, and Consistency.

7. 7. How IdentityRecord supports the first owned record layer

   IdentityRecord is the product where business owners build and maintain the owned record itself. RWC Guide defines the category and runs the diagnostic; IdentityRecord is where owners create the record, accept proof, publish their AI Page, and keep the data current. Future protocol-backed portability of these records is on the roadmap and will only be described as live once it is. Today, the owned-record layer ships through IdentityRecord.