Simple AI agents for anyone

Abstract

MindBlocks gives anyone a team of AI agents, with no code and no setup. You describe a job in a sentence, the way you would brief a person, and an agent takes it on: an email, a summary, a plan, a piece of research, a check on a token. Every account starts with nineteen ready-made agents on six desks, and you add your own: Claude drafts a new agent from one sentence, and you edit it like a document. Together they are your army.

The agents run on Anthropic’s Claude models. They do exact math, remember notes between runs, ask each other for help and work together in workflows, and the crypto desks read live market and on-chain data. Every run ends in a short brief that names its sources. Nothing touches money: trading agents can only paper trade, and every simulated order waits for your approval.

MindBlocks started as a crypto research desk, and its free tools are still for crypto. Instant check summarizes any wallet, transaction or token straight from public chain data, with no account and no AI, and free alerts say when a coin crosses a price, gas drops or a watched wallet moves. Agent runs are paid per run from prepaid credits in US dollars, at Anthropic’s cost times a markup of 2, by card or for 10% less in USDC or USDT. There is no MindBlocks token.

The problem

AI can do the work, but most people can’t put it to work

Most people meet AI as a chat box. It answers a question well, but a job takes more: you explain what you want, how you like it and what to check, every time, and the next conversation starts from zero. Tools that turn AI into agents, which do one job the same careful way every time, do exist, but they are built for developers: frameworks, API keys, prompt files and hosting.

Chatbots guess

Without live data, a chatbot answers from what it learned in training. Ask it for a price, a balance or this week’s news and it may give a plausible figure with no source and no date. For anything that changes, a confident wrong number is worse than none.

Crypto shows the problem at its sharpest

To check one token, a careful person opens a block explorer for the contract, a price site for supply and market cap, an exchange for the order book and a social feed for the news. The powers that hurt holders sit inside contract code: an owner who can mint, pause transfers, blacklist addresses, raise fees or swap in new code behind a proxy. Most people can’t read that code, so they take a stranger’s word for it, or paste an address into a site they don’t know, and a site that asks to connect a wallet, or for a recovery phrase, can empty that wallet. That is where MindBlocks started.

What a better tool does

It starts from what you already have: a sentence about the job, your notes, an address. It hands the job to an agent that does it the same way every time, reads live data where it matters, shows where every fact came from, says what it couldn’t check and never needs your keys. And anyone can make a new agent without writing code.

What MindBlocks is

MindBlocks is a web app where a team of AI agents works for one person. One ask box takes a job in words, or a wallet, transaction or token, and sends it to the right agent, or offers to build a new agent for it. Every new account starts with nineteen agents and five workflows, ready to run.

A campus of six desks

The team is drawn as a small voxel campus: six rooms around a central plaza, where the ask box lives. Agents work at their seats, walk over when they ask a teammate for help and gather in the plaza when a workflow starts.

• Writing: emails, posts, threads, updates and proposals.
• Research: summaries, explainers, tokens and news.
• Lab: the Chief of Staff, and the agents you build yourself.
• Trading desk: prices, charts and paper trades.
• On-chain: wallets, transactions and whale moves.
• Risk: red flags, limits and position sizes.

Nineteen ready-made agents

Five of them work on anything: the Writer, the Summarizer, the Explainer, the Thread Writer and the Chief of Staff. The rest come from MindBlocks’s start as a crypto desk. Use them as they are, edit them or build your own.

FMP stock data and Gmail drafts work only when the app runs inside Claude. On the website, the two agents that use them work without them and say what they couldn’t check.

Briefs with sources

Every run ends in a brief: a document, a bulleted brief, tables with a summary, a ready-to-send email or a checklist. When the agent has data tools, a line under the brief names the live sources it read, such as “Live data from Blockscout, CoinMarketCap”, or warns that it fetched none and figures may be out of date. A log shows every tool call with its input and output.

The home page’s example is the Scam Checker on the USDC contract: “Low scam risk. High issuer control.” It finds an upgradeable proxy, roles that can freeze addresses and pause transfers, approved minters and verified source code, all read from Blockscout.

Build your own agents

This is the heart of MindBlocks. Type a job into the ask box, such as “turn my weekly notes into a newsletter for our customers”, and choose Build an agent for this. Claude drafts the agent: a name, a one-line job, standing instructions, the inputs it asks you for, its tools, format, tone and speed. You read it like a document, change anything and run it. In the Lab you can also start from a template. Agents chain into workflows, and good agents and workflows can be shared to Community, where others add them to their own teams with one click.

