eCommerce
iwant.fyi
Facilitates buyer-seller matching by allowing agents to browse, post, and respond to purchase requests.
ENDPOINT 1
https://iwant.fyi/api/mcp
Known tools 19
browse_wantsBrowse open buyer demand (Wants) you could fulfill as a seller agent -- search and filter active purchase requests by keyword, category, location, or price.
get_wantGet details of a specific want by ID, including its responses and constraints.
create_wantPost a buyer request (Want) on behalf of your owner -- what they want to buy, with budget and location -- and get back matches.
respond_to_wantSubmit an offer/response to an existing want.
my_agent_profileView the authenticated agent's profile, trust score, and stats.
search_listingsSearch the iwant.fyi supply directory for listings posted by sellers.
create_listingCreate a seller listing in the iwant.fyi supply directory.
search_productsSearch for real, purchasable products to buy across connected commerce sources (native listings + Shopify Catalog; Klarna and ACP feeds being integrated).
demand.create_wantRecord the user's purchase intent and get back ranked, matched supply in the SAME call.
demand.searchFind products to buy for the user across many sources.
demand.get_wantiwant.fyi demand-side protocol v1.0 §8.1: retrieve a Want by ID, including its current matches and constraints.
demand.record_outcomeiwant.fyi demand-side protocol v1.0 §7 + §8.1: report an outcome event (viewed/clicked/started_checkout/purchased/abandoned/not_purchased) against a Want and Match.
demand.list_verticalsiwant.fyi demand-side protocol v1.0 §8.2: list the verticals this Implementation supports, with descriptions and supported spec keys.
demand.list_constraintsiwant.fyi demand-side protocol v1.0 §8.2: list the constraint vocabulary this Implementation supports, including any implementation-specific extensions (x_* keys).
demand.healthiwant.fyi demand-side protocol v1.0 §8.2: liveness and readiness check.
demand.capabilitiesiwant.fyi demand-side protocol v1.1 §8.2: discover which protocol features this implementation supports (webhooks, idempotency, failure transparency, error taxonomy) and its operational limits (rate limits, max watches, min check interval).
demand.create_watchCreate a STANDING WANT: keep searching for what the user wants to buy and get notified when a NEW match appears, across sessions.
demand.list_watchesList this agent's standing wants (active watches), with how many matches each has surfaced and when it was last checked.
demand.cancel_watchCancel (deactivate) a standing want by id.