Pre-trade token brief
A sourced one-pager before you size a spot or perp idea: what the asset is, what can reprice it, and what you have not checked.
Starter · 8 min
22 playbooks · 7 categories
Research, alerts, journals, airdrop ops, memecoin screens, news digests, and multi-agent stacks. Each use case is a job you can rerun: who it is for, the workflow, the inputs, and the ways it fails.
Start here
A sourced one-pager before you size a spot or perp idea: what the asset is, what can reprice it, and what you have not checked.
Starter · 8 min
A reject-first screen for a fresh pair: mint and freeze authority, liquidity control, taxes, holder concentration, and unverified code.
Starter · 9 min
An overnight digest ranked by what can change your open risk, with a source grade on every item.
Starter · 7 min
Three roles — brief, alert, journal — with a human gate between them and no path from text to an order.
Advanced · 10 min
File by job
01
Bounded memos before you size anything.
4 playbooks
02
Thresholds you wrote down before the session.
4 playbooks
03
What you did, what it cost, and which rule broke.
3 playbooks
04
Public criteria, spend caps, and claim windows.
3 playbooks
05
Reject-first filters, then a product you can verify.
3 playbooks
06
What changed, graded, and tied to open risk.
2 playbooks
07
Several roles, one human gate, no order route.
3 playbooks
Definition
A use case on this desk is a concrete operating loop for one trading job. It names the person it is for, the job to be done, the steps, the inputs and outputs, the failure modes, and the generic tool types that can carry a step.
It is not a catalog of skills, plugins, or MCP servers, and it is not a leaderboard of products. If a step needs a market feed, the page says “market data API”. It does not invent a claim about a vendor.
The stop line is the same everywhere: the agent does not send orders, hold keys, or mark its own work approved.
Crypto Agent Desk is an anonymous public directory of use cases for crypto traders who run AI agents. Each page states the job, the workflow, the inputs and outputs, the ways the agent fails, and the kinds of tools that fit.
A use case starts from a trading job: research a token, fire a level alert, file a journal entry, screen a new pair. Tool types are named only as categories that can do a step. This site does not rank plugins, skills, or MCP servers.
No. Agents draft and watch. A human gate sits before any decision that risks capital. The pages do not include an order route, a signing key, or a signal service.
The project is anonymous. Pages are published under the Crypto Agent Desk name, without a personal byline, a city, or a wallet.