AgentDeals is a developer infrastructure deals aggregation tool whose core goal is to let AI coding agents or developers themselves directly obtain current free tiers, startup credits, and pricing information during technology selection, without having to leave their workflow to check vendor pages one by one.
Purpose
It primarily solves the problem that "AI agents usually recommend infrastructure based on training data rather than current pricing." By integrating with AgentDeals, agents can query real-time indexed free tiers, startup credits, and price changes, verifying whether a deal is still valid before recommending a tech stack.
Main Capabilities
- Directory scale: indexes pricing data for 1,400+ developer infrastructure vendors across 60 categories. Each record carries a "last read vendor page" date, and each listing page notes the number of entries in that collection confirmed by a read within the last 90 days; the actual number is published by /api/freshness rather than asserted here.
- Search and filtering: supports searching deals by keyword, category, and eligibility (public, accelerator, oss, student, fintech, geographic, enterprise), sorting by vendor name, category, and latest directory date, as well as since-date filtering and pagination.
- Vendor comparison: compare_vendors can perform a risk check on one vendor or a side-by-side comparison of two vendors, with output including risks and alternatives.
- Change tracking: track_changes can show pricing changes, including types such as free tier removal, limit reduction, limit increase, new free tier, and pricing restructuring, and supports filtering by vendor and looking ahead to soon-to-expire deals.
- Recommendations and estimates: when mode is recommend, it can recommend infrastructure based on use case and requirements; estimate/audit modes can estimate or audit based on existing services.
- Referral codes: get_referral_code can retrieve the referral code for a specified vendor.
- Content assets: provides a list of AI/LLM API free tiers (31 vendors), with each row carrying the last read date and source URL; rows with terms changes include the replaced terms.
How to Use
Four integration methods are provided:
- Claude Code plugin: a single command automatically configures the remote MCP server, with no local setup required, and 4 tools and 6 prompt templates are immediately available.
- Claude Desktop extension: download the latest a from Releasesgentdeals.mcpb, install by double-clicking; you can also browse AgentDeals in Settings > Extensions.
- npx local stdio: no server required, runs locally via stdin/stdout.
- Remote HTTP: connect to a hosted instance, no installation required. In addition, you can place .mcp.json in the project root directory, compatible with MCP clients such as Claude Code and Cursor that read this file. A REST API is also provided for programmatic access without MCP. Supports two client configurations, local stdio (recommended, reliable and fast) and remote HTTP, and provides examples of configuration locations for Claude Desktop, Cursor, VS Code (GitHub Copilot), etc.
Use cases
- Selection comparison: e.g., "evaluate a side project between Supabase and Neon," use compare_vendors for a side-by-side comparison.
- Eligibility query: e.g., "we are a YC W24 company, what credits can we get," use search_deals with eligibility: accelerator.
- Verify before recommending: use track_changes to confirm the free tier has not been removed or reduced.
- Monitor changes: call track_changes weekly to get a summary, or use change_type: free_tier_removed to see which vendors have eliminated their free tier.
- Example queries: searching for free database hosting can return Neon, Supabase, MongoDB Atlas, etc.; querying recent pricing changes can return PlanetScale free tier removal, Heroku free dyno discontinuation, etc.
Limitations and unknowns
The material does not specify AgentDeals' specific pricing model, prices, usage limits, data update frequency, or a complete list of coverage; some values are dynamically published by /api/freshness, /api/changes, /setup, and /llms.txt, and this article does not repeat assertions about them. Installation commands and code configurations should be based on the official repository and documentation.
