TasteID × Blockchain.com · Design Partnership

Greater human
economic freedom.

TasteID is the consumer permission vault — HCP provides the rails for agents to query data and compensate humans with micropayments. Together, they turn June into a revenue source: external entities query June, blockchain.com gets paid, users get their cut.

Your data, your AI — and your cut. Every external query of June pays the users it learned from.

01The problem June has

June is a cost center

500K users, inference bills, wallet integration coming — and no revenue model. The intelligence June builds can't be sold, because the data behind it was never permissioned.

The data can't be productized

Privacy-first means June can't resell what it learns. But permissioned data is a product. Users who opt in want their data working — for a cut.

June + permissioned data = a queryable asset.
External entities pay to query June's intelligence.
Blockchain.com keeps the platform cut. Users get micropayments. Cost center becomes revenue line.

02What we bring — two pieces, one stack

TasteID — the permission vault

Plaid for consumer data, starting with music. GDPR full-history capture built — 86% more signal than API data alone. Users connect accounts, pull history, grant or revoke access per use. Music is the wedge; behavior is the moat.

HCP — the payment rails

When an external entity queries June, HCP attributes which users' data contributed and routes micropayments to them. ZK-verified: no operator can alter the recipient list. x402 moves the money; HCP decides who gets it.

The stack, in one line: the user permissions data in-wallet → June queries the vault → the user gets paid per query. Permission and payment, one system.

03How it works — June as a revenue source

1

Permission

One tap in-wallet. Users opt data into the vault — trading behavior, music taste, more. Revocable anytime.

→
2

June learns

Permissioned data makes June smarter. Personalization, insights, predictions — trained on data users chose to share.

→
3

External query

Developers, companies, agents query June's intelligence via API. Per-query pricing. A new product.

→
4

Everyone paid

Blockchain.com keeps the platform cut. HCP routes micropayments to the users whose data contributed.

June stops being a cost center. Every external query is revenue — for blockchain.com and for the users whose data made the answer possible. The first AI that shares its revenue with its training data.

04The scale — and the flywheel

44M confirmed walletsThe vault's distribution
44M
500K June usersAI-native, already engaged
500K
Wallet integration comingJune inside the wallet — vault beside it
1 surface
The flywheelMore users permission → smarter June → more external queriers → more revenue → more users permission. Cost center becomes profit center.
↻

June is the asset. The vault is the data. HCP is the payment.
One integration, a new revenue line.

05Design partnership — five decisions

What queriers buy first

Which June intelligence external entities pay for first — portfolio signals, market insights, behavioral patterns?

Query pricing

B2B per-query pricing. What developers and agents pay — and the platform margin blockchain.com keeps.

Attribution

Which users' data contributed to an answer — and their micropayment split. The HCP settlement design.

Permission UX

The one-tap moment in-wallet. Projected earnings preview: "wallets like yours earned ~$X last month."

Privacy guarantees

What queriers can never see. ZK proofs over raw data — answers out, source stays in.

June is the prototype. Every decision here ships in June first — then becomes the template for monetizing any AI on permissioned data. You're not integrating a feature; you're defining the revenue model for the category.

06The deal — first investor, design partner

$60K at $3M post-money

Tranche 1 terms. Blockchain.com comes in as first investor and design partner — equity in TasteID, plus the prototype that turns June into a revenue line:

Equity

$60K at $3M post — first money in, best terms anyone gets.

Revenue

June becomes a queryable asset. External entities pay per query — a new revenue source, not a cost center.

Position

First investor, first integration, first say on the standard every AI will eventually need.

You're not buying a feature.
You're founding the category — with equity.

07The close — four asks

1 · Close Friday: $60K at $3M

Terms with James. First money in sets the terms for everyone after.

2 · Design partnership

Scope the June prototype: data types, query patterns, payment UX.

3 · Counsel intro

Who you use for crypto counsel — align entities early.

4 · Investor intros — Base / CBV first

Warm intros to lead the round. Priority: Base and Coinbase Ventures to invest and co-author HCP alongside x402 — plus anyone else who should see this.