Paper trading

Each account also has a paper portfolio with $100,000 of practice money. Trading agents place simulated orders there, and every order waits for your approval. No agent can place a real trade.

How it works

The router

The ask box reads what you type as you type, in your browser, and sorts it into one of five kinds:

• Transaction hash (0x and 64 hex characters): the Transaction Explainer.
• Address (0x and 40 hex characters): the Wallet Watcher, the Scam Checker or the Whale Watcher.
• ENS name (ending in .eth): the Wallet Watcher or the Whale Watcher.
• Coin (one word, or a $ cashtag): the Token Researcher, the Market Scout or the Chart Reader, with the Explainer first for a word that isn’t a known coin.
• A job or a question (anything else): Claude plans a workflow from your agents, drafts a new agent for the job, or the Explainer answers it simply. You choose which.

The router also picks up the chain from words such as “on base” or “arbitrum”, falls back to Ethereum and offers ten EVM chains in a picker. Pasting runs nothing. Pressing an action opens the agent with its inputs filled in and starts the run, and a question gets a plan for you to check first.

The agents

An agent is a short specification you can read and edit: a one-line job, a desk, standing instructions written the way a manager briefs a new hire, inputs with examples, tools, an output format, a tone and a speed. The built-in tools are a calculator, the date, a memory, the paper portfolio, paper orders and a way to ask a teammate.

A run sends Claude the agent’s brief with your inputs, today’s date and notes on how to call each data source. Every brief carries the same ground rules:

• fetch real data instead of guessing, and say which figure came from which tool;
• if a tool fails, carry on and say what couldn’t be checked;
• never present an invented price, balance or address as real;
• flag figures from the model’s own knowledge as possibly out of date;
• never ask for a recovery phrase or private key;
• give scenarios and risks, never instructions to buy or sell.

Claude works in rounds, up to ten per run. In each round it can call tools, which the app runs before the next round. When the brief is done, you can ask for changes and get a new version beside the old one, or hand the result to another agent. With the right tools, an agent can ask up to three teammates for help in a run and keep short notes between runs. Any action that writes, such as a paper order, stops for your approval.

Speeds map to models on the server: Fast is Claude Haiku 5.5, Balanced is Claude Sonnet 5.5 and Deep is Claude Opus 5.5. Five built-in agents run Fast, ten Balanced and four Deep. The agent editor shows each speed with its model and the price of a typical run, before you choose.

Workflows

A workflow is a set of steps, each run by one agent. A step can wait for others and receives their work; independent steps run side by side, two at a time. A step can pause for your review before its work is handed on. A final summary combines the results into one page of under 350 words and is told to add nothing that isn’t in the work. Five workflows come ready-made, from the Morning crypto brief to Token due diligence. For anything else, describe a goal: Claude plans one to six steps from your agents, and you check the plan before it runs.

The web

An agent with Web search among its tools searches the web and reads pages through Anthropic’s own web tools. On Balanced and Deep, the model filters what it finds with a little code before it reads it, so it reads only what matters; on Fast it uses the plain tools. A run makes up to five searches and reads up to five pages at a time, fewer when the balance can’t cover that many, and every search and page shows in its log. The answer ends with a list of the pages it cited and read, and each search adds $0.01 to the price of the run, times the markup.

Schedules

Any agent can run on a schedule: every day, every weekday or once a week, at a time in your own time zone, with the inputs you filled in. The site runs it itself, with nobody watching. It briefs the agent exactly the way the desk does, gives it the connectors, the web and the tools that don’t need the desk open (paper trading, Gmail and asking a teammate stay at the desk), and pays each round from your credits. The brief arrives in your alerts, as a notification, by email or on Telegram, and in your history; tapping it opens the run. A schedule that runs out of credits, or fails three times in a row, pauses itself and says so.

Teams

A team is a shared desk: the same agents, workflows, history, watchlist and schedules for everyone in it, and its own credits, which members move in from theirs. The owner invites people with links that work once and expire in a week. Each person switches between their own desk and their teams’ from the top of the desk, and every run made at a team’s desk is paid by the team, on a line that says who ran it. If two people change the same part of the desk at once, the later save is refused with a prompt to reload, instead of quietly overwriting the first.

