Web3 Wallet-Targeting Agent

Extracts qualified on-chain wallets across Ethereum/L2s, Solana, and Cardano by real criteria, scores and segments them, and reaches them through compliant channels — every count from a real data source, never invented.

View in marketplace Open dashboard

A precision Web3 growth engine that builds targeted wallet audiences from first-party on-chain data. It pulls wallets per chain (Dune for EVM, Helius for Solana, Blockfrost for Cardano), dedupes and scores them 0–100 by stacked criteria, segments to the highest-ROI audience, and delivers via opt-in on-chain messaging, cNFT tease-drops, or address-only CSV exports for web2 ad vendors. It is built compliance-first: only opt-in channels, no unsolicited DMs, and no fabricated numbers — every wallet count comes from a tool result.

What it does

The agent replaces broad, low-signal crypto ad spend with precision targeting. You tell it the project, chains, target communities (NFT collections, Cardano policies, or saved Dune query IDs), and qualification criteria (e.g. ETH balance + wallet age, Solana NFT holders, ADA Handle holders). It then extracts those wallets directly from on-chain providers, merges lists across chains while stacking matched criteria into a 0–100 qualification score, and segments the result by chain, score tier, or criterion. A campaign that would cost $30k+ as a broad X campaign can be run for under ~$1k.

