Solana · Authentication Profile

Solana Authentication

Authentication

The Solana JSON-RPC OpenAPI declares no securitySchemes. The public cluster endpoints (api.mainnet-beta.solana.com, api.devnet.solana.com, api.testnet.solana.com) require no API key and no authentication — they are open, shared, rate-limited infrastructure not intended for production. Authenticated access is provided by third-party RPC providers (Helius, QuickNode, Triton, Alchemy, Syndica, GetBlock, etc.), which typically authenticate via an API key embedded in the request URL path/query or a header. Those keys are provider-specific and not part of the Solana protocol.

Solana declares 0 security scheme(s) across its OpenAPI definitions.

BlockchainCryptocurrencyWeb3DeFiTransactionsTokens
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: openapi/solana-rpc-api-openapi.yml
docs: https://solana.com/docs/rpc
description: >-
  The Solana JSON-RPC OpenAPI declares no securitySchemes. The public cluster endpoints
  (api.mainnet-beta.solana.com, api.devnet.solana.com, api.testnet.solana.com) require no API
  key and no authentication — they are open, shared, rate-limited infrastructure not intended
  for production. Authenticated access is provided by third-party RPC providers (Helius,
  QuickNode, Triton, Alchemy, Syndica, GetBlock, etc.), which typically authenticate via an
  API key embedded in the request URL path/query or a header. Those keys are provider-specific
  and not part of the Solana protocol.
summary:
  types: []
  api_key_in: []
  oauth2_flows: []
  public_endpoints_unauthenticated: true
schemes: []
notes:
  - Public RPC: no credentials; may return HTTP 429 (rate limited) / 403 (blocked).
  - Private RPC providers: bearer/API-key auth, out of scope for the core protocol.