BuyAPI

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.

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.

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.

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.

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".

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.

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.