Skip to content
Alchemy Logo

Admin API Overview

Programmatically manage Alchemy apps, networks, and usage.

The Admin API lets you manage Alchemy apps, list supported networks, and inspect compute unit usage without using the Alchemy Dashboard. Use it for automation, compliance, billing alerts, and enterprise workflows.

An App represents a single Alchemy project. You create an app, configure which networks it can access, and optionally restrict usage via allowlists. All app changes are applied immediately.

Usage data includes compute unit totals, estimated USD cost, billing period boundaries, and optional breakdowns by app, network, method, and request type.


Use this API to:

  • Create and delete apps
  • Update app metadata and configuration
  • Manage network and allowlist settings
  • Retrieve app details
  • Query supported networks
  • Retrieve account usage summaries for the current billing period and recent rolling windows
  • Query usage time series with hourly or daily granularity
  • Filter usage by app, network, method, and request type
  • Group usage results by request type, app, network, or method

Each request is authenticated and returns JSON responses.


All requests must include an access key. Grant only the permissions the caller needs:

  • App Management read or read and write, for apps and chains
  • Usage read (ADMIN_USAGE_READ), for Usage API endpoints

You can also authenticate usage requests with a dashboard user session token that has the viewer, developer, or admin role.

To create an access key:

  1. Go to the security tab in the Alchemy Dashboard
  2. Create a new access key
  3. Enable App Management and/or Usage with the permissions you need

Time-series query ranges are limited by plan:

PlanMaximum range
Free1 day
Pay as You Go7 days
Longer rangesContact sales

If you request a range longer than your plan supports, the API returns results for the allowed range.


The products field on the time series endpoint selects which meter to query.

If you omit products, the API uses SUPERNODE_CU. That meter is core RPC only. It does not include Enhanced APIs.

You can pass more than one product when those products share a unit. A request cannot mix CU products with SOLANA_GRPC_TB or SPONSORED_GAS.

For CU prices per method, see Compute Units.

products valueWhat it measuresUnit
SUPERNODE_CUCore RPC (default). Node methods, including eth_* and Solana JSON-RPC.CU
SUPERNODE_ENHANCED_CUEnhanced APIs: NFT, Token, Transfers, Portfolio, and Prices.CU
SOLANA_ARCHIVAL_CUSolana archival RPC. Historical Solana reads.CU
BLAST_CUBlast RPC.CU
SPONSORED_GASGas Manager sponsored transactions.sponsored gas
SOLANA_GRPC_TBSolana Yellowstone gRPC streams.TB

A dashboard-style CU query uses both core RPC and Enhanced APIs:

"products": ["SUPERNODE_CU", "SUPERNODE_ENHANCED_CU"]
Was this page helpful?