BuyAPI
BuyAPI gives AI agents real-time access to software pricing, vendor intelligence, and stack recommendations.
What it can do
- Vendors.Resolve: Finds BuyAPI vendor IDs for a user question. Category is optional; provide it when known. Use this for vendor discovery before vendors.details, or when the user asks which provider in
- Vendors.Details: Retrieves detailed vendor information including pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a B
- Vendors.Evidence: Returns recent BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a vendor page, or wh
What data it sees
Do you need an account
No: the server works without sign-in
BuyAPI gives AI agents real-time access to software pricing, vendor intelligence, and stack recommendations. Search and compare SaaS products, get structured pricing data, and make smarter software buying decisions — all through a simple MCP interface.
How to connect
How to connect BuyAPI to Claude
The server address to paste into Claude settings:
https://buyapi.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect BuyAPI to ChatGPT
The server address to paste into ChatGPT settings:
https://buyapi.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect BuyAPI to Cursor
The server address to paste into Cursor settings:
https://buyapi.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (7)
Raw names from tools/list. Only developers need these.
| vendors.resolve | Finds BuyAPI vendor IDs for a user question. Category is optional; provide it when known. Use this for vendor discovery before vendors.details, or when the user asks which provider in a category fits their constraints. Do not use this for local coding/debugging/docs questions unless they involve choosing a software vendor or tool. If the category is outside BuyAPI's corpus, the tool returns an explicit "not in corpus yet" result instead of inventing vendors. |
| vendors.details | Retrieves detailed vendor information including pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase. |
| vendors.evidence | Returns recent BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a vendor page, or what recent human/source signals exist. |
| stacks.findSimilar | Finds public stack profiles related to a vendor or recent curated stack examples. Use this when the user asks who uses a tool, what similar builders use, or wants examples of real stack combinations. |
| vendors.compare | Compares two or more BuyAPI vendors for a specific workload or decision. Use this for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace". |
| vendors.estimateCost | Produces deterministic monthly cost estimates from BuyAPI pricing data and explicit workload inputs. Use this when the user asks for cost math. Missing workload fields are returned as assumptions or unknowns instead of being hallucinated. |
| stacks.recommend | Recommends a complete stack from BuyAPI's corpus with a structured decision matrix, cost estimate, assumptions, unknowns, alternatives, and sources. Use this when the user is starting a project or asks for a complete stack choice. Do not use this for local coding/debugging/docs questions that do not involve software or vendor selection. Do not call vendors.resolve first; this tool handles retrieval and ranking. |