Skip to content
Fennec Wire

About

The fox, the wire,
and the rules.

Fennec Wire is a news channel for the AI ecosystem — English, daily, and written for people who have to make decisions with the numbers.

The name

Why a fennec.

The fennec is the desert fox: the smallest of the foxes, with the largest ears of any fox, and an animal that does its work after dark. Those ears are not decoration — they are how it finds what is moving under the sand, long before it is visible.

That is the job here. The AI ecosystem moves at night, in release notes, pricing pages, model cards and repository commits. Most of it is noise. A small part of it changes what you can build on Monday morning. We listen for that part.

The wire is the other half: a wire service, the feed that carries a story from the source to the reader with the facts intact. Not a magazine, not opinions — a wire, with the source attached.

The fox keeps watch. The wire carries what is true. Nothing gets published because it is loud.


Coverage

What we watch.

  • LLMs — Releases, benchmark runs and the claims that hold up — what actually changed between two model versions.
  • Cloud — AWS, Google Cloud, Azure, OVHcloud, Cloudflare: inference endpoints, regions, limits and what they cost.
  • Tokens — Per-token prices, cache pricing, context windows and the bill at the end of the month. Numbers, not adjectives.
  • Models — Open-weight against closed-weight: what ships, what stalls, what the licence actually allows.
  • Harness — The tools agents run inside — sandboxes, permissions, subagents, and the failure modes that come with them.
  • Claude Code — The agentic coding stack followed release by release: skills, hooks, MCP servers, and the workflows around them.

Out of scope

What we do not cover.

A channel is defined as much by what it refuses as by what it publishes. Three things never make it onto Fennec Wire:

  • Partisan politics. Policy that changes what a model may do is news; the horse race around it is not ours to call.
  • People. Who hired whom, who argued with whom. The ecosystem is the subject, not the personalities in it.
  • Unsourced rumors. A screenshot is not a source. If it cannot be traced to something a company published, it is not published here.

And no press releases rewritten as news. If a vendor announcement matters, it matters because of what it changes — and that is what gets reported.


The charter

Rigor before speed.

These rules are published so they can be held against us. They apply to every video, thread and description we put out.

Sourced or it does not ship

Every price, benchmark score and release date carries its source. If a figure cannot be traced back to a primary announcement or a public leaderboard, it does not make the cut.

No invented numbers

We would rather publish nothing than a plausible number. Estimates are labelled as estimates, and the method behind them is shown.

Rigor before speed

A story published an hour late with the right numbers beats one published first with the wrong ones. Corrections are published, not quietly edited.

Corrections

When we get something wrong, the correction is published where the mistake was made — visible, dated, and not a silent edit. If a figure turns out to be wrong, the figure is the thing that gets fixed first.

Spotted an error? Write tocorrections@fennecwire.com.

Channels

Where to find us.

YouTubeWeekly briefings and deep dives — benchmarks read line by line, pricing tables checked twice.
@fennecwire
TikTokOne release, one number, sixty seconds. The cut that fits between two meetings.
@fennecwire.news
XLive threads as releases land — prices, context windows, benchmarks, with the source attached.
@fennecwire
EmailTips, corrections, and anything that belongs on the wire.
contact@fennecwire.com