Wiredrag is an API that reads your whole codebase at once, lists the places a value travels and names where each trace stopped.
2,147,483,647 + 1 = -2,147,483,648
Send one commit of a repository up to six million lines and a question, like every place orders.id is still held as a 32-bit integer. It reads all of it in one context and returns each place with its file and line, marked found or unconfirmed, and names every file it did not read.
$180 a question, quoted before you ask. The first one is free.

Four ways to answer an every-place question, and the one where ours costs more
Three kinds of tool a staff engineer already reaches for, and this endpoint. Magic's ten-million-line model is left out: nothing is offered to buy.
Criterion
- Reads every file
- Follows the value
- Says what it skipped
- One question costs
Wiredrag
- All of it, in one context
- Protobuf, Java, schemas, keys, exports
- Every answer, with reasons
- $50 or $180; minutes
Grep and the type checker
- Grep reads all; the checker, one language
- Names, not values; stops at services
- No: hits and errors, not coverage
- Nothing; a second
1M-token slices
- A fortieth per slice
- Inside one slice only
- No: forty answers, no ledger
- About $400 a pass
A retrieval tool
- The chunks it retrieves
- As far as retrieved chunks reach
- Answers from what it retrieved
- A flat team plan, usage included
A four-million-line monorepo is forty 1M-token context windows long
40x
the repository against one 1M-token window
At about ten tokens a line, the ratio Magic gives for 100 million tokens and ten million lines, four million lines come to some 40 million tokens.
One 1M-token window holds a fortieth of it.
Grep answers in a second and costs nothing. A question here takes minutes and costs $40 to $180.
For anything one file can answer, we are the wrong tool. Keep us for the question whose answer is a list nobody has finished.
It wins where the value changes its name and crosses into another language
See what one answer holdsOne context holds the whole repository, so a field declared in /proto and filled in /services/billing is seen from both ends.
order_id, orderId, oid - one value under every name it takes
Cache keys and CSV exports - where the value turns into text
Unconfirmed - each trace that stopped, and where

Shown: the unconfirmed part of an answer. Places traced only as far as a boundary, and the files it did not read.