DEV Community: AntSeed

Most AI APIs hand you a label and ask you to believe it.

AntSeed — Tue, 21 Jul 2026 15:59:39 +0000

gpt-5.5. claude-opus-4.8. minimax-m3. "Premium model."

What happens when the endpoint quietly swaps you onto something cheaper? Or mixes your traffic across three providers? Or wraps some other API and slaps a nice name on it? Or serves you a quantized stand-in that's 80% as good and 40% of the cost?

What evidence do you actually have that you got what you paid for?

Honestly, for most APIs the answer is: none. You have a string in a JSON field. That's it.

At AntSeed we're building the verification layer that string was always missing.

A label is not evidence

This isn't some paranoid hypothetical I dreamed up. There's a paper called Real Money, Fake Models that audited "shadow" APIs claiming to serve official frontier models. They found real divergence in utility, safety, and identity. The incentive writes itself. Charge for the expensive model, ship something cheaper, keep the spread. Rinse, repeat.

A centralized provider can wave you toward their brand, their contract, their support desk when you complain. Fine. But a peer to peer market has none of that. Our sellers are independent peers. There's no head office to email. So the evidence has to live somewhere else... it has to travel with the response itself.

And here's the distinction that took us a while to say cleanly:

Signed responses do not prove model identity. They prove who served which bytes.

That's the foundation. Get attribution first. Once a seller's output is provably theirs, you can layer statistical model auditing on top. Cryptographic provenance, then behavioral verification. Order matters, and I'll come back to why.

What's shipping right now: ResponseAuth

The first piece already lives in @antseed/node.

For supported buyer to seller connections, the seller signs a ResponseAuthPayload right after serving a response. That payload locks in:

the request hash and the response hash
buyer peer id and seller peer id
the advertised service and provider name
status code and timing
an optional payment channel id

The buyer checks the signature against the seller's peer identity, then stores the result locally. And a random sample of verified exchanges gets written to disk as full evidence:

<dataDir>/verification_samples/
  <sellerPeerId>/
    <sampleId>/
      manifest.json
      request.bin
      response.bin

Now, this does NOT tell you the response came from the model on the label. Read that twice, because people get it twisted. What it tells you is that the seller can never later deny serving those exact bytes.

That's the whole game right there. It's the line between a complaint and a receipt.

What comes next: fingerprint verifiers

The next layer isn't one clever test. It's a suite. Truth be told, anyone selling you a single "is this the real model?" oracle is selling you something that doesn't exist.

Different cheats leave different fingerprints:

A cheap substitute tends to fall apart on knowledge boundary probes.
A wrapper around a real model can leak instruction hierarchy artifacts.
A relay sometimes gives itself away through runtime behavior.
A whole model family carries rare token or perturbation signatures you can measure.

So the spec tracks a bunch of verifier families, each catching a different lie:

KBF (knowledge boundary fingerprinting): numeric probes right at the edge of what the claimed model should know. See the paper and the reference implementation.
LLMmap-style behavioral probes: prompts picked specifically because model families answer them differently. LLMmap.
TRAP-style adversarial triggers: private prompts that pull out distinctive target-model behavior. TRAP.
ZeroPrint-style perturbation fingerprints: watch how answers shift under meaning-preserving input tweaks. ZeroPrint.
UTF / rare-token fingerprints: poke at under-trained or weird tokens and see what falls out. UTF.
LLMPrint-style prompt-injection fingerprints: exercise instruction hierarchy and injection behavior. LLMPrint.
Julius-style service fingerprints: figure out the serving stack itself, Ollama, vLLM, LiteLLM, whatever's underneath. Julius and its repo.
READER-style passive provenance: analyze ordinary signed responses after the fact. READER.

None of these is gospel on its own. That's the point. You build a suite where independent signals stack up. A SAME result is not a certificate of authenticity. But a strong DIFF, backed by signed response evidence and reproducible references? That's something a buyer can actually act on.

Why public fingerprints should behave like torrents

Here's a tension I keep chewing on.

Private probes are what you need for real enforcement. Because if every seller can see your exact test set, a dishonest one just routes those specific prompts to the real model and serves garbage for everything else. Classic teach-to-the-test.

