Urgent.News

What's breaking now, across thousands of outlets.

Tech

I wired a free no-key deals API into my agent: 7 MCP tools, verified discounts

I built fazy.com, a price-checked deals site. Last week I needed deal data inside an agent without scraping, so I used our own API. It is free, no key, 60 req/min, and read-only. Here is the whole integration. The API: https://fazy.com/developers The MCP server: https://fazy.com/mcp (7 tools: search_deals, get_deal, get_price_history, similar_deals, list_categories, catalog_slice, post_brief) Why…

I have integrated a free no-key deals API into my agent, enabling it to access verified discount information without the need for scraping. This integration is possible through fazy.com, a price-checked deals site that I built. The API is free to use, requires no authentication key, and allows for 60 requests per minute. It offers read-only access to deal data.

The API can be accessed via the following link: https://fazy.com/developers. Additionally, there is an MCP server available at https://fazy.com/mcp, which provides seven tools for interacting with the deals data: search_deals, get_deal, get_price_history, similar_deals, list_categories, catalog_slice, and post_brief.

Unlike scraping, this API provides several advantages. Each deal includes a verified discount percentage (discount_pct), as well as the current and reference prices. The get_price_history endpoint returns records of price changes along with their corresponding dates. This allows the agent to determine whether a deal is genuinely a good value, rather than simply trusting the store's displayed price.

To verify this methodology, we compared our own catalogue against the prices provided by the API. We found that 83% of the time, the API's prices did not match the listed prices on the retailer's website. This discrepancy was documented in more detail here: https://fazy.com/blog/was-prices-we-never-saw.

When using the API, a minimal example cURL command can be used without requiring a key:

curl https://fazy.com/api/v1/deals/search?q=robot+vacuum

The response will include the following relevant fields for each deal: discount_pct, price, reference_price, merchant, in_stock, and a url field pointing to the deal's page. For MCP clients, they can simply point to https://fazy.com/mcp, and the API's tools will be accessible.

The repository containing the source code for this integration can be found here: https://github.com/FazyFer/fazy-mcp.

As the founder of this project, I am naturally enthusiastic about the potential of this free API and the valuable data it provides. I am more than happy to answer any questions regarding the price-tracking methodology employed by the API.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

CVE-2026-96355: Six Impact Classes, Only One of Which Is a Defacement Problem

CVE-2026-96355: Six Impact Classes, Only One of Which Is a Defacement Problem Not every severe-sounding advisory is equally severe in practice.

  • Six impact classes identified from Drupal extension vulnerabilities
  • Only one class involves defacement, others include code execution and privilege escalation
  • Advisory released September 23, 2026, aggregates 36 CVE identifiers

Our slopsquatting detector had three ways to say "safe". None of them needed evidence.

Ask a language model which package to use and, now and then, it names one that does not exist. If someone registers that name first, the next developer — or the next coding agent — who follows the…

  • Three criteria assessed package safety: age, provenance, registration
  • Age criterion classified packages based on publication days
  • Registration criterion had issues with false positives and creation date

Open-Source Device CVEs: What to Patch by Vertical (September 2026)

Originally published on TECH VEDA: Open-Source Device CVEs: What to Patch by Vertical (September 2026) . This is a monthly series covering the device stack beyond the Linux kernel.

  • 36 open-source device CVEs discovered in September 2026
  • U-Boot network boot code, TLS libraries, libxml2, and Python affected most
  • Chromium V8 CVEs with published proof of concept require immediate patching

More from Friday 2 October →