Buy a member's offering over x402
An x402 v2 resource (coinbase/x402 specs/transports-v2/http.md). Without a payment header it answers 402 with PaymentRequirements (in the PAYMENT-REQUIRED header and the body) whose payTo is the SELLING MEMBER's own address: Base USDC (exact, EIP-3009) and, when the member takes it, Solana USDC (exact, fee payer from the CDP facilitator). Retry with PAYMENT-SIGNATURE (or the v1 X-PAYMENT) header: IC checks the payment itself, settles through the CDP facilitator straight into the member's wallet, fulfils (file link, booking, paid inbox message, the member's webhook, or manual) and returns the receipt with PAYMENT-RESPONSE / X-PAYMENT-RESPONSE. The same payment replayed returns the same receipt and is never fulfilled twice. A fulfilment that fails after settlement still returns the receipt (status fulfilment_failed); the member is told. 202 = settlement_pending: retry the same request, never pay again. IC holds no funds and takes no fee. Unknown handle, unknown slug, paused and taken-down offerings all answer the same 404. MCP discovery: ic_offerings_get. 404 unless offerings are enabled.
Request
- Base URL: https://www.immersivecommons.com
- URL: https://www.immersivecommons.com/m/{handle}/x/{slug}
- Auth: none required
Path parameters
The selling member's IC handle.
The offering's slug.
Query parameters
pay_what_you_want only: the decimal USDC you choose to pay, at least the minimum.
per_unit only: how many units.
Advertise only this network.
Headers
Base64 x402 PaymentPayload (v2). X-PAYMENT is accepted too.
Request body
By kind. message: { message, from_name?, reply_to? }. booking: { start, name, email, note?, hold_token? }. manual: { note?, contact? }. webhook: any JSON (forwarded as input). file: none.
Response
Paid, settled and fulfilled (or fulfilment_failed): the receipt and the result.
Changes
No recorded changes to this operation across all 1 revision of this API.