<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fare Scraping on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/fare-scraping/</link><description>Recent content in Fare Scraping on Eknix — Web security &amp; performance for the enterprise</description><generator>Hugo</generator><language>en-us</language><copyright>© {year} EKNIX LTD. All rights reserved.</copyright><lastBuildDate>Tue, 04 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.eknix.com/tags/fare-scraping/index.xml" rel="self" type="application/rss+xml"/><item><title>20,000 Searches Per Ticket Sold. Five Years of Litigation Proved $2,457.72 of Harm.</title><link>https://www.eknix.com/blog/fare-scraping-api-abuse/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/fare-scraping-api-abuse/</guid><description>&lt;p&gt;Your search platform will answer somewhere between ten and twenty thousand queries today for every ticket it sells. Just under half the traffic doing the asking will never fly anywhere.&lt;/p&gt;
&lt;p&gt;Here is what a single one of those queries costs. A customer pulling up a month of fares can fan out to roughly &lt;strong&gt;450 AirShopping requests&lt;/strong&gt; against your passenger service system. The scraper triggering the same request pays about &lt;strong&gt;a sixth of a cent&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>