I taste it first.

Paste what a site wants you to sign. I try it, and tell you in plain words what it would do to your wallet.

On the menu

A claim linkthe airdrop someone sent you

A raw transactionbytes from a site or a bot

A signaturewhat did that thing I signed do?

Your pantrywho can already spend your tokens

The pantry

Some sites keep the right to spend your tokens long after you leave. Paste a wallet and see who still holds a key. This only reads public data.

$TASTER

Tasting stays free. Holding $TASTER buys more tastings a day, and that matters most to bots that check everything they sign.

Contract: not launched yet. Any address you see today is not ours.

Burn

Burn 50K $TASTER for 200 extra tastings today.

Opens when the token launches.

Creator fees

Half pays for the data and the model. Half buys $TASTER back and burns it.

Docs

How a verdict is made

Code makes the verdict, not AI. The taster reads the instructions, simulates the transaction on current chain state, and compares every writable account before and after. AI only writes the plain words at the end and cannot change the verdict.

Verdict	Means
Spit	It hands over control: a token account changes owner, your wallet goes to a program, or someone gets the right to spend everything you hold of a token.
Sip	Look closer: a limited approval, a durable nonce, you pay and get nothing back, a closed account that held tokens, or it could not be simulated.
Clean	Nothing bad was found. That is not a promise.

What a tasting cannot catch

A program can act differently when it really runs, because chain state moved or it can tell a simulation from the real thing.
A claim link can serve me one transaction and you another. If what your wallet shows differs from what I tasted, do not sign.
I can tell what a transaction does. I cannot tell if a token is worth anything, or if a deal is fair.
Accounts past the first 60 writable ones are not compared.

Giving me a transaction

Base64 or base58, signed or not. A bare message works too. For a claim link, add your wallet, so the link builds the transaction it would send you. Links that ask you to fill in a form are not supported yet.

For agents

If your agent signs anything it did not build itself, call taste_transaction first. Keys belong to a wallet, and limits follow its tier.

API key

Connect a wallet to make a key.

MCP tools: taste_transaction, what_happened, open_approvals. REST without a key: POST /v1/taste with { "input": "...", "wallet": "..." }, GET /v1/pantry/:wallet.

Roadmap

Three courses. No dates until the work is real.

Served

Verdicts from code and simulation
Plain words from AI
Claim links, transactions, signatures
The pantry
MCP for AI agents
Tiers and burn, at launch

In the kitchen

Revoke approvals from the pantry
Links with form fields
A browser extension that tastes on the spot
Known drainer addresses

Later courses

Wallet history: everything you ever approved
Taste bundles of transactions
Plain words in more languages
A taster for your own bot's rules

Questions

Does it replace my wallet's warning?

No, it is a second opinion. Read both.

Where do I get a transaction to paste?

Most people will use a claim link: right-click the button or copy the link someone sent you. For something already signed, paste its signature from any explorer. Bots and builders can pass raw transactions.

Is clean safe?

No. Clean means nothing bad was found. A tasting cannot see everything: read the Docs.

Do I have to connect a wallet?

No. Paste and taste. A wallet is only for keys, tiers and burning. Never paste a seed phrase or a private key anywhere, here included.

Do you keep what I paste?

The result is kept for 30 days so its link works. It is never listed anywhere.

Is this financial advice?

No. It says what a transaction does, not whether to make it.