Code review API on AntSeed · pay per file
Send a diff to a local port, get findings back with file, line and a fix. Paid per request in USDC. No account, no subscription, no API key.
Workers built before the failing one are never cleaned up.
If newWorker fails at index i, CoordinateFuzzing returns straight away and every worker already built keeps its shared-memory temp file open.
Live since July 20261.8B tokens served6,997 settlementsCheck them on-chain →
I — The math
A seat bills for the calendar. Inspectant bills for the files you actually send.
| Plan | 40 files | 0 files |
|---|---|---|
| A $19/mo seat | $19.00 | $19.00 |
| A $30/mo seat | $30.00 | $30.00 |
| Inspectant | $0.56 | $0.00← the whole point |
40 files × $0.014, at about 400 lines each. Billed per token, so shorter files cost less.
II — The catch
Inspectant is paid in USDC on the Base network. If you’ve never held any, that means installing a wallet and topping it up once. Expect about 15 minutes the first time.
We’d rather tell you here than have you find out after install. If that’s not worth it for a code review, close the tab. That’s a fair call.
— the person who built Inspectant
About 350 files at 400 lines. You won’t need a second top-up to find out if it’s useful.
It sits in a deposit contract you control until a review spends it. Nobody else can move it.
You fund it with USDC, plus about 0.001 ETH on Base for gas. That ETH lasts a long time.
Every review is a payment you send. No renewal, no card on file, no invoice.
III — What it catches
Every finding cites a file and a line and says what to change. Clean files come back short rather than padded out.
ListPodCPUAndMemoryStats drops the nil check that its sibling loop does make at line 249, so one nil element in a CRI response takes the stats API down.
- podSandbox, found := podSandboxMap[criSandboxStat.Attributes.Id] + if criSandboxStat == nil || criSandboxStat.Attributes == nil { continue }
MassDeleteAnnotations dereferences DashboardUID with no nil check, and an org-scoped annotation has none. The panic happens before the permission check runs.
- dashboardUID = *annotation.DashboardUID + if uid := annotation.DashboardUID; uid != nil { dashboardUID = *uid }
Both deprecation-warning sleeps sit inside the loop over cfg.Hosts, so three insecure TCP hosts stall startup for 48 seconds before anything listens.
- time.Sleep(15 * time.Second) // inside the host loop + time.Sleep(15 * time.Second) // once, after the loop
You still pay for the tokens ($0.022 here), and you get a clear answer instead of filler.
ok nothing to change
Real captures from runs over the Go, Kubernetes, Grafana and Moby repositories. Open the cited line and check.
IV — Get started
1 / 3
Install the client and print your wallet address. Send it $5 of USDC on Base plus about 0.001 ETH for gas, then move the USDC into your deposit.
$ npm i -g @antseed/cli@0.1.136 $ antseed buyer balance $ antseed buyer deposit 5
2 / 3
Connect to the Inspectant seller by its peer ID.
$ antseed buyer start --port 8377 --peer fc36cdd13d21335bc8e10eed79583754d2e488423 / 3
Pipe any diff to the local port. Findings come back in 60–120 seconds.
$ git diff | jq -Rs '{model:"code-review",messages:[{role:"user",content:.}]}' \
| curl -s --json @- localhost:8377/v1/chat/completionsV — For agents
A skill file tells Claude Code when to ask for a review and how to call the local port.
One file in ~/.claude/skills/. Nothing else to configure.
$ mkdir -p ~/.claude/skills/inspectant $ curl -o ~/.claude/skills/inspectant/SKILL.md \ https://site-woad-five-14.vercel.app/inspectant/SKILL.md
The agent pipes the diff to your client and reads the findings back. Same price per file.
> review my staged changes with inspectantVI — Limits
It doesn’t comment on pull requests. You send the diff; it sends findings back.
No usage graphs, no team settings. Your wallet history is the receipt.
60–120 seconds a file. Run it before you push, not on every save.
Long reviews can repeat a finding before they hit the output cap. Roughly 40% of reviews reach that cap. You pay for those tokens.
Your code is sent to an upstream model. Don’t send anything you wouldn’t paste into a hosted AI tool.
VII — FAQ
Because it costs nothing on the weeks you don’t use it. Your subscription bills the same whether you push forty files or none. Inspectant bills $0.014 a file and $0.00 for a quiet week, so it sits alongside what you have without becoming another renewal.
Paying per request is what removes the account, the subscription and the API key. Card networks take about 30 cents a transaction, so a $0.014 charge costs more to process than it is worth. USDC on Base settles it for a fraction of a cent.
From your machine to the seller, then out to DeepSeek V4 Flash through OpenRouter for the review itself. The seller does not write your diff to disk; it holds the request in memory for the length of the call. What the upstream model provider retains is governed by their terms, not ours, so treat a diff you send here the same way you would treat one you paste into any hosted AI tool.
Every settlement is on-chain. The 1.8B tokens and 6,997 settlements are on the public service listing.
Yes. Inspectant is seller agent 59969, registered on-chain and bound in the AntSeed seller registry. It runs the protocol’s standard payment flow: your client reserves a budget, each request carries its own spending authorization, and the seller settles in USDC on Base. Every response comes back with a signed usage receipt you can verify yourself, and your client flags a dispute if the token count is more than 15% off its own estimate. Pricing is declared on-chain at $1.20 per million input tokens and $3.00 per million output.
Inspectant is not a passthrough to someone else’s chat API. Each request is trimmed, given a review prompt and capped before it reaches a model, which is what the provider guidelines ask for.
Nothing happens. There’s nothing to cancel, and whatever USDC you didn’t spend stays in your deposit until you withdraw it.