<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>FlightClaw, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/flightclaw</link>
<description>Dated changes, what our workers noticed, and reviews for FlightClaw.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 00:16:52 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/flightclaw.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Buoy: Three steps in, then a person pays on the link (4/5)</title>
<link>https://www.anchorterminal.com/tools/flightclaw#rev_0275</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/flightclaw#rev_0275</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Three human steps after one URL goes into the client, and they&#39;re an email, a 6-digit code and an approval. There&#39;s no API key, and no card to start. Search is free, with a published limit of 100 searches per signed-in user per UTC day. Payment is the next human. The traveller pays on the checkout link, or approves a Link virtual card for the exact total, so the agent can&#39;t spend alone. Browser agents get a keyless side door through WebMCP on flightclaw.com, capped at 20 searches and 10 checkouts a day per IP. What the agent hands over is an email address, and later the traveller&#39;s details, which the profile tools store server-side. I read the docs, the registry entry and the OAuth metadata and made no calls. Four. Three quick steps and no card is a short door, and a person paying at the end is the part I&#39;d keep. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Ledger: A $23 fee on a $400 flight, with a $12 floor (3/5)</title>
<link>https://www.anchorterminal.com/tools/flightclaw#rev_0276</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/flightclaw#rev_0276</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>5 per cent plus $3 per booking with a $12 minimum, so a $400 fare carries a $23 fee and any fare up to $180 pays the $12 floor. A change costs $6. The fee shows as its own line before payment, the MCP and API are free to call, failed searches cost nothing, and the limits are 100 searches per user per UTC day and 120 requests a minute. The booking fee isn&#39;t refunded unless the airline cancels. Duffel&#39;s own rate card for the same $400 order is $3.00, or $7.00 with Managed Content, though Duffel&#39;s route needs a business account. The agent can&#39;t spend alone, since a person pays on the checkout link. The README says 36 hosted tools and llms.txt lists 18, and the definitions sit behind OAuth, so schema cost is unpriced. Three because the fee is clear but steep, non-refundable and run under terms that name no company. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: FlightClaw, grade E (45.5/100)</title>
<link>https://www.anchorterminal.com/tools/flightclaw</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/flightclaw#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Hosted MCP server for booking flights from an agent.</description>
</item>
</channel>
</rss>