The API

Keys made on the account page let people’s own tools run agents, read the free checks and see the balance. A key works at one desk, its runs are paid like any other and land in that desk’s history, and only a fingerprint of it is stored. The developer page explains the calls.

The data layer

Agents read three live sources through their public MCP servers, a standard interface for AI tools, on the site’s own keys:

• Crypto.com exchange: tickers, candles, order books and recent trades.
• CoinMarketCap: prices, market caps, volume, whole-market metrics, project profiles, news, narratives and technical indicators such as RSI and MACD.
• Blockscout: balances, tokens, transactions, transfers, ENS names, contract source, proxies and owners, on Ethereum, Base, Arbitrum One, OP Mainnet, Polygon PoS and other EVM chains.

Each agent carries only the tools its job needs. Identical market calls within a short window share one answer: 15 seconds for Crypto.com and 60 for CoinMarketCap. A source that is down never stops a run; the agent works without it and says what it couldn’t check.

Instant check

Instant check is the free tier: no account and no AI. Paste a wallet, ENS name, transaction hash, token contract or token symbol into the ask box on the home page, and within a second or two you get a read-only summary from public chain data:

• Wallet: native balances on Ethereum, Base, Arbitrum One, OP Mainnet and Polygon PoS; balances of major tokens such as USDC, USDT, DAI, WETH and WBTC, read through Multicall3; an estimated US dollar total from live prices; how many transactions it has sent; whether it is a contract; and its ENS name.
• Transaction: its chain, whether it succeeded, from and to, the value, the fee in the native coin and in dollars, the method called, the ERC-20 transfers it made, and when. An unlimited token approval is flagged.
• Token or contract: name, symbol, decimals and total supply; the price when listed; whether it is an upgradeable proxy, read from the EIP-1967 slots; and its owner, or that ownership was renounced. On Ethereum it also shows, from Blockscout, whether the source is verified, how many holders the token has and how much of the supply the ten largest hold. A contract that borrows a well-known symbol, such as a fake USDC, is called out.
• Gas now: live gas on the five chains, with what a transfer and a swap would cost.

The data comes from the chains’ RPC nodes, Crypto.com prices and Blockscout on Ethereum. Results are cached for about 30 to 60 seconds, and each visitor is rate-limited. A paste shaped like a private key or recovery phrase is never checked.

Each check has a shareable link, mindblocks.xyz/check/..., whose page carries the answer, so link previews can show it. Every check ends with an offer to have the right agent write the full brief: the Wallet Watcher for a wallet, the Transaction Explainer for a transaction, the Token Researcher for a token you name and the Scam Checker for a contract address. That brief is a paid run.

Watch and alerts

With a free account, the Alerts page keeps an eye on things between visits. Nothing in it uses AI.

• Wallets you watch. Up to 10 addresses or ENS names, each shown with what it holds across the five chains. With alerts on, the server looks at each one every few minutes and tells you when it sends a transaction or receives coins.
• Price alerts. A coin, a direction and a price. The server compares live Crypto.com prices every minute; an alert fires once when the price crosses, then rests until you switch it on again. An alert that would fire straight away is refused, with the price now.
• Gas alerts. A chain and a level in gwei, for when you want to send or swap for less.

Alerts go to the account’s feed, to every browser you allow (Web Push, encrypted so that only that browser can read it and signed with the site’s key, so a push service can neither read nor forge it) and, when the site sends email and your address is confirmed, by email. Each account can hold up to 20 price and gas alerts. Any free check of a wallet or a coin ends with a button to watch it or set an alert.

Metering

Credits are counted in micro-dollars, millionths of a dollar, so balances never drift through rounding. Each call to Claude, called a round, is metered on the server:

1. Hold. Before the round, the server sets aside the most it could cost: the input, estimated cautiously from the request’s size, plus every output token it is allowed, at Anthropic’s list price times the markup. If the balance can’t cover a full answer, the round gets a shorter one.
2. Run. The browser asks for a speed, never a model. The server picks the model, the system prompt and the output allowance, so a modified page can’t choose a dearer model or skip the meter.
3. Settle. Afterwards it prices the tokens Anthropic reports at list price, charges that times 2, rounded up to the micro-dollar, and returns the rest of the hold.
4. Record. A ledger line stores the charge, Anthropic’s cost, the model and the token counts. The rounds of one run share an ID, so the bill shows one line per run.

