Terms

HEY publishes research about what projects have built. It is not financial or investment advice, not a recommendation to buy, sell or hold anything, and not a prediction of any price.

HEY records what projects on Robinhood Chain ship — releases, deployments, code, contracts, documentation — each with its source and the time HEY read it. Activity status, Build Momentum, Still Building and the other research labels describe that record under the published methodology. Still Building means verified activity through a market drawdown HEY tracked. It is not a buy signal, and continued building says nothing about where a price will go.

Market figures — price, market cap, liquidity, volume — are context, shown with the time they were read. They can be late, incomplete or wrong, and they never decide a project’s status or its place in any ranking. A missing figure means HEY does not know it, not that it is zero.

Make your own decisions, and check anything that matters to you against its source.

HEY never holds your keys and never signs or submits a transaction for you. It builds no swap, asks for no token approval and executes no trade.

“View on Uniswap” opens Uniswap’s own site. Where HEY offers “Continue on Uniswap”, it opens Uniswap’s swap page with the amount you typed, and any swap is between you, your wallet and Uniswap’s interface.

Some optional features are paid in tokens: research requests, paid placements, bonds and funding a bounty. For these, HEY shows the amount and the treasury address, your wallet shows you the transfer, and you approve it in your wallet. A transfer on a blockchain cannot be reversed by HEY, so check the amount and the address before you sign. Bonds are held by HEY’s treasury and returned under the rule shown when you post one; refunds and bounty payouts are transfers HEY sends from its treasury.

• Reading HEY never requires an account or a wallet.
• You can sign in with a wallet — by signing a message that moves no funds and grants no approval — or with GitHub. Keep your wallet and your GitHub account secure: whoever controls them controls the HEY account.
• A wallet address belongs to one HEY account at a time.
• HEY may suspend an account or an API key that abuses the service, and says so where the key is refused.

Every fact HEY publishes carries where it came from and when HEY read it: a repository, a release, a contract on the chain, an explorer, a project’s own site, a market source. What a project says about itself is labelled self-reported and kept apart from what HEY verified. HEY can be wrong, and a source can be wrong; the source is linked so you can check.

Paid placements are labelled “Sponsored”. Payment, paid promotion and holding $HEY never change a project’s status, scores or organic ranking.

If you run a project, you can claim its page from the page itself (“Claim this project”, at /claim/<project>). You prove it one of four ways: a DNS record on the project’s domain, a file or meta tag on its website, administrator access to its GitHub repository or organisation, or a signature from the address that launched, owns or deployed its token contract.

Once claimed, you can post what you ship, edit the page’s description, and add a source or disown one listed as the project’s, from “Submit an update” (/project/<project>/update). Updates are labelled self-reported until a source backs them.

If you think something is wrong — on your project’s page or anyone else’s — write to [email protected] with the page and the source that shows the correct fact. There is no public dispute form yet. HEY keeps conflicting sources on record rather than silently overwriting one with the other.

The public API, the SDK and the hosted MCP server read the same public data as the site. Without a key, the API allows 120 requests a minute per address. The hosted MCP server allows 60 calls a minute per address, and each tool call is also counted against the API’s limits and your key, if you send one.

API keys are issued on your account page, one active key per account. A key is shown once and stored only as a hash. It reads the same public data with its own allowance, which follows your account’s holding tier:

• Free: 10,000 requests a month, 120 a minute.
• Holder (a linked wallet holding 10,000 $HEY or more): 50,000 a month, 600 a minute.
• Holder+ (100,000 $HEY or more): 250,000 a month, 1,200 a minute.

Past a limit, the API answers 429 with a retry-after header. The bulk reads answer keyed requests only.

When you use the API or the MCP server:

• cite HEY and link the source of what you republish, and keep the reading date with any market figure;
• don’t present HEY’s records as a recommendation to buy or sell, or as a verdict that a project is safe or unsafe;
• don’t get around the limits with many keys, accounts or addresses, or share a key to do so;
• don’t probe, overload or attack the service, or try to read anything that is not public.

HEY publishes no uptime commitment for the API or the MCP server. Status shows how fresh HEY’s data is.

$HEY is HEY Research Lab’s token on Robinhood Chain. HEY makes no promise about its price, its value or any return, and holding it earns no yield and no share of revenue. It never buys a ranking, a score, a status or positive coverage, and HEY researches its own project by the same rules as every other. Nothing on HEY is a signal to buy it.

On this deployment, $HEY is used for:

• Request Research. Pay in HEY for a place in the research queue; the research that follows runs the normal methodology.
• Lower HEY price for holding tiers. Accounts whose linked wallet reaches a holding tier pay less HEY for Request Research.
• Research bounties. Evidence work paid in HEY from the treasury: half at approval, half ninety days later if the evidence still stands.
• Bonds behind claims. A Scout claim, an owner update or a submission may carry a HEY bond, returned when the claim checks out.
• API key allowance by holding tier. An API key reads the same public data with a monthly allowance that follows the account's tier.
• Early access to research notes. New research notes open to holding tiers before they open to everyone.
• Advisory research-funding vote. Once a month, accounts with a linked wallet say where the treasury's research third goes, weighed by HEY held. Advisory: the founder decides and publishes.
• Research Terminal beta access. The Research Terminal beta admits invited or approved accounts whose linked wallet reaches the tier the console asks for, and accounts whose linked wallet held at least $500 worth of $HEY at the time of HEY's balance check, valued at HEY's own market reading.

Not open here: Labelled paid placements priced in HEY (planned); Monthly treasury ledger (planned); API and MCP credits paid in HEY (planned); Evidence challenges (planned).

The $HEY page explains each use and what $HEY can never buy.

Quotes are provided by the Uniswap Labs API. Using them is subject to Uniswap Labs’ Terms of Service and Privacy Policy. HEY sends Uniswap no reader address — every quote is asked with a fixed placeholder swapper — and stores no amount and no quote.

When a Research Terminal reader asks for a Uniswap quote, HEY sends Uniswap the token, the amount typed and a fixed placeholder in place of an address. Your address is never sent, and HEY stores no quote.

Uniswap Labs’ Terms of Service and Privacy Policy also govern anything you do on Uniswap’s own site after following a HEY link. Uniswap is a trademark of Uniswap Labs. HEY Research Lab is not affiliated with or endorsed by Uniswap Labs.

Signing in with GitHub is subject to GitHub’s terms; connecting a wallet goes through your wallet and WalletConnect; the Telegram bot runs on Telegram. Each of those services has its own terms. The Privacy page lists every service that receives data from HEY.

When you submit a project, post an update, hand in research or ask a question, send only what is accurate and yours to share. Owner updates and research notes are published with their labels. HEY may reject or remove a submission that is spam, impersonation, phishing, malware or a false claim; where a bond was posted, its published rule decides what happens to it.

When these terms change, their date changes. Questions: [email protected].