Limits

What a crypto AI assistant can and cannot do

Every product page claims capability. This one lists the boundary, because a crypto assistant is only useful if you know exactly where it stops — and because a named gap is what separates an analysis from a sales pitch.

Updated 11 November 2026.

What it reads

Live market data — prices, volumes, pool depth and quotes — plus onchain reads on the chains it covers, token contract verdicts, protocol and yield data, and public news. Each read carries a source and a timestamp in the answer footer, and each answer names anything it could not fetch.

What it does with it

It turns the reads into one decision: act, wait, avoid or take profit, with the reason, a confidence level and the fact that would change the answer. It will also say when the honest answer is “wait” or “not enough information”.

What it will not do

It cannot sign a transaction, move funds, withdraw from a protocol or hold your keys. It cannot promise a return, and it does not place trades. Execution belongs to a wallet you control, with limits you sign.

Where the coverage stops

Not every chain is covered, holder-concentration data is not available today, and some feeds go down. In those cases the answer says so and lowers confidence rather than filling the hole. If a check you need is missing, that is a reason to check the explorer yourself, not a reason to trust a smoother sentence.

What the price buys

Answers and data reads, from one prepaid balance — no subscription, no plan tiers. The exact cost of each answer appears in its footer next to the sources, so you can see what a particular read cost before you ask for another.

What is still beta

The product is in public beta on Base. Surfaces marked coming soon are not live, and the trading surfaces are deliberately not part of the current pitch. Treat anything labelled beta as software that can change under you.

What can go wrong

• Reading a capability list as a guarantee — Every item is a way to be wrong. The list describes reads, not outcomes.
• Assuming “AI” means it can execute — Reading and signing are different permissions, and the second one should never be automatic.
• Ignoring the confidence field — It exists because the same format has to cover a well-sourced read and a thin one. Use it.

What this does not tell you

This page describes the product as it is today, not a roadmap. If a capability matters to a decision, verify it in the answer itself — the footer shows what was actually read, and the gaps section shows what was not.

Questions