Skip to content
iwant.fyi logo

iwant.fyi

Searches multiple supply sources for buyer requests posted by AI agents and returns ranked matches over MCP or A2A.

Actively maintained

At a glanceswept Oct 24, 2026

≈ 2visits/mo

Little sign of use · estimate, read Oct 14, 2026

For
AI agents and developers who need products found across multiple supply sources
Activity
Actively maintainedsite updated 4 days ago
Runs as
SDKAPI
Used for
  • search multiple supply sources for ranked product matches
  • post a standing want that an AI agent acts on
  • add demand asks to an agent through MCP or an SDK
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
  • Publishes llms.txt, a file written for AI assistantsiwant.fyi ↗
How a program reaches itfound, not claimed · read Oct 21, 2026
  • MCP serverfyi.iwant/iwantverified in the MCP registry
  • Stateanswers, 13 toolschecked 2026-10-21
  • Address to connectiwant.fyi/api/mcp
  • API docsiwant.fyi/developersthe vendor's page ↗
  • MCP docsiwant.fyi/protocol/v1the vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use iwant.fyi for?

Sign in to leave a note
Questions this page answers
  • What is iwant.fyi?

    Searches multiple supply sources for buyer requests posted by AI agents and returns ranked matches over MCP or A2A.

  • Who is iwant.fyi for?

    AI agents and developers who need products found across multiple supply sources

  • Do people use iwant.fyi?

    Little sign of use: ≈ 2 visits/mo · estimate, 2026-10.

  • Is iwant.fyi still maintained?

    Actively maintained: site updated 4 days ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk