The server words every message about a Request, and each channel prints it.
- REST writes return
message(what to tell the buyer) andagent_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, besidenext_actions. It also hasattention: the sentence for eachneeds_attentionflag and for a Request about to end. After a write it hasbuyer_statustoo. next_actionsis ordered by what is missing: model, confirmation, delivery, quantity.- Your agent sees two answers to the
still_wantcheck, yes and pause. To close a Request, use the close operation. - The wording of
message,hint,next_stepandnext_actionschanged. Codes and field names did not.
- 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_requestsandGET /api/purchasesreturncan: the tools this connection may call.answer_question:still_wantis its own entry.- A refusal for a missing permission names it in
error.details.permission.
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_requestsflags what needs attention:new_offer,open_question,details_needed,still_wantandoffer_ending.close_requestcloses a Request and emails the buyer a link to reopen it within 7 days.answer_questionanswers seller questions and thestill_wantcheck.- Requests saved before this change were removed. Your agent needs to connect again.