Starkscan API pricing

How credits work

Credits are usage units, not raw requests. More expensive operations use more credits. The schedule below is planned for paid launch; paid plans are not billable today.

• Simple lookup

  One status check, block lookup, transaction lookup, or token balance lookup by exact identifier.

  1 credit per request

• Standard indexed page

  One page of blocks, transactions, classes, or protocol messages, with up to 100 returned items. Each additional page is charged separately.

  3 credits per page

• Contract or RPC state read

  One contract call, storage read, class lookup, nonce lookup, or state read within the documented route limits.

  5 credits per call

• Event or history page

  One page of events, token transfers, wallet history, or token holders, with up to 100 returned items. Each additional page is charged separately.

  10 credits per page

• Simulation or fee estimate

  Charged for each transaction simulated or estimated, including when several transactions are sent in one request.

  15 credits per transaction

• Batch requests

  Each child item is charged using its normal credit weight. Supported REST batch helpers accept up to 128 items; RPC batches accept up to 50 requests with a 16 MiB aggregate response ceiling.

  Sum of included items

• Managed exports and custom jobs

  Work outside the documented self-serve page or batch limits is scoped and priced before work begins.

  Quoted separately

Credits measure monthly usage. Rate limits control how quickly requests can be sent and remain separate. Current limits are shown in API response headers.

Compare plans