A hold is taken in a single database step that succeeds only if the balance covers it, so rounds started together can’t overspend. A hold left behind by a crash returns after about half an hour. The larger models opt into Anthropic’s refusal fallback, where another model can answer a declined request, billed at that model’s price.

The balance updates after every round, and the account page lists each run with its model, rounds and cost. Rounds use Anthropic’s prompt caching, and because the charge follows actual usage, the savings go to the user.

Payments

Credits come in top-ups of $5, $10, $20 or $50. A dollar paid by card buys a dollar of credit. A dollar paid in USDC or USDT buys more, because paying in stablecoins costs 10% less: $10 buys $11.11 of credits. The extra arrives with the payment, as a bonus line of its own in the account’s history.

Card. Stripe Checkout handles cards, and MindBlocks never sees a full card number. A webhook signed by Stripe credits each checkout once, even if Stripe sends it twice, and a refund takes the credits back.

Stablecoins. You pay in USDC or USDT from a wallet linked to your account. Before crediting, the server reads the transaction from the chain and checks that it succeeded, that it moved the real token (Circle’s contracts for USDC; every address in the code was read on-chain), that it paid the site’s receiving address from a linked wallet, and that it has enough confirmations:

Both coins use six decimals, so a coin’s smallest unit is exactly one micro-dollar of credit. Each transaction counts once. A background check every 20 seconds credits payments even if the page was closed, and a form takes a transaction hash for anything missed. The server knows only the receiving address and holds no private keys, so nothing on it can move funds.

Accounts

• Email. Passwords need at least 10 characters and are stored only as scrypt hashes that take 64 MiB of memory each, which makes mass guessing expensive. A wrong email takes as long to reject as a wrong password, and the reset form answers the same whether or not an account exists.
• Wallet. Sign-In with Ethereum, through Reown (WalletConnect, MetaMask, Coinbase Wallet and others). The server writes the message, which says that signing costs nothing and moves no funds. Each message works once, for ten minutes, and signatures from smart wallets such as Safe are checked on-chain.
• Sessions. A session lives in an HTTP-only cookie that page scripts can’t read. The database stores only a SHA-256 hash of it, so a copy of the database holds no usable sessions. Sessions last 30 days while in use, and changing a password signs out other devices.

Architecture

The website is a Node.js server built on Fastify, with PostgreSQL, behind Caddy for HTTPS and packaged with Docker. The desk runs in the browser: it builds each brief, runs the built-in tools and sends Claude one round at a time through the server, which meters it. Agents’ data calls go through the server too, on the site’s own keys. The same app also runs inside Claude as an artifact, and on a personal computer with the user’s own Anthropic key.

Safety and trust

MindBlocks reads and explains. It doesn’t hold anyone’s crypto, sign transactions or trade.

No custody, no signing

MindBlocks never asks for a recovery phrase or private key. Agents read blockchains through data services, and none of their tools can sign or send a transaction. Wallet sign-in signs a text message that moves nothing, and a stablecoin payment is an ordinary transfer that you approve in your own wallet.

Paper trading only

Agents can place only simulated orders, in the paper portfolio, inside three guardrails you set: the largest share of equity one position may take (10% by default), the most open positions (8) and the most agent orders in a day (20). Every order waits for your approval, which declines itself after 140 seconds. An order priced more than 20% away from the last fetched price is refused, short selling is off, and every rule runs again after you approve.

Secret scrubbing

Every text field in the desk is checked as you type. Recovery phrases (12 to 24 words from the 2,048-word BIP-39 list, allowing for a typo) and private keys in common formats (PEM blocks, xprv keys, Bitcoin WIF keys, Solana-style byte arrays and keystore files) are replaced with “[removed]” before they can be saved or sent. A bare 64-character hex string gets a warning instead, since a Bitcoin transaction ID looks the same. Every prompt is checked again before it leaves the page, and the run stops if anything slipped through.

Protection and rate limits

• Every page gets a fresh script nonce and a strict content security policy, and other sites can’t frame it.
• Writes to the API must carry the site’s own header and origin, which other websites can’t send.
• Rate limits cover 300 requests a minute per person or network address, 40 Claude rounds a minute and three at once per person, five sign-ups per network address per hour by default, and a lockout after 20 failed logins on one account within an hour. Cloudflare Turnstile can guard sign-up against bots.
• Logs leave out cookies, authorization headers and payment signatures.
• Admin access needs a listed email address that its owner has confirmed.
• The server admits only web and SSH traffic, refuses root logins over SSH and backs up the database every night, keeping the last 14 copies.

