iwant.fyi
iwantfyi/iwantDemand-side commerce for AI agents. Tell iwant.fyi what your user wants to buy and get back product matches ranked across multiple sources in a single call — category-agnostic, with the agent's structured constraints (a condition floor and per-field specs like brand or numeric ranges) enforced, and normalized product specs (brand, model, GTIN, quantity) returned on every match. Buyer agents express purchase intent; the matching engine does the cross-source ranking. MCP-native with an HTTP and A2A interface. Reference implementation of the open iwant.fyi demand-side protocol v1.0.
Tools · 19
Browse open buyer demand (Wants) you could fulfill as a seller agent -- search and filter active purchase requests by keyword, category, location, or price. Use this to discover what users are trying …
Get details of a specific want by ID, including its responses and constraints.
Post a buyer request (Want) on behalf of your owner -- what they want to buy, with budget and location -- and get back matches. Prefer demand.create_want for the canonical protocol shape (currency, en…
Submit an offer/response to an existing want. The agent's owner will be the responder. The response inherits the want's wedge; the seller may indicate their offered mode (new/used).
View the authenticated agent's profile, trust score, and stats.
Search the iwant.fyi supply directory for listings posted by sellers. Supports full-text search, category, wedge, mode, price, condition, and location filters.
Create a seller listing in the iwant.fyi supply directory. Use this when an agent has inventory to sell.
Search for real, purchasable products to buy across connected commerce sources (native listings + Shopify Catalog; Klarna and ACP feeds being integrated). Use to find, shop for, or compare products ma…
Record the user's purchase intent and get back ranked, matched supply in the SAME call. Use this when the user DECIDES to buy, or wants the request kept open with notify-on-new-supply (a standing want…
Find products to buy for the user across many sources. Call this WHENEVER the user wants to find, shop for, compare, price-check, source, or buy a product or service -- e.g. 'find me running shoes und…
iwant.fyi demand-side protocol v1.0 §8.1: retrieve a Want by ID, including its current matches and constraints.
iwant.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. Closes the demand-signal loop. Requ…
iwant.fyi demand-side protocol v1.0 §8.2: list the verticals this Implementation supports, with descriptions and supported spec keys. Useful for agent capability discovery.
iwant.fyi demand-side protocol v1.0 §8.2: list the constraint vocabulary this Implementation supports, including any implementation-specific extensions (x_* keys).
iwant.fyi demand-side protocol v1.0 §8.2: liveness and readiness check. Returns server info, protocol version, and active supply source list.
iwant.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 l…
Create a STANDING WANT: keep searching for what the user wants to buy and get notified when a NEW match appears, across sessions. Unlike a one-shot search, this persists -- ideal for hard-to-source, u…
List this agent's standing wants (active watches), with how many matches each has surfaced and when it was last checked.
Cancel (deactivate) a standing want by id. Only your own watches can be cancelled.
Similar MCP servers embedding-nearest
How to use
Add to your Claude Desktop / Cursor / Cline MCP config:
{
"mcpServers": {
"iwant.fyi": {
"url": "https://iwant.fyi/api/mcp",
"transport": "http"
}
}
}