streamable-httpApache-2.0updated 3mo ago
The iwant.fyi demand-side protocol defines how AI agents express structured purchase intent on behalf of users, receive matched supply across multiple sources, and report outcomes back. It is MCP-native, transport-flexible, and intentionally agnostic about who matches the demand, who fulfills it, and how money moves.
What can you do with iwant fyi demand side commerce?
iwant.fyi demand-side protocol
The iwant.fyi demand-side protocol defines how AI agents express structured purchase intent on behalf of users, receive matched supply across multiple sources, and report outcomes back. It is MCP-native, transport-flexible, and intentionally agnostic about who matches the demand, who fulfills it, and how money moves.
Why
Existing agentic commerce protocols are supply-side: ACP and UCP define how an agent completes a purchase at a merchant; AP2 handles payment authorization; MCP is general tool/data access. None of them defines how an agent expresses what its user wants in a structured, machine-matchable form, or how that demand persists across sessions and gets fulfilled across multiple sources.
The iwant.fyi demand-side protocol fills that gap.
Spec
- v1.1 (Draft) — Current. Additive, backward-compatible with v1.0: signed webhooks for Standing Wants (§16), partial-result transparency (§6.1), retryable error taxonomy (§11.2), idempotency keys (§8.4), capability discovery (§8.2), deterministic ordering + cursor (§6.3).
Read it rendered with anchors at iwant.fyi/protocol/v1.
JSON Schema for the core objects: schemas/1.1/ (also served live at
https://iwant.fyi/.well-known/iwantfyi/schemas/1.1/).
Conformance
A test kit verifies any implementation against spec §15:
npx @iwantfyi/conformance-kit --mcp https://iwant.fyi/api/mcp --http https://iwant.fyi/api/v1 --api-key <key>
Source: conformance-kit/ · npm: @iwantfyi/conformance-kit (Apache-2.0). The
reference implementation also self-reports at /api/v1/conformance.
Reference implementation
iwant.fyi — https://iwant.fyi/api/mcp
The iwant.fyi MCP server is the reference implementation. It advertises spec conformance and is the canonical surface to test against.
Official SDKs (all Apache 2.0)
| Framework | Package | Repo |
|---|---|---|
| TypeScript / generic | @iwantfyi/sdk |
staugs/iwantfyi-sdk |
| LangChain (Python) | iwantfyi-langchain |
staugs/iwantfyi-langchain |
| Composio (Python) | iwantfyi-composio |
staugs/iwantfyi-composio |
| CrewAI (Python) | iwantfyi-crewai |
staugs/iwantfyi-crewai |
Three open-source example agents at staugs/iwantfyi-examples.
Status
v1.1 is published as a draft for public comment. Feedback, issues, and proposed extensions are welcome via GitHub issues or directly to hi@iwant.fyi.
License
The specification is published under the Apache License 2.0. Implementations are not required to be open source.
Install
Add iwant fyi demand side commerce to your client. Pick the one you use.
claude mcp add --transport http iwant-fyi-demand-side-commerce https://iwant.fyi/api/mcpcodex mcp add iwant-fyi-demand-side-commerce --url https://iwant.fyi/api/mcp{
"mcpServers": {
"iwant-fyi-demand-side-commerce": {
"url": "https://iwant.fyi/api/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"iwant-fyi-demand-side-commerce": {
"type": "http",
"url": "https://iwant.fyi/api/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"iwant-fyi-demand-side-commerce": {
"url": "https://iwant.fyi/api/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"iwant-fyi-demand-side-commerce": {
"serverUrl": "https://iwant.fyi/api/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation17/25
- Maintenance22/25
- Trust13/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 85 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.1.0Latest | Jun 9, 2026 |
| 1.0.1 | Jun 7, 2026 |
| 1.0.0 | Jun 6, 2026 |