Injective · Authentication Profile

Injective Authentication

Authentication

Injective's public read APIs (Chain LCD/REST, Tendermint RPC, and the Indexer gRPC/gRPC-web/REST + Chain Stream WebSocket) are open, permissionless endpoints that require no API key or OAuth token — they are rate-limited public infrastructure. WRITE access is not key-based: state changes are performed by broadcasting cryptographically signed transactions. Signing uses either native Cosmos secp256k1 (bech32 inj1... accounts) or Ethereum EIP-712 typed-data signing (0x... keys), with optional AuthZ grant delegation for session-based auto-signing.

Injective secures its APIs with none-public and signature-based-transactions across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyCryptoBlockchainDeFiTradingDerivativesWeb3Layer 1CosmosTokenizationPaymentsAI Agents
Methods: none-public, signature-based-transactions Schemes: 4 OAuth flows: API key in:

Security Schemes

public-read none
cosmos-signature transaction-signature
scheme: secp256k1 (Cosmos), bech32 address inj1...
eip712-signature transaction-signature
scheme: EIP-712 typed data, EVM address 0x...
authz-delegation on-chain-grant
scheme: Cosmos AuthZ MsgGrant for session-based/auto signing

Source

Authentication Profile

injective-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://docs.injective.network/developers-native/query-chain + query-indexer
summary:
  types: [none-public, signature-based-transactions]
  api_key_in: []
  oauth2_flows: []
description: >-
  Injective's public read APIs (Chain LCD/REST, Tendermint RPC, and the Indexer
  gRPC/gRPC-web/REST + Chain Stream WebSocket) are open, permissionless endpoints
  that require no API key or OAuth token — they are rate-limited public
  infrastructure. WRITE access is not key-based: state changes are performed by
  broadcasting cryptographically signed transactions. Signing uses either native
  Cosmos secp256k1 (bech32 inj1... accounts) or Ethereum EIP-712 typed-data signing
  (0x... keys), with optional AuthZ grant delegation for session-based auto-signing.
schemes:
- name: public-read
  type: none
  applies_to: [Chain LCD/REST, Tendermint RPC, Indexer gRPC/REST, Chain Stream WS]
  note: no credential required; rate-limited public sentry endpoints
- name: cosmos-signature
  type: transaction-signature
  scheme: secp256k1 (Cosmos), bech32 address inj1...
  applies_to: [transaction broadcast]
- name: eip712-signature
  type: transaction-signature
  scheme: EIP-712 typed data, EVM address 0x...
  applies_to: [transaction broadcast, Injective EVM]
- name: authz-delegation
  type: on-chain-grant
  scheme: Cosmos AuthZ MsgGrant for session-based/auto signing
  docs: https://github.com/InjectiveLabs/agent-skills (injective-trading-autosign)

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/injective-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.