Data, API and what it costs
The rating is free and always will be. Credibility is the asset, and a rating nobody can read is worth nothing. What is priced is the layer underneath it: who else is in the trade, how a strategy is actually being run, and what it can absorb before its own edge is gone.
Reading the site
Everything that makes the ratings worth trusting: the vault and operator universe, consistency, the autonomy verdict with its evidence, and the methodology in full.
No account needed.
Everything on the site: cluster membership, behavioural signals, capacity, positions and exports. One seat, no API.
The Analyst surface plus fills, flows and depositor detail. For a team reading this daily.
What each one opens
Generated from the access checks themselves| Capability | Free $0 No account | Analyst $69.00/mo Before you allocate | Desk $119.00/mo Every day after |
|---|---|---|---|
| Ratings and coverage | |||
Agent-managed vault ratings Every vault we can see, with the evidence behind the autonomy verdict rather than a claim. | ✓ | ✓ | ✓ |
All vaults, operators, assets, platforms The full universe, not only the agent-managed part, because a crowd is measured against everyone in it. | ✓ | ✓ | ✓ |
30-day consistency Whether a strategy kept operating, not merely whether its return line stayed flat. | ✓ | ✓ | ✓ |
Methodology in full How every number is derived, including what it cannot see. A rating nobody can check is one nobody should trust. | ✓ | ✓ | ✓ |
| Deciding whether to allocate | |||
Crowding clusters and coverage Which strategies are quietly running the same book, and what share of an instrument they are between them. | · | ✓ | ✓ |
Who is in a crowded book The named vaults, which side, at what size and leverage. This is what turns "there is a risk" into a decision. | · | ✓ | ✓ |
Behavioural evidence The execution-timing signature behind an autonomy verdict, so you can disagree with it. | · | ✓ | ✓ |
Capacity How much capital a strategy can absorb before its own edge is eaten, with the working shown. | · | ✓ | ✓ |
Current exposure What each vault holds right now, by instrument and side. | · | ✓ | ✓ |
Gross-to-net waterfall Where a headline return goes before it reaches a depositor. | · | ✓ | ✓ |
| Monitoring what you hold | |||
Execution quality Taker share, fee rate and slippage from individual fills — the part of a result that is competence rather than market view, and the first thing to degrade when a strategy is scaled too far. | · | · | ✓ |
Deposit and withdrawal flows Money leaves before a return line turns. | · | · | ✓ |
Depositor concentration and timing How much of a vault is one wallet that could withdraw and reprice everyone else, and whether the best-timed wallets are already going. | · | · | ✓ |
| Taking it away with you | |||
CSV export — vaults, operators, crowding Every column as a file, including the operator cohort counts with closed vaults kept in. Cells a spreadsheet would execute are defused, since the names come from strangers on a public venue. | · | ✓ | ✓ |
Alerts Crowding past a share you choose, consistency falling, drawdown past a limit, or a strategy version changing. Each fires on the crossing and then stays quiet — an alert that repeats is one you would mute. | · | ✓ | ✓ |
This table is built from the same list the site reads when deciding what to show you, so it cannot promise something you would then be refused. It grows as the platform does. Everything listed is built — nothing here is a promise.
For machines
50,000 calls a month
Programmatic access to ratings, crowding and behaviour. 50,000 calls a month.
500,000 calls a month
The same surface at ten times the volume. For a product that reads this continuously.
Unmetered
Unmetered, including fills, flows and depositor data. Agents settling per query pay here too.
The API
One entitlement layer serves the web interface and REST clients alike, so a capability means the same thing everywhere and cannot drift between surfaces. Endpoints above your tier return 402 Payment Required naming the capability you need; a spent monthly allowance returns 429 and never touches the free surface.
GET /api/v1/plans prices and quotas, no key needed
GET /api/v1/account your balance, quota and deposit address
GET /api/v1/meta counts, capabilities, known limitations
GET /api/v1/vaults filter by chain, platform, agent-managed
GET /api/v1/vaults/{slug} metrics, NAV series, positions
GET /api/v1/vaults/{slug}/waterfall gross to net
GET /api/v1/vaults/{slug}/execution fills, taker share, fee rate
GET /api/v1/operators cohort summaries, survivors and failures
GET /api/v1/crowding clusters, coverage; members need a plan
GET /api/v1/assets instruments and who holds them
POST /api/v1/registry pre-register a strategy (free)
POST /api/v1/commit commit to a decision BEFORE executing
POST /api/v1/reveal reveal it afterwards; we match it on chain
GET /api/v1/attestation/{digest} whether the sequence is intactThe last three are the only thing here that ties a strategy to its trades. An agent posts a hash of its intent before placing an order — we cannot see the trade, because the hash covers a nonce too — then reveals it afterwards, and we check it against what appeared on chain. A gap in the sequence, a commitment never revealed, or a reveal matching nothing are all the same failure: a decision the record does not cover. Any of them voids the grade permanently, because the missing commitment would have had to be made before the trade.
Paying inside the request
A 402 carries your own deposit address. Send the transfer, then retry the same request with X-PAYMENT: base:0x<txHash> — we read that transaction on chain during the request and credit it, so there is no waiting for a background job. The reply carries X-Payment-Response saying what happened.
What we do not do is submit a payment for you. Canonical x402 has the server broadcast a signed authorisation, which needs a private key and a gas balance. We hold neither, and acquiring them would give up the property that makes a compromise of this server cost a list of addresses rather than anyone’s funds. Naming the limit beats claiming x402 support and sending an agent looking for an endpoint that is not there.
An agent never needs a browser. It can read /api/v1/plans unauthenticated, and /api/v1/account returns its own balance, quota and deposit address against an X-API-Key — so it can top itself up without a human clicking anything.
MCP — for assistants
Nine tools that let an assistant read ratings, crowding, execution quality and operator cohorts directly. It is a shell over the same REST API rather than a second implementation, so entitlements and quota are decided in one place — and a key is optional: without one every tool still answers with the free surface.
{
"mcpServers": {
"aspern": {
"command": "npx",
"args": ["-y", "tsx", "<path>/services/mcp/src/index.ts"],
"env": { "ASPERN_API_KEY": "asp_pro_…", "ASPERN_API_URL": "https://aspern.176-102-64-240.sslip.io/api" }
}
}
}When a tool hits a wall the assistant is told what kind of wall it is. A 402 carries the amount owed and a deposit address; a partly-answered response carries the arrears alongside it, so a missing field is never mistaken for a plan that needs upgrading.
Paying
USDC or USDT on Ethereum, Base, Arbitrum or Optimism, to an address issued to you alone — the same string on every one of those chains, so use whichever is cheapest. No card, no automatic renewal, no invoice chasing. Credit appears once the transfer is deep enough to be irreversible. Sign in to see yours.
What we will not do
- • No paid placement, sponsored rankings or advertising. A rating that can be bought is not a rating.
- • We do not trade on our own data.
- • We publish the limits of what we know. Anything held on a centralised exchange is invisible to us, so the concentration we show is a floor, never a ceiling.
Read the methodology before relying on any of it.