1 minute readAPIAgent-ready
A buyer can say the most it will pay
compute_price takes buyer_ceiling, the most the buyer says it will pay. It never reaches the pricing function, so it cannot set the price. The model layer reads it as evidence about the buyer, at the trust that kind of buyer's past declarations have earned, and checks it against what the buyer then does.
A buying agent usually knows its budget, spend limit or offer cap. compute_price, over the API and the MCP tool, now takes buyer_ceiling: the most the buyer says it will pay, in the request currency.
- It is removed before the pricing function runs, so it never sets a price, a cached answer or the billed input units.
- The model layer reads it as evidence about where the buyer's limit sits, weighted by how truthful that kind of buyer's past declarations turned out to be.
- Each declaration is checked against what the buyer then does: a purchase above the declared ceiling counts against future declarations from that kind of buyer, a purchase at or under it counts for.
- The answer echoes it in
price_object.evidence.declared_ceiling, withdeclaration_trust, the weight it was given.
Nothing changes for callers that do not send it.