`set_requirements`

Define what the buyer is looking for. Each requirement is must|should and is checked at L1 (catalog field), L2 (RFP answer) or L3 (evidence question). Replaces the previous set.

L2 A buyer token (Authorization: Bearer)

Arguments

Name	Type	Required	Description
`name`	string		e.g. "AI governance tender 2026"
`market`	string		The category of what you need, from list_capabilities, e.g. "crm". Matching then looks only at vendors of that category
`requirements`	list of object	yes

Call it

curl -X POST https://rfx.market/api/set_requirements \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer <buyer_token>' \
  -d '{"requirements":[]}'

Over MCP: tools/call with name: "set_requirements" and the same arguments.