Delivery is through compliant channels only: an address-only CSV for ad vendors (Slise/Hypelab), opt-in Dialect push to Solana subscribers who opted into the dApp, XMTP messaging, and Metaplex cNFT tease-drops (the latter two queued on a Railway worker since they can't run on Cloudflare). It enforces hard compliance rules — cNFT metadata must be informational with a live claim path and never a wallet-signing prompt, no unsolicited X/Twitter DMs, and no bought lists. It honors an autonomy setting: in Recommend mode it builds lists, segments, CSVs, and drafts and files CRM tasks for a human; in Autonomous mode it may broadcast and dispatch directly. Every run finishes with an executive report and a one-line summary, and usage is metered per wallets extracted and broadcasts sent.

How it works

Your Business

Extract per chain

Pulls wallets from real providers: web3_extract_evm (Dune saved queries for EVM), web3_extract_solana (Helius DAS for NFT/token holders), web3_extract_cardano (Blockfrost for policy holders / ADA Handles). Counts come only from tool results.

Merge, dedupe & score

web3_merge_lists combines lists across chains, removes duplicate wallets, and stacks matched criteria — a wallet hitting multiple criteria scores higher on a 0–100 scale.

Segment

web3_segment filters the master list to the highest-ROI audience by chain, minimum qualification score (e.g. ≥80), and/or criterion substring, returning a new list id plus its distribution.

Deliver via compliant channels

web3_export_csv produces an address-only CSV for ad vendors; web3_broadcast_dialect sends opt-in Solana push to subscribers (non-subscribers dropped); web3_dispatch queues XMTP messages or a Metaplex cNFT tease-drop on the Railway worker (clean metadata + live claim path).

Report & record

web3_make_report assembles a targeting report (audience by chain/criterion/score with charts, the channel plan, compliance notes, recommendations); top insights become CRM tasks via crm_create_task, and record_output writes lists built, wallets reached, channels used, and the report link.

Outcomes delivered

Setting it up — owner / admin

1
Subscribe and deploy
Subscribe to the Web3 Wallet-Targeting Agent and deploy it. Audiences and campaigns live in the Web3 workspace, and reports appear in the Web3 dashboard → Reports.
2
Connect data sources
Add API keys for the chains you target: Dune (EVM extraction), Helius (Solana), Blockfrost (Cardano). Each chain only activates once its key is present. Optionally configure Dialect (DIALECT_API_KEY/DIALECT_PROJECT_ID — register the dApp at dialect.to/integrate) for opt-in push.
3
Deploy the Railway web3-runner (only if using XMTP/cNFT)
Extraction, scoring, segmentation, CSV export, and Dialect push all run in-platform. XMTP messaging and Metaplex cNFT drops can't run on Cloudflare, so deploy the Railway web3-runner (set WEB3_RUNNER_URL + WEB3_DISPATCH_SECRET) and confirm the sender wallet is funded before any drop.
4
Fill the config fields
Set Project / token name (project_name), Chains (all / evm / solana / cardano), Target communities (collections, policies, or dune:IDs), Targeting criteria (e.g. ETH ≥0.05 + 6mo age), Channels (dialect, xmtp, cnft, ads_csv), Message / offer, and — for tease-drops — cNFT metadata URL (cnft_metadata_uri) plus an optional cNFT tree address override (cnft_tree_address; blank uses the platform's shared tree).
5
Set autonomy and schedule
Choose Autonomy: Recommend (build lists + drafts + CSVs, no sends) or Autonomous (broadcast + dispatch). Set the schedule for rolling snapshots, or leave it on-demand. Broadcasts only fire when you approve them or in Autonomous mode.
6
Do the first run
Open the Web3 workspace, set targets, and run Extract wallets (mode=extract) to confirm counts, or Run full campaign for the end-to-end loop. Mode-scoped runs exist for extract, segment, and broadcast, plus real-time chat over your targeting.

Using it day to day — your team

1
Define or refine the target
In the Web3 workspace, enter or adjust the target communities and criteria for the audience you want (e.g. holders of specific collections plus stakers above a balance threshold).
2
Run an extract or full campaign
Trigger Extract to build fresh wallet lists, or Run full campaign to extract, merge/score, segment, deliver, and report in one pass. Watch the run produce real, deduped counts per chain.
3
Review segments and the report
Inspect the deduped master list, the score distribution, and the segmented audience (e.g. score ≥80). The report shows audience by chain/criterion/score with charts, the channel plan, and compliance notes.
4
Use the outputs (Deliver)
Each wallet list has a Deliver action. For display ads: download the address-only CSV and upload it to your own Slise/Hypelab account — you build the ad creative, set the budget, and pay the network there (MNKI supplies only the audience; ads are served and reported on the network, not inside MNKI). For messaging: approve an opt-in Dialect push, or an XMTP message / cNFT tease-drop. In Recommend mode the agent drafts and files CRM tasks; clicking Deliver → Approve in the console is your explicit sign-off to send.
5
Chat with your targeting
Ask questions in real time (e.g. "how many wallets score ≥80 on Solana?"); chat is scoped to the list, segment, and CSV-export tools and computes answers from your real data, not estimates.

Use cases

Community-targeted airdrop tease

Extract holders of a set of NFT collections plus stakers, merge and score, then cNFT tease-drop the top segment with a live claim link.

Multi-chain eligibility lists

Pull EVM balance+age, Solana NFT/staker, and Cardano ADA-Handle wallets into one deduped master list for a snapshot or ad targeting.

Ad-vendor handoff

Segment to score ≥80 and export an address-only CSV to upload to Slise/Hypelab for on-chain-targeted display ads.

Opt-in Solana push campaign

Filter a list to Solana subscribers and send a compliant Dialect push announcing an offer — reaching only wallets that opted into the dApp.

What to expect

Targeted, deduped wallet lists across up to 3 chains with a 0–100 qualification score per wallet
Audience segments by chain / score tier / criterion, exported as vendor-ready address-only CSVs
Compliant on-chain outreach — opt-in Dialect/XMTP messages and cNFT tease-drops with a live claim path
An executive report (audience charts, channel plan, compliance notes, recommendations) plus CRM tasks for top actions
A precision campaign runnable for under ~$1k versus $30k+ for a broad X campaign

Metrics to watch

Unique wallets extracted per chain after dedupe (real provider counts)
Qualified audience size at each score tier (e.g. wallets scoring ≥80)
Dialect push recipients and sent counts (opt-in reach)
cNFT tease-drop claim/redemption rate via the live claim link
Cost per qualified wallet reached versus broad ad spend
Coverage of target communities/criteria that actually resolved to data

FAQ

Is this compliant, or is it spam?

Compliant by design. On-chain messaging via Dialect/XMTP only reaches users who opted into the dApp; cNFT tease-drops are informational with a live claim path and never a wallet-signing prompt. The agent will not send unsolicited X/Twitter DMs or use bought lists, and it verifies the sender wallet is funded before a drop.

Which chains and data sources does it use?

Ethereum and L2s via Dune (saved queries), Solana via Helius DAS, and Cardano via Blockfrost — all first-party REST. You provide the API key for each chain you target, and a chain only activates once its key is configured.

How are wallets scored?

On a 0–100 scale by criterion (balance, age, NFT holding, staking, dApp activity). Wallets matching multiple criteria stack to a higher score during the merge step. Every number is computed from real provider data — the agent is instructed never to invent or estimate counts.

Where do the display ads run, and who pays?

On the ad network, not inside MNKI. MNKI produces the targeted wallet CSV (the audience); you upload it to your own Slise or Hypelab account, build the creative, set the budget, and view performance there. You sign up with the ad network and pay it directly — MNKI doesn't broker the account or the ad spend, and you can't preview the ads inside MNKI.

Do I connect a wallet to pay gas?

No — there's no in-browser wallet connect. XMTP messages are free (no per-message gas); they need a sender identity configured on the Railway worker by your platform operator. cNFT tease-drops mint on Solana and need a funded Solana sender wallet, whose key also lives on the Railway worker — never entered in the dashboard.

What needs the Railway worker?

Only XMTP messaging and Metaplex cNFT drops, which can't run on Cloudflare Workers — these queue to a small Railway web3-runner (which holds the sender wallet) and return results via callback. Extraction, scoring, segmentation, CSV export, and Dialect push all run in-platform.

Will it broadcast without my approval?

Only in Autonomous mode. In the default Recommend mode it builds lists, segments, CSVs, and draft messages and files CRM tasks for a human to approve — it does not broadcast or dispatch.