Skip to main content
Messages from the server (API-Version 2026-11-20)
The server words every message about a Request, and each channel prints it.
  • REST writes return message (what to tell the buyer) and agent_line (what your agent does next). Over MCP the same text is a second text block of the tool result.
  • A Request read or written over REST has next_step, the single next step, beside next_actions. It also has attention: the sentence for each needs_attention flag and for a Request about to end. After a write it has buyer_status too.
  • next_actions is ordered by what is missing: model, confirmation, delivery, quantity.
  • Your agent sees two answers to the still_want check, yes and pause. To close a Request, use the close operation.
  • The wording of message, hint, next_step and next_actions changed. Codes and field names did not.
Permissions an agent can see
  • The default consent level lets your agent record whether an Offer fits (respond_to_offer), under a new permission, offer_fit. An agent connected before this change needs to connect again to get it.
  • list_requests and GET /api/purchases return can: the tools this connection may call. answer_question:still_want is its own entry.
  • A refusal for a missing permission names it in error.details.permission.
Buyer redesign
The buyer MCP server lists 9 tools: list_requests, get_request, get_offers, save_request, update_request, close_request, answer_question, respond_to_offer and set_notifications.
  • A Request has items, each with a quantity and the options (models) the buyer would accept.
  • list_requests flags what needs attention: new_offer, open_question, details_needed, still_want and offer_ending.
  • close_request closes a Request and emails the buyer a link to reopen it within 7 days.
  • answer_question answers seller questions and the still_want check.
  • Requests saved before this change were removed. Your agent needs to connect again.