Agentic Finance Graph

Home/Research/Builder Codes

Builder Codes · live

Which apps build the transactions that move agent money

ERC-8021 lets an app sign the transactions it builds with a short code. We read that code on every counted agent payment we can and group the money by it. Codes are shown as codes: the registry names no one, and we do not guess.

Agentic Finance Graph · Published 2026-10-11 · Measured 2026-10-11 19:04 UTC · updated hourly

$4,245,377counted agent payments carrying a Builder Code
15.0%of the counted value that has been read
56registered codes seen (64 distinct strings)
618agents whose payments carry a code
99.9%of counted value read for a code (59.7% of payments)

Measured 2026-10-11 19:04 UTC. Last transaction input read 2026-10-11 17:03 UTC. Value summed per row and per transaction agree: yes.

What a Builder Code is

An app that builds a transaction on Base can append a short tag to the end of the calldata: the code, its length, a schema byte and a fixed 16-byte marker (ERC-8021). Base's attribution reads the tag to credit the app. We read the same bytes on every counted agent payment we can, highest value first, and store the code on the row. The result is a way to group agent money by the app that sent it without guessing who the app is: the registry's public metadata names no one for most codes, so the codes are shown as codes. The one we can name is our own, bc_yqx4j4qp, attached to Desk plan payments since 11 October 2026.

A payment with no code was built by an app that did not append one, by a wallet, or by a script; absence says nothing about the app. Definition: pay.builder.attribution.v1. The document behind this page: /api/builders.

Registered codes, by counted value

