Skip to main content
Get fast answers to the most common questions about Solana AI Gateway authentication, billing, endpoints, and MCP integration. Each answer is self-contained and links to related docs where available.
No. Solana AI Gateway uses standard Ed25519 signature verification via tweetnacl, so any wallet that can sign a hex challenge and return a base58 signature works. Phantom, Solflare, Backpack, and CLI tools are all compatible. The only requirement is that you control the private key for the wallet you claim the API key with.
Yes. Every paid endpoint accepts a network query parameter. Set it to devnet to route requests through the devnet cluster. If you omit the parameter, the gateway defaults to mainnet-beta. Public endpoints such as balance and blockhash also support devnet.
Paid endpoints return a 402 Payment Required response when your API key has no remaining free calls and its credit balance is too low to cover the per-call flat rate of 2,200,000 lamports. To continue using the gateway, send SOL to the gateway wallet (Brpc8HoPo1d3Uiyo7kbERnjMqwLJJmbWxtwxHxzar6DU) and claim a new key via POST /api/keys/claim.
You should not share your API key. The gateway debits credits per call, so anyone with your key can consume your balance. There is no multi-user or team-scoped key model. If you suspect a key has been exposed, rotate it immediately.
The gateway does not expose an explicit rotation endpoint. To rotate, send a new SOL top-up from the same wallet. The Helius webhook will create a fresh pending claim, and calling POST /api/keys/claim again will issue a new API key tied to the same wallet. You can then stop using the old key.
No. The gateway never sees or stores your private key. Authentication is based on a public-key signature: you sign a server-generated challenge locally, and the gateway verifies the signature against your wallet address using tweetnacl. Only the wallet address and a hashed API key are stored in the database.
Yes. If you omit the network query parameter on any endpoint, the gateway automatically routes the request to mainnet-beta. Explicitly pass ?network=devnet whenever you want to target the devnet cluster.
The gateway exposes a Model Context Protocol (MCP) manifest at GET /.well-known/mcp.json. The manifest lists the server name, version, capabilities, available tools, and the SSE endpoint (/mcp/sse). An MCP client fetches the manifest, opens an SSE connection to receive a sessionId, and then posts messages to POST /mcp/messages?sessionId=<id>. This lets LLM agents discover and invoke gateway tools without hardcoding endpoint URLs.