Part II: The six domainsChapter summary

An agent that can read about a restaurant but cannot book it will book the restaurant next door. This is the hardest commercial truth in the field, and the reason for the principle “be callable, not just readable”. The value of a relationship with an agent lies in what it can do with you.

Transact means defining actions: reserve, buy, apply, request a quote, join, cancel. Each action needs clear inputs, clear limits and a clear result. Schema.org’s potentialAction can declare them on a page; an MCP server or an API can expose them as tools; commerce protocols such as ACP and UCP standardize how an agent completes a purchase while the merchant remains the seller of record.

  1. Read

    Facts and offers

    schema.org, feeds

  2. Ask

    Questions answered

    MCP, an agent endpoint

  3. Act

    Book, apply, quote

    potentialAction, tools

  4. Buy

    Pay and confirm

    ACP, UCP, payment rails

Figure 7. From reading to acting. Each step lets agents do more, and the value of the relationship rises with it.

Payment is the delicate part. The principal must authorize what the agent spends, the merchant must know the payment is good, and both must be able to undo a mistake. The rails are being built now by card networks, payment processors and platforms, and they do not yet agree. The chapter compares them in plain terms and suggests where an organization should start: usually with one valuable action, on one widely supported protocol, done well.

Transactions also expose an organization’s operations. A booking an agent makes at 3am must be honored at 9am. Inventory, staff and policies must keep up with promises made by software. Transact is where Agent Relations stops being a marketing project.

Read the whole chapter

This is a summary. The full chapter is in the book, which is coming soon. One email when it is published.