Skip to content
Arsenii Petrovich edited this page Feb 23, 2026 · 3 revisions

Purpose

Lists managed API endpoints per provider and plan/node type.

Storage path

references/offers/apis.csv - canonical source for all new offers (including offers only exist one network). listings/specific-networks/<network_name>/apis.csv - use !offer:<slug> references and only specify network-specific overrides when needed. listings/all-networks/apis.csv - use for entries that should propagate to all network JSON outputs.

When to add

  • Provider exposes a stable API for this chain.

Example

slug,provider,offer,actionButtons,planName,planType,historicalData,apiType,technology,chain,accessPrice,queryPrice,verifiedUptime,verifiedLatency,verifiedBlocksBehindAvg,uptimeSla,bandwidthSla,blocksBehindSla,supportSla,starred,trial,availableApis,limitations,securityImprovements,monitoringAndAnalytics,regions,additionalFeatures,address
algorand-mainnet-indexer,Algorand,"[""[Website](https://dev.algorand.co/nodes/installation/indexer-installation/#_top)"",""[Docs](https://developer.algorand.org/docs/get-details/indexer/)""]",,Free,Archive,Indexed Data,Algorand Indexer,mainnet,$0,$0(self-hosted open-source),,,,,,,,FALSE,FALSE,"[""REST API""]",,"[""Secure API keys"",""Encrypted endpoints""]","[""Real-time logging with SDKs""]","[""Global""]","[""Network agnostic (supports MainNet/TestNet/BetaNet)"",""Efficient data retrieval"",""Requires a separate binary download""]",null
blockdaemon-mainnet-dedicated,,!offer:blockdaemon-dedicated-recent-state,"[""[Website](https://www.blockdaemon.com/protocols/algorand)"",""[Docs](https://docs.blockdaemon.com/docs/algorand)""]",,,,,Algorand REST,mainnet,,,,,,,,,,,,,,,,,,

Columns

slug

Refer to Common Columns.

provider

Refer to Common Columns.

actionButtons

Refer to Common Columns.

planName

Refer to Common Columns.

planType

Refer to Common Columns.

historicalData

Whether this API supports querying information for the specific block. Blank: No Format: text Examples: Pruned, Archive, Partial Archive Tips:

  • Should be either Pruned or Archive. If API does not allow querying data up to block 0, but only to certain block in the past - Partial Archive may also be used as a value.
  • If the API is not connected with the blocks - keep Pruned (because you can't query to specific block in history then)

apiType

Type of the API in Web3. Blank: No Format: text Examples: RPC, Indexed Data, Custom Tips:

  • In the majority of the cases should be either RPC or Indexed Data. RPC represents most-used native API that fetches data directly from the blockchain nodes.
  • Custom is used only if provider provides only an API that is not standard for the RPC nodes of the network. For example - only an API to fetch balance without support for any other methods. Duplicate this information in the availableApis column.
  • Prefer Technology field over apiType to distinguish between specific custom API types.
  • Use other, more specific options only if it is necessary for developers to distinguish between more specific node types.

technology

Specific API type, name or category. Used to more clearly distinct between apiTypes Blank: Yes Format: text Examples: The Graph, Subsquidm EVM JSON-RPC

chain

Refer to Common Columns.

accessPrice

Monthly access price. May or may not be credited towards a monthly usage. Blank: Yes Format: text Examples: $0, $49, Custom Tips:

  • Provide information about discounts if available.

queryPrice

Price per 1M requests (or CUs). Blank: Yes Format: text Examples: $0, $0.40/1M CUs Tips:

  • Specify unit if not per request (e.g., CUs).

verifiedUptime, verifiedLatency, verifiedBlocksBehindAvg

Exists only in resulting JSONs. Used by the Chain.Love team to keep a history of verifired provider's performance, in accordance with Whitepaper. Can't be modified manually.

uptimeSla

Stated uptime guarantee. Blank: Yes Format: text Examples: 99.9%, 99.99% Tips:

  • Use percent format if applicable.

bandwidthSla

Stated bandwidth guarantee. Blank: Yes Format: text Examples: 1G/s, 10G/s

blocksBehindSla

Stated maximum lag in blocks. Blank: Yes Format: number Examples: 100, 200

supportSla

Stated support commitment. Blank: Yes Format: text Examples: 24h response, 1h response

starred

Refer to Common Columns.

trial

Refer to Common Columns.

availableApis

Namespaces/method groups. Blank: Yes Format: JSON list Examples: ["eth","web3","net","debug","trace"] Tips:

  • Use exceptions if helpful (e.g., "All except eth_call").

limitations

Rate limits/quotas. Blank: Yes Format: JSON list Examples: ["12M req/mo","40 rps"] Tips:

  • Express limits with unit and period (e.g., req/s, req/min, per month).

securityImprovements

Security features. Blank: Yes Format: JSON list Examples: ["DDoS Protection","IP Protection"]

monitoringAndAnalytics

Observability. Blank: Yes Format: JSON list Examples: ["Usage analytics"]

regions

Hosting regions.
Blank: Yes Format: JSON list Examples: ["US East","EU West"] Tips:

  • Use ["Global"] if specific region is unknown or not applicable.

additionalFeatures

Notable extra features. Blank: Yes Format: JSON list Examples: ["Cross-chain data replication"]

address

Owner address to claim provider Blank: Yes Format: 0x... Examples: 0x0fd8fd1dc8162148cb9413062fe6c6b144335dbf Tips:

  • Add your address to claim ownership (PR subject to KYC).

Clone this wiki locally