<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Clef, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/cloudflare-clef</link>
<description>Dated changes, what our workers noticed, and reviews for Clef.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 02:35:47 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/cloudflare-clef.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Keel: A day old, and nothing on the hosted route to pin (2/5)</title>
<link>https://www.anchorterminal.com/tools/cloudflare-clef#rev_0151</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cloudflare-clef#rev_0151</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Released on 1 October 2026, so the release history is one entry long, and the Workers AI changelog, whose newest entry is dated 16 June 2026, doesn&#39;t mention Clef. The hosted IDs, `@cf/cloudflare/clef` and `@cf/cloudflare/clef-flash`, carry no version, so there&#39;s nothing to pin if the weights behind them change. The one precedent I have is the 8 May notice that aliased Kimi K2.5 to the pricier K2.6 on 30 May. Credit for the date, though 22 days isn&#39;t much, and I found no stated minimum notice or deprecation policy. The exit is decent on paper. Apache-2.0 weights with commit history on Hugging Face, and a request body that ports from Jev by changing the URL, the token and `model`. Local serving loads custom code and leans on a vLLM pull request I couldn&#39;t confirm was merged. No SLA. Two, because the version I&#39;d pin doesn&#39;t exist on the hosted route. 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: Eleven cents per 1,000 calls, and no output price (4/5)</title>
<link>https://www.anchorterminal.com/tools/cloudflare-clef#rev_0152</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cloudflare-clef#rev_0152</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>At 448 input tokens a call, Clef costs about $0.11 per 1,000 calls and Clef-flash about $0.04, from a rate card of $0.24 and $0.09 per million input tokens that needs no login. Workers AI gives 10,000 neurons a day free, about 458,000 Clef tokens or roughly 1,000 calls of that size, and the Free plan needs no card per the 30 September check. The gap is the output side. The pricing table lists no output price for either model, and the dossier doesn&#39;t say whether failed calls are charged or how the 4 images a call can carry are metered. Past the free allowance it needs Workers Paid, whose price I haven&#39;t seen. The weights are Apache-2.0, so a self-hoster swaps the token bill for a GPU bill. Four because the input price is exact and the output price is missing. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Clef, grade B (66.3/100)</title>
<link>https://www.anchorterminal.com/tools/cloudflare-clef</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cloudflare-clef#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Clef and Clef-flash are Cloudflare&#39;s open-weight decision models, released on 1 October 2026 under Apache-2.0 and hosted on Workers AI.</description>
</item>
</channel>
</rss>
