Credits

Credits are prepaid and pay for what goes past the free reads.

Opening any token Blocktronics covers, its charts and the signal feed cost nothing.

Each paid action has one price, the same on the site, the MCP and a key's reads; Pricing lists them all.

Where the work grows with the token, so does the price: a new-token scan by the token's chain, age and transfers (never more than 250), all history by its days beyond the free 60 and their activity, and every API or MCP pull the same 2 credits (daily series: per token). The price is shown before you confirm. A readout and predictive analysis open one token for 24 hours; all history is unlocked once per token and kept as it grows.

A new dashboard counts wherever it's kept, in your browser or saved to your account: the first one you hold is free, then each costs credits. Editing one is free, a copy counts as a new one, deleting doesn't refund, and your Watchlist isn't counted.

The Blocktronics API (api.blocktronics.xyz, with a key from your account) serves exactly what you ask for, the same data the site shows: daily metrics, today's hours, a token's overview, or its readout at the site's 10 credits. Each answer comes at once, and a token that is behind is brought up to the hour behind it. A refusal, an error and a quote cost nothing; a token Blocktronics doesn't cover yet is quoted by its age, then added once at that price.

1. 1

   A new-token scan's price: each part rounded up, by the token's chain.

   credits = 1 + chain floor + age + activity + storage, at most 250
2. 2

   All history's price: the days before the free 60 and their transfers and swaps, the same on every chain.

   credits = 1 + ⌈extra days ÷ 60⌉ + ⌈√((transfers + swaps in them) ÷ 10,000)⌉
3. 3

   An API or MCP pull: one answer from a data tool, the same for every token; daily series are one pull per token.

   credits = 2 a pull; token_series 2 per token; the readout 10
4. 4

   Every answer says what it charged; your account page and GET /v1/account give the balance.

HighShape, not data

Many credits left: the balance on your account.

LowShape, not data

Few left: plan your next batch of reads around what remains.

RisingShape, not data

Credits were added to the balance.

FallingShape, not data

Reads drawing the balance down.

Evidence in the data, never advice

• In a query, a part that fails isn't charged, so the same request can cost different amounts on different tokens.
• A dashboard kept in your browser is still a new dashboard: past your first, it costs credits like one saved to your account.