vendor_resolve
HUMAN ONLY, vendor. Decide a break-out: approve, deny, or counter with a value. For a requirement question pass answer (and status met|partial|unmet). Your agent then continues.
Vendor A vendor key (x-vendor-key) needs a person: name and confirm: true
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
breakout_id | string | yes | From vendor_inbox |
decision | "approve" | "deny" | "counter" | yes | |
value | any | For counter: the value you offer | |
answer | string | For a requirement question | |
status | "met" | "partial" | "unmet" | ||
note | string | Optional reason | |
name | string | yes | The person deciding |
title | string | Their title | |
confirm | boolean | yes | true only after the person has explicitly approved |
email | string | For an NDA with real e-signature: the signer's email, where the NDA is sent to sign |
Call it
curl -X POST https://rfx.market/api/vendor_resolve \
-H 'content-type: application/json' \
-H 'x-vendor-key: <vendor_key>' \
-d '{"breakout_id":"…","decision":"approve","name":"…","confirm":true}'Over MCP: tools/call with name: "vendor_resolve" and the same arguments.