Thundercore Authentication
ThunderCore's public API surface is unauthenticated. The JSON-RPC endpoints (mainnet and testnet, HTTP and WebSocket) and the BlockScout explorer API require no API key — access is controlled by rate limiting (10K/hr on the public mainnet endpoint) rather than credentials. Transaction submission is authorized cryptographically: transactions are signed with the sender's ECDSA (secp256k1) private key per the Ethereum transaction model, with EIP-155 chain-id replay protection (chain ID 108 mainnet / 18 testnet). For hosted key management and social-login auth, the docs point to Particle Network's MPC-based Auth Service as a partner offering.
ThunderCore secures its APIs with none and cryptographic-signature across 3 declared security schemes, 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.