How to use every part of the platform

Your first dataset, start to finish

From a token pair to a citable series you can put in a paper, in about five minutes.

Joining a class

What a student needs, which is almost nothing.

Setting up a department or team

Invites, seats, domain joining, and who can see what.

First API call

A key, a request, and the two conventions that will bite you.

The explorer, over the whole chain

Search by block, transaction, address or event signature; read any range of history a page at a time; take the filtered set as a CSV.

Decoded events

How a log's raw topics and data become named parameters, where the ABIs come from, and what the coverage figure measures.

How prices are computed

What a bar actually measures, where it comes from, and when it is absent.

Citations and reproducibility

Hashes for series and dataset queries, inline citations for single on-chain values, and what a library needs to cite them.

Research pages and notes

Projects, saved items, and the two levels of annotation.

The assistant on a page

Ask about the page you are writing; every figure comes from a tool, and nothing lands on the page until you choose.

Classroom assignments

Pinned datasets that cannot drift between students.

Aave health factors

What the panel contains, how it was validated, and what it refuses to answer.

Aave forks (Spark, and how a fork gets added)

What "the same pipeline" means, and what a fork's health panel does and does not cover.

Aave liquidations

Every LiquidationCall, with the bonus it actually paid.

Compound v3 absorptions

Why Comet has no liquidators, and whose dollars the figures are.

Morpho Blue and bad debt

Why the numbers here are per market, in the market's own tokens, and never added up.

MakerDAO collateral and vaults

Where the ledger's collateral types come from, how they are priced, and what the vault panel covers.

The event timeline

A dated, sourced registry for event studies.

Webhooks

Push delivery, signed, with the failure behaviour spelled out.

Using dfrds from an AI assistant

Connect Claude or any MCP client with the API key you already have.

Plans and entitlements

How access is decided, and why the role label has nothing to do with it.

Two-factor authentication

How the second factor works, what recovery codes are for, why staff can't opt out, and the rules around passwords, lockouts and email confirmation.

Account levels, and who can do what

The five levels on the platform — alpha, admin, partner, institution, user — and where each one's powers stop.

Your data

How to take everything you own out as a zip, what deleting your account removes and what it keeps, and how long discarded work, page history and export files are retained.

Single sign-on with your institution

SAML for universities and teams that run their own identity provider: what to give your IdP, what it must send back, testing the connection, and rotating certificates.

Managing partners

Creating a partner, setting the commercial terms, assigning who administers it, and what ending a partnership does and does not do.

Bundles and partner earnings

What a bundle is, how a partner's margin works, and why the institution never sees it.

Your partner console

What your dashboard shows, how earnings are counted, and where the boundary sits between your tenancy and their research.

Seats and buying more of them

How your allowance works, what happens when you run out, and what a top-up costs.

Billing and payments

How a subscription is bought and managed, what the emails are, and what happens when a payment fails.

Reviewing the platform as any level

Seeded demonstration accounts and the switcher, for walking each level's screens without holding an account of that type.

Downloading data

How the catalogue is organised, what the query manager does, and why some datasets cannot be exported together.

Alerts

What you can watch, where to set it, and why an alert fires exactly once.

Favourite pairs

Keeping the markets you care about one click away, from anywhere.

API reference

Every endpoint, its scope and its parameters, read from the OpenAPI document at render time.

Protocol coverage

Which lending protocols are tracked, what each page shows, and what is planned, from the registry.

Data dictionary

Every dataset's columns, units, and the conventions behind them.

How we decide what to publish

The rules behind every number on the platform.