But public fingerprints still matter a ton. Reproducibility. Smoke tests. Shared baselines. Research. Network-wide learning. The question was never whether to publish them. It was how to publish them without turning AntSeed into yet another centralized API or some hosted database that becomes a single point of failure (and control).

Our answer in the spec: a fingerprint swarm.

Think torrent, not registry.

Torrent concept	AntSeed fingerprint swarm
`.torrent` / magnet metadata	fingerprint pack announcement
info hash	`packId`
tracker / DHT	AntSeed discovery topics
seeders	peers mirroring verified packs
downloaded files	signed fingerprint packs
piece hashes	optional chunk hashes
uploader identity	publisher peer id + signature

A fingerprint pack is a signed, content-addressed bundle. A peer announces a little metadata. Other peers grab the pack from any mirror or seeder, verify the content hash, verify the publisher signature, and then decide for themselves whether to trust it.

The trust model is honestly kind of beautiful in how boring it is:

Discovery tells me a pack exists.
Storage gives me bytes.
Hash proves the bytes are correct.
Signature proves who published the pack.
Local trust policy decides whether I use it.

No central server has to be the oracle. GitHub can be a review surface and a bootstrap mirror. IPFS, Arweave, plain HTTPS mirrors, AntSeed peers, all of them can serve the same pack bytes. Doesn't matter where it came from. If the hash and signature check out, the pack is valid. Full stop.

What this actually enables

The long-term flow ends up looking like this:

A seller advertises a model or service.
The buyer sends normal requests through AntSeed.
The seller signs response provenance with ResponseAuth.
The buyer stores that verified evidence locally.
The buyer imports trusted public fingerprint packs from the swarm.
The buyer keeps private references around for the tougher audits.
The buyer runs the fingerprint verifiers locally.
Routing quietly steers away from sellers with bad evidence.
Disputes and slashing come later, and only after off-chain verification.

That ordering is the whole philosophy, so let me be blunt about it. We do NOT open with slashing. Punishment-first designs are how you get a network full of angry false positives and no sellers. Instead: make responses attributable,

Inference Is the New Oil: Who Controls the Pipe

AntSeed — Wed, 08 Jul 2026 09:23:51 +0000

Inference Is the New Oil- And Most of It Is Sitting Idle
Two-thirds of all AI compute is now inference. Not training. Not research. Serving requests, in production, right now.

That single number — flagged by hardware analyst Derek Colley when comparing Trainium3 and Nvidia's NVL72 rack specs — reframes the entire AI infrastructure conversation. Training built the models. Inference is where the money actually prints. And the industry is only just catching up to that reality.

The Shift Nobody Announced
For years, "AI compute" was shorthand for training runs: the multi-million-dollar, months-long jobs that produced GPT-4 or Claude. Infrastructure investment followed that assumption. Chip design followed it. Investor narratives followed it.

Then inference quietly ate the workload.

McKinsey projects inference will surpass training's share of total AI compute by 2030. Based on the current two-thirds figure, that projection looks conservative. The crossover already happened — we're now watching the gap widen.

The market noticed. Brad Gerstner publicly stated that Anthropic's revenue "went totally parabolic" after Opus 4 launched, suggesting the company could approach $100 billion in annual revenue. He called it "the single most important thing in the market." The Philadelphia Semiconductor Index — a reasonable proxy for how capital is reading AI infrastructure — was up 80% on the back of that revenue signal alone.

Inference profitability isn't a thesis anymore. It's a reported result.

The Hardware Bet Is Changing
When inference dominates the workload, the optimal chip is no longer necessarily the one that wins training benchmarks.

That logic is playing out in real hardware decisions right now. DeepSeek is reportedly building its own inference-specific chip, deliberately stepping back from Nvidia and Huawei silicon. The explicit design goal is inference efficiency — not raw training throughput. AWS's Trainium3 reaches approximately 362 MXFP8 PFLOPs at rack scale. Nvidia's NVL72 sits at roughly 360 PFLOPs on the same metric. On paper, for inference workloads, they're tied.

The GPU-as-default assumption is cracking. Cerebras has positioned itself on latency. Specialized inference chips from multiple directions are closing the gap that Nvidia held comfortably for the training era.

This isn't a chip story. It's a signal that inference has its own economics — and those economics reward different architectural choices than training did.