Share is of all attributed value. "Agents" is the number of distinct paying agents under the code's largest variant; "payees" the distinct addresses paid; "top payee" the share of the code's value that went to its single largest payee (a code that pays one contract is one app's own flow, a code spread over many payees is a wallet or a marketplace). "Last 7 days" counts payments and value since a week ago at measurement time.

#codevaluesharepaymentsagentspayeestop payeefirst seenlast seenlast 7 days
1 bc_doqm1bei $3,849,697 90.7% 1,546 256 7 98.9% 2026-08-06 2026-10-11 158 · $405,095
2 bc_r9qzf8op $113,248 2.7% 555 111 86 16.0% 2026-03-08 2026-10-11 39 · $8,798
3 bc_scxiima9 +4 tags $110,173 2.6% 1,824 23 1 100.0% 2026-02-28 2026-10-11 91 · $3,883
4 bc_tpolfjho $53,840 1.3% 1,009 37 3 70.0% 2026-04-26 2026-09-28 –
5 bc_oad79faa $24,714 0.6% 140 9 14 44.1% 2026-02-26 2026-09-18 –
6 bc_r7yhais5 $20,023 0.5% 135 38 8 97.8% 2026-02-18 2026-10-07 4 · $21
7 bc_youcterf $12,087 0.3% 9 2 2 87.6% 2026-03-04 2026-07-05 –
8 bc_hm64q4jm $7,752 0.2% 115 37 2 73.9% 2026-10-06 2026-10-11 115 · $7,752
9 bc_pj3fz4w7 $5,512 0.1% 45 15 13 39.9% 2026-04-22 2026-09-13 –
10 bc_yidatp2g $5,226 0.1% 91 2 3 67.6% 2026-06-24 2026-10-10 6 · $332
11 bc_rd8s0npa $5,154 0.1% 176 39 2 98.7% 2026-05-06 2026-10-09 2 · $399
12 bc_t5chwytk $5,098 0.1% 73 21 24 29.9% 2026-09-16 2026-10-10 21 · $1,572
13 bc_nhvgty8t $4,599 0.1% 455 17 79 54.5% 2026-04-27 2026-10-11 25 · $192
14 bc_julg9gbq $4,304 0.1% 50 1 9 47.3% 2026-07-14 2026-10-04 –
15 bc_l4vqaa9e $2,786 0.1% 34 11 7 53.8% 2026-06-30 2026-09-27 –
16 bc_camnko4g $2,500 0.1% 1 1 1 100.0% 2026-02-26 2026-02-26 –
17 bc_u3g3444p $2,165 0.1% 18 8 1 100.0% 2026-06-24 2026-09-20 –
18 bc_92yf9czs $1,962 0.1% 22 6 4 94.2% 2026-07-06 2026-08-06 –
19 bc_4raffiaj $1,772 0.0% 20 12 3 92.8% 2026-07-15 2026-08-24 –
20 bc_rvetawt5 $1,612 0.0% 24 13 8 31.7% 2026-08-10 2026-10-07 4 · $308
21 bc_zgzef186 $1,231 0.0% 41 9 18 20.1% 2026-02-05 2026-08-23 –
22 bc_ctejvoov $900 0.0% 2 1 1 100.0% 2026-09-14 2026-09-24 –
23 bc_ipu1jetp $852 0.0% 10 2 4 69.7% 2026-03-10 2026-08-04 –
24 bc_480ypir7 $797 0.0% 60 10 8 52.4% 2026-06-17 2026-08-25 –
25 bc_avd0l2dd $778 0.0% 37 8 4 84.3% 2026-04-29 2026-05-29 –
26 bc_jnz0sz8z $655 0.0% 5 1 1 100.0% 2026-09-29 2026-10-10 3 · $313
27 bc_vf6cwk6h $615 0.0% 111 1 1 100.0% 2026-05-07 2026-08-11 –
28 bc_i85qhgg2 $532 0.0% 41 3 9 40.6% 2026-08-18 2026-10-06 7 · $88
29 bc_4iovi1yy $348 0.0% 16 1 7 39.2% 2026-07-17 2026-07-22 –
30 bc_b83zsgn0 $330 0.0% 6 4 2 53.9% 2026-09-12 2026-09-28 –
31 bc_nlhvsi52 $291 0.0% 13 8 4 52.0% 2026-05-09 2026-10-04 1 · $20
32 bc_9ixiqtey $205 0.0% 3 1 3 55.4% 2026-10-04 2026-10-09 3 · $205
33 bc_di3pknj1 $185 0.0% 37 2 1 100.0% 2026-04-27 2026-08-24 –
34 bc_exqaso18 $165 0.0% 3 3 1 100.0% 2026-09-08 2026-10-04 –
35 bc_onpde6mu $150 0.0% 10 3 4 64.7% 2026-09-17 2026-10-06 1 · $4
36 bc_5jcus08a $118 0.0% 23 6 14 25.4% 2026-03-02 2026-05-31 –
37 bc_nbn6qkni $110 0.0% 2 2 1 100.0% 2026-05-30 2026-06-10 –
38 bc_wn1fm95i $106 0.0% 14 2 5 58.5% 2026-09-08 2026-09-23 –
39 bc_kj26kx76 $100 0.0% 24 1 1 100.0% 2026-02-20 2026-02-23 –
40 bc_9y2g1ceu $94 0.0% 4 1 4 34.0% 2026-04-03 2026-08-27 –
41 bc_s3j5vf7h $80 0.0% 11 3 1 100.0% 2026-09-02 2026-09-06 –
42 bc_hzjzr9nv $80 0.0% 4 1 4 43.8% 2026-09-29 2026-10-06 1 · $35
43 bc_hr8binqm $79 0.0% 7 6 2 94.9% 2026-06-23 2026-09-21 –
44 bc_582md4io $78 0.0% 1 1 1 100.0% 2026-09-24 2026-09-24 –
45 bc_yhhltdnc $67 0.0% 13 1 4 33.2% 2026-09-28 2026-10-10 8 · $32
46 bc_60exfq1d $36 0.0% 2 2 2 70.9% 2026-05-26 2026-09-11 –
47 bc_p54y774f $21 0.0% 2 2 1 100.0% 2026-08-04 2026-08-28 –
48 bc_lfbayxwx $20 0.0% 5 2 1 100.0% 2026-09-10 2026-09-10 –
49 bc_qsurd2pa $20 0.0% 1 1 1 100.0% 2026-07-21 2026-07-21 –
50 bc_7qp6nz9w $18 0.0% 1 1 1 100.0% 2026-08-05 2026-08-05 –
51 bc_6b7scuim $13 0.0% 1 1 1 100.0% 2026-08-23 2026-08-23 –
52 bc_by8j7h2o $10 0.0% 1 1 1 100.0% 2026-10-09 2026-10-09 1 · $10
53 bc_q52is5ye $8 0.0% 1 1 1 100.0% 2026-09-07 2026-09-07 –
54 bc_e25smadr $5 0.0% 1 1 1 100.0% 2026-09-14 2026-09-14 –
55 bc_52j000yi $5 0.0% 1 1 1 100.0% 2026-05-02 2026-05-02 –
56 bc_0f6inod1 $4 0.0% 1 1 1 100.0% 2026-03-10 2026-03-10 –

Suffixes that are not a registered code

The marker was present but the bytes before it are not a bc_ code: another schema this reader does not decode, free text an app put there, or bytes that are not printable. They are counted and shown so the attributed total is not quietly smaller than what carries the marker.

suffixkindvaluepaymentsagentsfirst seenlast seen
schema:2 other schema $1,202 54 23 2026-06-17 2026-10-03
6a8780bbddcaae5e9cdba49b unregistered text $550 2 1 2026-08-29 2026-08-29
uULhrcTU9EDF unregistered text $271 5 4 2026-07-11 2026-09-07
unparsed unparsed $23 2 1 2026-07-10 2026-07-12

How to read this page

  • Coverage runs ahead by value. Transactions are read highest value first, so almost all counted value has been read while a large share of small payments has not. The two coverage figures above are both shown for that reason.
  • One code dominates. The largest code carries most of the attributed value and most of the agents; it is an app many agents pay through, not one agent. Which app it is, the registry does not say and we do not guess.
  • Codes with tags. ERC-8021 lets an app add its own sub-tags after the code (a wallet, a surface). They are folded into the registered code above and counted in the "+tags" note; the raw strings are in the document.
  • This is not a ranking of apps. Agents that pay through apps without a code are invisible here by construction. It is the attribution Base itself reads, measured on the counted agent-payment set.

Questions people actually ask

What is an ERC-8021 Builder Code?
A short identifier an application appends to the calldata of the transactions it builds, ending in a fixed 16-byte marker, so that Base can credit the app. Codes are registered in Base's Builder Codes registry; most registrations carry no public name.
Does a Builder Code tell you which agent or which payee is involved?
No. The code identifies the app that built the transaction. The agent is the wallet that paid and the payee is the address that received; both are read from the transfer itself. This page groups counted agent payments by the code found on their transaction.
Why is most agent money not attributed to any code?
Because most transactions carry no suffix: the wallet, script or app that built them did not append one. Absence of a code is not evidence of anything about the app. Of the counted value that has been read, about one dollar in seven carries a code.