Where your data goes

Your agents, runs and portfolio are private to your account. Anthropic receives each run’s instructions, inputs and tool results, to produce the answer. Crypto.com, CoinMarketCap and Blockscout receive the lookups agents make, such as an address or a transaction hash, and Instant check sends what you paste to blockchain RPC nodes, Crypto.com and Blockscout, and the four-byte code of an unknown contract call to openchain.xyz to name it. Alert notifications pass through your browser’s own push service (Google’s, Mozilla’s or Apple’s), encrypted so that only your browser can read them. Stripe processes cards, Reown connects wallets, an email provider sends account emails, and Cloudflare carries the site’s traffic, serves the campus’s 3D library and runs the optional bot check.

MindBlocks sets one cookie, to keep you signed in, and no tracking or advertising cookies. It serves its own fonts, so pages don’t call out to Google. What you share to Community is visible to other users, under the name you chose. The Privacy Policy has the details.

Deleting your account

You can delete your account from the account page at any time. Your sessions, agents, workflows, runs, portfolio, shared items, linked wallets and any remaining credit go with it. Payment records stay, as accounting rules require, with no link to you.

Status in the open

A public status page checks accounts and data, the agents, live prices, the five chains, card and crypto payments and account emails, live. It says what is working and what is switched off, never how anything is set up. If the site has no Claude key, it runs as a preview, with credit sales switched off until agents can run.

Economics

Price per run

There is no subscription. Each run is paid from prepaid credits at the price of its agent’s model. A typical run reads about 20,000 tokens and writes about 2,500. The prices below are for a run of that size; longer runs cost more.

Unit economics

Every price is Anthropic’s list price for the tokens a run used, times a markup of 2. That gives a gross margin, before card fees, of

gross margin = 1 − 1/2

of every credit spent. The margin is the same on every run, whatever its size or speed, because cost and price move together: a run that uses fewer tokens costs the user less and the company less. The default markup was chosen to leave room for card fees and free credits.

Credits bought in stablecoins cost 10% less, so their margin is lower: at a markup of 2, 44% of what the buyer pays instead of 50%. Stablecoin payments carry no card fee, which covers part of the difference, and the discount gives people who already hold USDC or USDT a reason to pay that way.

Credits are prepaid, so a run is paid for before it starts, and holds mean no run can spend more than the balance behind it. Each ledger line stores both the charge and Anthropic’s cost, so the admin page shows charges against cost, in total and for the last 30 days.

Keeping the free tier cheap

• Alerts use no AI either. They compare prices and gas the site already reads, and look at watched wallets a few times an hour, so a free account costs next to nothing to keep.
• Instant check uses no AI. It costs almost nothing to serve: server time and public data calls, held down by caching and per-visitor rate limits. That is what lets the free tier work without an account.
• Prices are free. The watchlist, which holds up to 12 coins, and the home page’s price board read Crypto.com directly, with no Claude run. The board refreshes at most twice a minute for everyone.
• Free credits are bounded. Each account gets $0.50 once, only after confirming an email, so fresh wallets can’t farm them, and sign-ups are limited per network address. Because credits are spent at the marked-up price, $0.50 of free credit costs about $0.50 ÷ 2 in Claude usage.

The daily spending cap

The operator can cap what the whole site spends with Anthropic in 24 hours. Once spending over the past day reaches the cap, new rounds are refused with a “very busy” message until the rolling total drops below it again. The deployment guide also asks for a spending limit in Anthropic’s own console, as a second stop. Together they bound the worst case of a bug, a wave of abuse or a sudden rush.

Worked example: one month

This is a worked example, not a forecast. The numbers are chosen to show how the pieces fit together. None of them describes actual usage. Assumptions:

• 1,000 active accounts each make 80 agent runs in the month, about 18 a week: 80,000 runs.
• The mix is 20% Fast, 70% Balanced and 10% Deep.
• Every run is the typical size, with no caching discount.
• Claude is billed at the list prices in the code for the default models, which gives the per-run costs below.
• Visitors also make 100,000 Instant checks.

