Buy requests

A buy request is the buyer demand object. The API name remains Request. Marketing copy may say “tell the market what you want.”

Resources

• POST https://api.breezewish.com/v1/requests creates a draft. Scope intents:write. Autonomy DRAFT.
• POST https://api.breezewish.com/v1/requests/{id}/publish publishes it. Scope intents:publish. Autonomy NEGOTIATE.
• POST https://api.breezewish.com/v1/requests/{id}/cancel cancels it. Scope intents:write.
• GET https://api.breezewish.com/v1/requests is the public board.
• MCP: create_request, publish_request, cancel_request, search_public_requests, get_public_request.

create_intent, publish_intent, and cancel_intent are deprecated aliases.

Visibility

Public fields are on the board. MATCHING_ONLY fields are used for routing and are not a public document. PRIVATE fields, including a maximum budget the buyer did not publish, stay off seller and public projections.

Idempotency

Send Idempotency-Key on publish. Reusing the key with the same body returns the original result.

Schema

https://api.breezewish.com/schemas/v1/request.json

The walkthrough in these docs is one buyer request:

Need 8 H200 GPUs for 4 weeks in the US. Start by Nov 1. InfiniBand preferred. Maximum budget private.

The seller in the matching walkthrough is Acme Compute: H200 capacity in the US, 8–64 GPUs, minimum 7-day term.

Common errors