BuyAPI

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Vendor intelligence for AI coding agents choosing developer tools and stacks.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "BuyAPI": {
      "url": "https://buyapi.ai/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• vendors.resolve read-only

  First stop for category-specific vendor recommendations and vendor ID discovery. Finds BuyAPI vendor IDs for a user question; provide category when known. Use this when the user asks which provider in a category fits their constraints. With a covered category, the response includes ranked results plus a top-3 decision matrix with fit labels, confidence, tradeoffs, cost notes, freshness, and sources. 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.

  Parameters:

  • query (required) — string — The user's question or task context for relevance ranking
  • category — string — Optional category: database, auth, hosting, payments, email, analytics, feature-flags

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• vendors.details read-only

  Follow-up tool for one known vendor. Retrieves detailed pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase. Use this after a candidate is selected and the user needs claim-level pricing, limit, gotcha, or provenance details.

  Parameters:

  • vendorId (required) — string — BuyAPI vendor ID, e.g. /database/supabase
  • query — string — Specific question to focus the response on

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• vendors.evidence read-only

  Returns recent reviewed BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a recommendation, or what recent human/source/opinion/history signals exist. This is a trust and provenance follow-up, not the first recommendation tool.

  Parameters:

  • subjectType (required) — string — Evidence subject type
  • subjectId (required) — string — Subject ID, e.g. /database/supabase or database
  • limit — number — Maximum rows to return

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• stacks.findSimilar read-only

  Finds reviewed public stack examples 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. Do not use it as a generic recommendation tool.

  Parameters:

  • limit — number — Maximum stacks to return
  • vendorId — string — Optional BuyAPI vendor ID, e.g. /database/convex

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• vendors.compare read-only

  Compares two or more already-known BuyAPI vendors for a specific workload or decision. Use this when the candidate set is known, for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace". If the user has not named candidates, use vendors.resolve first.

  Parameters:

  • vendorIds (required) — array — BuyAPI vendor IDs, e.g. ['/database/convex', '/database/neon']
  • query (required) — string — The user's decision context
  • workload — object — Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• vendors.estimateCost read-only

  Produces directional monthly cost estimates from BuyAPI pricing data and explicit workload inputs. Use this only when the user asks for cost math and provides explicit workload inputs. Missing workload fields are returned as assumptions or unknowns instead of being hallucinated. Treat results as BuyAPI claim-based estimate math; verify exact billing in first-party docs, vendor CLIs, or vendor MCPs before purchase or production decisions.

  Parameters:

  • workload (required) — object — Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.
  • category — string — Optional category to estimate across the current corpus
  • vendorIds — array — Optional vendor IDs to estimate directly

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• stacks.recommend read-only

  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 multi-layer 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.

  Parameters:

  • projectDescription (required) — string — What the user is building
  • workload — object — Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.
  • stackFacts — object — Optional derived stack facts such as languages, frameworks, runtimes, package managers, test tools, and dev workflow. Do not pass source code or secrets.
  • constraints — string — Budget, scale, existing tools, team size, compliance needs
  • stackContext — array — Optional existing stack context from a repo scan or saved private stack. Agents should pass derived tool metadata only, not source code.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.