The Real Bottleneck Isn't Supply
Here's the counterintuitive part: GPU shortage and idle GPU supply are being discussed simultaneously, by serious people, as both being real.

That's not contradiction. That's a distribution problem wearing a capacity problem's clothes.

AI demand is outpacing available supply in the right locations, at the right latency, with the right access layer. Meanwhile, millions of deployed GPUs sit underutilized. The shortage is organized routing, not raw silicon.

Projects like RENDER's Dispersed are building directly on this arbitrage — the gap between deployed GPU capacity and actually-utilized GPU capacity. The thesis is that idle compute is the real unlock, not new builds. If you can route inference workloads to existing hardware that's currently doing nothing, you've solved the shortage without manufacturing a single new chip.

This is the same structural insight that made content delivery networks (CDNs) valuable in the early web era. Building more servers wasn't the answer. Routing intelligently to existing ones was.

AntSeed's Position in This Picture
AntSeed is infrastructure for this exact moment. The core bet: inference routing through a decentralized provider network eliminates the gatekeepers that sit between model capability and the people who need it.

When inference is the workload — not training, not fine-tuning, but live, continuous, production serving — the structural question becomes: who controls the routing layer? Centralized aggregators set the terms. They decide pricing, availability, and access. That's fine until it isn't — until a model goes dark, a rate limit hits, or costs spike because a single provider had a quarter to make.

AntSeed routes around that. Providers plug in compute. Buyers get inference. No single point of control. Check live network stats to see the current state of the network — requests handled, providers active, cost per token versus centralized alternatives.

The comparison to OpenRouter and other aggregators isn't abstract. It's architectural. One model centralizes routing control; the other distributes it. When inference is two-thirds of all AI compute and that share is growing, the routing layer is the oil pipeline. The question is who owns it.

What This Means for the Next Two Years
A few things that follow from the inference-first reality:

Model providers will be judged on serving economics, not just benchmark scores. Anthropic's parabolic revenue is a serving story, not a training story.
Chip design will bifurcate further. Training chips and inference chips will increasingly be optimized for different objectives. Buying the best training chip to run inference is like buying a freight truck to do last-mile delivery.
Idle compute becomes a real asset class. The gap between deployed and utilized GPU capacity is large enough to build businesses on — and several projects already are.
Routing infrastructure becomes critical. When inference supply is distributed across data centers, idle consumer hardware, and specialized inference farms, the value lives in the layer that organizes it all.
The oil analogy holds precisely because oil's value wasn't in finding it — it was in refining it, transporting it, and getting it to where it was needed, when it was needed. Inference is the same. The models exist. The compute exists. The value is in the pipe.

Inference overtook training as the dominant AI workload. That's already happened. The hardware industry is catching up to it, the chip design assumptions are shifting because of it, and the revenue numbers from model providers are confirming it.

The bottleneck going forward isn't capacity — it's organized routing of capacity that already exists.

Why we're building an AI market where nobody's the middleman

AntSeed — Sun, 05 Jul 2026 22:32:51 +0000

Quick disclosure before anything else: I'm on the team behind this. Not a neutral reviewer, just someone who got tired of the same thing you probably did.
So a few of us built AntSeed. It's an open market for AI inference. Anyone can sell intelligence, anyone can buy it. Your request goes straight to whichever provider fits, cheapest, fastest, or the one with the best track record, instead of whoever your subscription picked for you months ago.
The part that actually convinced me wasn't the pitch. It was realizing there's no position in this network from which anyone can gatekeep. Not us, not anyone. That's not a policy we wrote down somewhere. It's just how the thing is built.
A few things worth knowing-

No account wall. You open it, you ask something, that's it.
Payments settle per request, straight to the provider.
Some providers run on privacy-hardened hardware, if what you're sending needs to actually stay private.

Two things while I've got you here-
If you've got spare GPU capacity or you're already running inference **for something else, we're looking for more providers on the supply side. Bring your own hardware or API capacity, price it however you want, build a reputation that's yours to keep. No approval process, no listing fee.
And separately, honestly the one I'm most excited about: **we're opening up an early alpha for model fingerprint verification. The short version of the problem... on an open market, how do you actually know the model you're paying for is the model you're getting? We're building a verification layer around it, and we want a small group of technical people poking holes in it before it's public.
Happy to answer anything below, especially the skeptical questions. Those are usually the good ones.