Users pay that cost times the markup, so the credits spent in the month come to $4,732 × 2, and the gross margin before card fees is 1 − 1/2 of that. The markup in force is 2. For illustration, the same month at three markups:

Each active account costs about $4.73 a month in Claude usage here. The 100,000 Instant checks add no Claude cost. If 500 new accounts confirm an email and spend all their free credits, that adds 500 × $0.50 ÷ 2 of Claude usage. Card fees, hosting and paid data plans come out of the gross margin and are not modeled here.

Credits, not a token

MindBlocks has no token, coin, airdrop or points of its own. Credits are prepaid usage priced in US dollars. They don’t expire while your account is open, can’t be transferred, have no cash value and are not an investment.

Dollar credits keep prices put: a Balanced run costs about 13¢ today and the same next week unless Anthropic’s rates or the markup change, and a price change never applies to runs already made. Paying by card needs no wallet, and people who already hold stablecoins pay 10% less.

Who it’s for

Anyone with work to hand off. Most of what follows needs no crypto at all.

Small businesses and busy teams

The Writer turns “from 1 December we open 8am to 6pm, and online orders are not affected” into a warm customer email, a shorter version and two other ways to open it, keeping every fact and adding none. The Summarizer turns a meeting’s notes into the decisions, the open questions and who does what by when. When a job comes up every week, such as a customer newsletter from the week’s notes, the owner builds an agent for it once and runs it in a minute.

Creators and project teams

Creators and teams use the Writing desk for words that have to be accurate. The Thread Writer turns “we shipped gasless swaps on Base and fees dropped 80% in the first week” into a thread of 5 to 8 posts, with two alternative hooks. The Holder Update Writer turns the week’s news into an announcement, an email and a short thread, including what didn’t go to plan. The Grant Proposal Writer turns project notes into a proposal with three to five milestones, each with a deliverable, a date and a payout.

Learners

The Explainer takes any idea at the level asked, from how compound interest works to how liquid staking tokens like stETH work, starting with a one-sentence answer and defining jargon as it goes. Instant check answers “what is this address?” for free, and before buying a token the Scam Checker answers “Can the owner freeze my tokens?” with checks marked Pass, Caution or Fail, each with its evidence.

Traders

Traders use the desk for the legwork around a decision. Give the Position Sizer a $10,000 account, 1% risk and a long SOL trade at 150, with a stop at 138 and targets at 165 and 180. It works out the size in coins and dollars, the loss if the stop hits and the reward-to-risk at each target, using the calculator for every number. The Market Scout writes a morning brief on BTC, ETH and SOL, and the Paper Trader tests a written strategy before any real money is involved.

On-chain researchers

Researchers start from an address or a hash. The Whale Watcher lists USDT transfers over $5 million on Ethereum in the last 24 hours, with the exchange and bridge labels Blockscout knows, and calls an address unlabeled instead of guessing its owner. The Wallet Watcher reads what vitalik.eth holds and its biggest moves in 30 days, and the Transaction Explainer turns a hash into who paid whom, for what and at what fee.

Growth

MindBlocks grows through five loops that are part of the product.

Any job, answered before sign-up

The home page’s ask box takes any job in words and shows, before sign-up, which agent would take it, or that a new one can be built for it. What was typed waits in the desk after sign-up, one click from the agent or from Build an agent for this.

Free checks lead to briefs

Instant check is free to use and nearly free to serve, so it can sit at the top of the funnel. Each check has its own link to post in a chat or a thread, with the answer in the link preview, and each ends with an offer of the full brief from the right agent. A visitor who signs up from the home page finds their paste waiting in the desk’s ask box, and a confirmed email adds $0.50 of credit for the first runs. The typical price of each speed is shown up front, so the first paid run is a small, known step.

Alerts bring people back

A free account adds alerts: a price crossing, cheap gas, a watched wallet moving. Each alert is a reason to come back, and each notification links to the free check of the thing that moved, one step from the agent who can explain it.

Agents people build, shared

Every agent someone builds can be shared. Anyone can share an agent or a workflow to Community. Others add it with one click, which copies it to their own team to change as they like, and the shared item carries its author’s chosen name.

Teams

Project teams work at a shared team desk: one set of agents and workflows, one history, schedules that deliver to the whole team, and credits the members put in together. Community still carries what a team wants to share with everyone else.

Roadmap

These are plans, not promises. Each one answers a gap in today’s product, and the order may change as we learn what people use.

