Report · measured 2026-08-29
Three tasks, each done twice
Once by asking an agent. Once by hand — every call a person would have to make, in the same minute, over the same node. The plan was to measure how much time an agent saves.
That is not what came back. The hand-done route answered 0 of 3 questions; the agent answered 3 of 3. On one task the hand-done path was quicker — because the public node refused its log queries, so it skipped the only expensive step and returned a number it already had. The fastest path in any comparison is always the broken one, which is why no ratio is published where a side failed to answer.
How the hand-done path was measured. It is a script issuing the same calls a person would have to issue — no page loads, no reading, no typing an address into a block explorer, no deciding which explorer to open. It is therefore a floor on what a person costs, never an estimate of it. Inflating that side would have been easy and would have made this document worthless.
What is recorded as a failure. A query the node refused is recorded as unmeasured, never as zero. “Nobody traded in this pool” and “we could not look” are different answers, and a report that renders them the same is worse than no report.
What can be re-run. Everything. node scripts/advantage-report.mjs writes the JSON this page is generated from; the endpoints it calls are public, need no key, and are the same ones any caller gets.
Task 1trading / liquidity provision
I have $10,000 to provide as liquidity for CAKE/WBNB on PancakeSwap. Which of the five fee tiers should it go into?
The pair lives in up to five pools at once. Every public interface ranks them by the capital already parked in them, and that is not what an LP is paid on.
Asking the agent
2,833 ms
1 request
Answered the question
Doing it by hand
1,553 ms
22 requests
Did not answer
the public node refused the log range, so no tier could be priced — only the capital ranking survived, which is the number every public interface already shows
No time ratio is published for this task. One of the two paths never produced the answer, and dividing a time by a non-answer would turn a failure into a benchmark.
What the five pools actually paid, over minutes of chain
| Tier | Capital parked | Swaps | Fees paid | Fees per $1,000 parked |
|---|
| V2 0.25% |
$16,788,287.11 |
47 |
$3.06 |
$0.00018 |
| V3 0.01% |
$24,253.04 |
183 |
$0.69 |
$0.02865 |
| V3 0.05% |
$1,125,592.03 |
86 |
$18.94 |
$0.01682 |
| V3 0.25% |
$3,954,044.46 |
4 |
$2.17 |
$0.00055 |
| V3 1.00% |
$2,863.54 |
0 |
$0 |
$0.00000 |
The tier holding the most capital is V2 0.25%. The tier that paid best is V3 0.01%. Every public interface ranks this pair by the first column; an LP is paid on the last one. Measured over a single -minute window and deliberately not annualised — forty minutes of flow says what happened in forty minutes.
Task 2security / risk
Before I take a $5,000 position: what does that trade actually cost, and can the liquidity behind it be withdrawn tomorrow?
The headline slippage a router shows is not the cost. Transfer tax, price impact and swap fee are three different numbers, and LP withdrawability is not on the token page at all.
Asking the agent
3,278 ms
1 request
Answered the question
Doing it by hand
382 ms
6 requests
Did not answer
the transfer tax and the share of liquidity this pool represents are both missing. Neither is a field to read: the tax only exists in the difference between what a swap sent and what arrived, and the share needs every other pool on every other venue found first.
No time ratio is published for this task. One of the two paths never produced the answer, and dividing a time by a non-answer would turn a failure into a benchmark.
Task 3agent discovery / hiring
Find me an agent on BNB Smart Chain that monitors a Venus health factor, and tell me what it charges.
The identity registry holds hundreds of thousands of ids with no index and no search, and it grows every hour. Nothing about it is queryable by what an agent does.
Asking the agent
387 ms
1 request
Answered the question
Doing it by hand
11,559 ms
187 requests
Did not answer
no candidate was produced. The registry has no index: 150 ids were read to measure the rate, and that is 0.05% of it.
No time ratio is published for this task. One of the two paths never produced the answer, and dividing a time by a non-answer would turn a failure into a benchmark.
What this does and does not show
- Both paths read the same chain over the same RPC in the same run, so network conditions apply to both equally.
- The manual path is a lower bound on human effort and is described that way everywhere it appears.
- Task 3 extrapolates from a measured per-id rate over a 150-id sample. The extrapolation is labelled; the measurement is real.
- Speed is the weakest of the three columns. Two of the three tasks produce a different answer by hand, not merely a later one.
- Every endpoint used on the agent side is free and unauthenticated. The cost difference in this report is not a subscription — it is a person.