API.market vs FeatQ: Which Is Better in 2026?

API.market is an API marketplace for developers and teams building software, automations and AI-agent workflows. It provides a place to discover APIs and use their capabilities, with a hosted Model Context Protocol gateway for agents that support remote MCP connections. The company is registered in the United States, is based in San Francisco and launched in April 2024.

For an agent workflow, the connection endpoint is https://api.market/api/mcp/gateway. Setup documentation is available at https://api.market/mcp. The gateway uses Streamable HTTP and requires an account with OAuth or API-key authentication. It is a hosted proprietary service; it is not offered as a public open-source server implementation. The website and the MCP connection endpoint serve different purposes: clients should connect to the gateway URL, while people can use the setup page to learn how to configure access.

The gateway exposes five tools. search_apis helps find relevant APIs in the catalog. get_api_tools provides information about the operations associated with a selected API. call_api invokes an operation. check_usage helps inspect usage, and manage_subscription handles subscription-related actions. This gives an agent a discovery-and-execution workflow without presenting every catalog operation as a separate tool at connection time.

A typical use starts with a developer defining the capability their application or agent needs. The agent can search for an API, inspect the available operations and required inputs, and then make an authenticated call where access is available. Developers should review the selected provider, its data requirements and its pricing before placing calls in a production workflow. Requests may send task data to the chosen API provider. Subscription changes and calls to paid operations should remain subject to the application owner’s approval and spending controls.

Pricing depends on the selected API. Free tiers and paid plans vary across providers; the marketplace should not be interpreted as unlimited free access to every API. API.market is relevant to developers and teams that want API discovery, access and usage information in a shared workflow, including teams connecting AI agents to external services. Product questions can be sent to hey@api.market.

FeatQ is a hosted feature request board for software products, built for founders and software teams who ship with coding agents. Users submit feature requests and vote without creating an account, so there is no signup wall to abandon. FeatQ ranks requests by votes and comments and shows them on a public board with statuses and a public roadmap.

Each board has its own MCP server at https://featq.com/api/mcp (streamable HTTP, authenticated with the board's API key). Claude Code, Cursor, Codex CLI, Windsurf, Gemini CLI or any other MCP client can connect and use seven tools: list_requests, get_ranked_requests, get_request, generate_spec, update_request_status, get_board_stats and list_competitor_claims. In practice a Monday prompt can be one line: pull the top-voted request from FeatQ and build it. generate_spec turns a request and its comment thread into a build-ready markdown spec. When a request is marked done, FeatQ publishes it to the board's public changelog and emails every voter who opted in, so the people who asked hear that it shipped.

An embeddable widget adds feedback collection to any app with one script tag, including apps built with Lovable, Bolt or v0. FeatQ also watches competitor comparison pages, lists the points those pages make about your product, and turns any point into a feature request.

Pricing is flat per board, with no per-user fee: $19 a month or $144 a year for the first 25 boards, then $29 a month or $228 a year. A lifetime plan is $199 once. Each board holds up to 10,000 voters. 14-day money-back guarantee.

Who it is for: founders and software teams who build with coding agents, Shopify and other app-store app makers, and anyone whose next step after a vote is a coding agent. Use cases include a public product roadmap with voting, collecting feature requests on one board, and a changelog that tells voters when their request shipped.

Integrations: Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, ChatGPT and Grok over MCP; the feedback widget works in apps built with Lovable, Bolt and v0. Docs cover the MCP server, the widget and end-to-end automation at featq.com/docs.

What problem it solves

Feedback boards become graveyards: votes go in and nothing comes out, and the people who asked never hear back. The expensive step for a team shipping with a coding agent is no longer the code, it is choosing what to build next. FeatQ connects the vote to the code: the agent pulls the top request as a spec, builds it, marks it done, and every voter gets the changelog by email.