Aurora Authentication
Aurora's public JSON-RPC endpoints (mainnet.aurora.dev and testnet.aurora.dev) are open and require no API key or bearer token; access control is performed at the protocol layer by cryptographic signing of transactions with an Ethereum-compatible private key (secp256k1), exactly as on Ethereum. Read (eth_call, eth_getBalance, etc.) calls are unauthenticated; state changes (eth_sendRawTransaction) require a client-signed transaction, not an HTTP credential. Dedicated per-project RPC endpoints provisioned through Aurora Cloud may carry their own API key.
Aurora secures its APIs with none across 1 declared security scheme, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.