Recipe 38 of 65
Do a Hyperliquid builder's users come back? (retention)
/v1/hyperliquid/builders/{builder}/users?window=all gives every user's first and last fill with the builder and its active days; group them by first month for a retention view.
GET /v1/hyperliquid/builders/{builder}/users answers it, page by page. With window=all it lists every wallet that
ever traded through the builder, each with first_seen (its first fill through this builder), last_seen and active_days (the UTC days it
traded). Page through all of them, group the wallets by the month of first_seen, and per group count how many came
back: active_days of 2 or more, or a last_seen in the last 30 days. The full parameter list is on
Builder users.
Quick answer
Ask for every user over the whole history, 1,000 per page.
# every user of the builder over its whole history, 1,000 per page, with first and last fill and active days
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/builders/0xb84168cf3be63c6b8dad05ff5d755e97432ff80b/users?window=all&limit=1000"Example response
Captured from the live API on 2026-10-24 at 17:16 UTC with limit=3, all 3 rows.
The biggest user by volume first traded through this builder on 2026-02-13, was last seen on 2026-09-13 and traded on 128 days in between: retained for seven months, then gone. The second has traded on 249 days since 2025-08-11 and was active on the day of the capture. The third used it on 26 days and stopped in August.
{
"builder": "0xb84168cf3be63c6b8dad05ff5d755e97432ff80b",
"window": {
"window": "all",
"start": "2024-10-27T18:15:13+00:00",
"end": "2026-10-24T17:16:32.667000+00:00"
},
"sort": "volume",
"order": "desc",
"users": [
{
"wallet": "0x5a9312c32337a4501c0faa982163ff15e177a0ca",
"rank": 1,
"symbols": 18,
"fee_usd": 384873.3608090022,
"volume_usd": 752498029.646594,
"share_volume_usd": 752498029.646594,
"fills": 52850,
"fee_rate_bps": 5.114609549074242,
"fee_usd_node": 87925.9235949999,
"trader_fee_usd": 121289.78202299983,
"builder_routed_deployer_fee_usd": 2777.096762999995,
"closed_pnl_usd": -688126.7450509986,
"active_days": 128,
"crossed_fills": 52816,
"taker_pct": 99.9356669820246,
"first_seen": "2026-02-13T12:14:14+00:00",
"last_seen": "2026-09-13T22:22:17.561000+00:00"
},
{
"wallet": "0x1aa6a90f54dfaa5aa876b4fb34c7207340f9e60b",
"rank": 2,
"symbols": 15,
"fee_usd": 245067.89161200015,
"volume_usd": 490135837.04683053,
"share_volume_usd": 490135837.04683053,
"fills": 60846,
"fee_rate_bps": 4.999999450939656,
"fee_usd_node": 3506.048438,
"trader_fee_usd": 6633.874247000002,
"builder_routed_deployer_fee_usd": 0.0,
"closed_pnl_usd": 1871671.1893459954,
"active_days": 249,
"crossed_fills": 60846,
"taker_pct": 100.0,
"first_seen": "2025-08-11T00:51:00+00:00",
"last_seen": "2026-10-24T16:15:13.963000+00:00"
},
{
"wallet": "0x4c46f7295a1fe70d2ad04dfd5fa0e8007b17cba5",
"rank": 3,
"symbols": 5,
"fee_usd": 221950.55782,
"volume_usd": 443901129.33712804,
"share_volume_usd": 443901129.33712804,
"fills": 15658,
"fee_rate_bps": 4.9999998457187065,
"fee_usd_node": 221950.55782,
"trader_fee_usd": 371465.92603200173,
"builder_routed_deployer_fee_usd": 0.0,
"closed_pnl_usd": 305196.2409070009,
"active_days": 26,
"crossed_fills": 15616,
"taker_pct": 99.73176650913271,
"first_seen": "2026-04-14T12:49:55.516000+00:00",
"last_seen": "2026-08-19T16:35:54.577000+00:00"
}
],
"nextCursor": "eyJoaSI6IjIwMjYtMTAtMjRUMTc6MTY6MzIuNjY3MDAwKzAwOjAwIiwibG8iOiIyMDI0LTEwLTI3VDE4OjE1OjEzKzAwOjAwIiwiciI6MywidiI6NDQzOTAxMTI5LjMzNzEyODA0LCJ3IjoiMHg0YzQ2ZjcyOTVhMWZlNzBkMmFkMDRkZmQ1ZmEwZTgwMDdiMTdjYmE1In0"
}Variations
The next page. Follow nextCursor.
# NEXT is the previous response's nextCursor; the cursor pins the window, so the walk is one snapshot
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/builders/0xb84168cf3be63c6b8dad05ff5d755e97432ff80b/users?window=all&limit=1000&cursor=$NEXT"New or returning this week. List the last 7 days' users and look each one up in the all-time list: a first_seen before the 7 days means a
returning user.
# the wallets that traded through the builder in the last 7 days
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/builders/0xb84168cf3be63c6b8dad05ff5d755e97432ff80b/users?window=7d&limit=1000"Daily active users. The builder's daily series counts distinct users per day.
# distinct users per UTC day for the last 90 days
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/builders/0xb84168cf3be63c6b8dad05ff5d755e97432ff80b/series?bucket=1d&limit=90"Before you rely on it
No retention table, only first day, last day and active days
The API does not serve which months each wallet was active in, so a true cohort table (the share of a month's new
users still trading in month 2, 3, 4) cannot be read directly. Per wallet you get its first and last fill with the
builder and how many days it traded; with a recent window you can split new from returning users. A full
month-by-month table needs every fill from /builders/{builder}/fills, millions of rows for a big builder.
Daily users do not add up, and big builders are many pages
users in /series counts distinct wallets per bucket, so a month's sum counts a wallet once per active day. This
builder had 196,592 users over its lifetime: about 197 pages of 1,000. Older history was imported from the venue's
published files and starts at the builder's lifetime.first_seen on its profile, so no first_seen can be earlier.
Ask your agent
Connected to the Vike MCP server (https://vike.io/mcp) in Claude, ChatGPT or Cursor, ask it in plain words.
The hl_builders tool answers with view: users and window: all, at 1 credit a call.
For the Hyperliquid builder 0xb84168cf3be63c6b8dad05ff5d755e97432ff80b, list its top 50 users of all time with first seen, last seen and active days