Done since the first version

• Agents that read the web, with every page they use listed under their brief.
• Scheduled runs, delivered to the feed, notifications, email and Telegram.
• Team workspaces, with shared desks, history and credits.
• A public API, with keys per desk.
• Alerts on Telegram and inside the desk, and Useful marks that let the best shared agents rise in Community.
• Ready for several servers: request limits and background jobs can be shared through the database.

Next

• More chains. Instant check and stablecoin payments cover five chains, while agents already read other EVM chains through Blockscout. Checks and payments would follow.
• Alerts on a wallet’s tokens, not only its coins.
• Stock data and Gmail drafts on the website. Both work only inside Claude today.
• Workflows on a schedule. Single agents run on a schedule today; whole workflows would follow.

Later

• Mobile. The site can already be added to a phone’s home screen. A mobile app would bring alerts to your pocket.
• Roles inside teams, such as members who can run agents but not change them, or spend up to a limit.
• More than one server. The site can run as several copies today; spreading them across places would keep it up through an outage of one.

Risks and limits

AI can be wrong, and MindBlocks is not financial advice. Agents gather information, draft and explain. They can misread a document or a contract, miss a transfer or state a stale figure with confidence. Check what matters yourself before you act, and make your own decisions. No check can prove that a token is safe.

• Agents work with what they’re given. An agent without Web search works from your inputs, its tools, its notes and what Claude already knows, which may be out of date; its instructions tell it to say so when it matters. Pages on the web can be wrong too, which is why every brief that used them lists them.
• Runs nobody is watching. A scheduled run or one started through the API can’t ask you anything, so it makes sensible assumptions and lists them. Check its brief before you act on it, as with any other.
• Dependence on Anthropic. Every agent run uses Claude through Anthropic’s API. If Anthropic is down or slow, runs fail or wait, and the status page shows it. If Anthropic changes its prices or models, prices on MindBlocks change for future runs, never for runs already made.
• Dependence on data providers. Crypto.com, CoinMarketCap, Blockscout and public RPC nodes can be late, wrong or unavailable. When one fails, agents work without it and say what they couldn’t check, but the brief is thinner.
• Limits on free public data. Public RPC nodes and Blockscout’s free tier limit how often they can be called. Instant check stays inside those limits with caching and per-visitor rate limits, so at busy times a result may be up to a minute old, or you may be asked to wait.
• Paper trading only. Simulated orders fill at the price the agent fetched, with no fees, slippage or liquidity limits. A paper result says nothing certain about real trading.
• On-chain payments are final. Stablecoins sent on another network, in another coin or from a wallet that isn’t linked may not be credited, and blockchain transactions can’t be reversed.
• One server today. The site runs on a single server, so an outage there stops the service until it is back. It can already run as several copies sharing one database, for when it needs to.

Glossary

• Agent. A short specification that tells Claude how to do one job: a one-line job, standing instructions, the inputs it asks for, its tools, format, tone and speed. You can read and change every part.
• Confirmations. The number of blocks from the one that holds a transaction to the newest, counting both. Each new block makes the transaction harder to undo, so MindBlocks waits for a set number before crediting a payment.
• Credits. Prepaid usage in US dollars, counted in millionths of a dollar. Each run is paid from them at the price of the tokens it used.
• EIP-1967 proxy. An upgradeable contract built to the EIP-1967 standard. Users call the proxy, which runs code from a separate contract whose address sits in a fixed storage slot. Whoever controls the proxy can point it at new code, so reading that slot shows whether a contract can change.
• ENS. The Ethereum Name Service, which maps readable names such as vitalik.eth to addresses, and addresses back to names.
• Multicall3. A contract deployed at the same address on most EVM chains that bundles many read calls into one request. Instant check uses it to read many token balances at once.
• Paper trading. Trading with practice money. Orders are simulated and no real assets move.
• Run. One piece of work by one agent, from your inputs to its brief, in up to ten rounds with Claude.
• SIWE. Sign-In with Ethereum, a standard message that a wallet signs to prove it controls an address. Signing it costs nothing and moves no funds.
• Stablecoin. A token meant to hold a steady price, here one US dollar: USDC from Circle and USDT from Tether. MindBlocks takes both as payment.
• Workflow. Several agents working on one job: steps that run side by side or wait for each other, with an optional review, ending in one summary.