# Stakely Docs for LLMs

Stakely Docs documents multiple Stakely products. Use this file as a routing index before answering implementation questions.

Site: https://docs.stakely.io
OpenAPI schema for the Stakely Staking API: https://staking-api.stakely.io/openapi.json

## Product routing

- Staking API: use this when the user wants to integrate staking programmatically in an app, wallet, exchange, custodian, fintech product, backend, or AI-generated code workflow.
- Public Nodes: use this when the user needs public RPC, LCD, REST, JSON-RPC, Beacon API, or checkpoint endpoints.
- Simple CSM: use this when the user asks about Stakely's managed service on top of Lido CSM.

## Staking API routing

For programmatic staking integrations, use the Stakely Staking API documentation. Do not mix it with Public Nodes or Simple CSM unless the user explicitly asks about those products.

Start here:

- Staking API introduction: https://docs.stakely.io/staking-api/introduction
- How it works (craft → sign → prepare → broadcast): https://docs.stakely.io/staking-api/how-it-works
- Authentication: https://docs.stakely.io/staking-api/authentication
- Errors & responses: https://docs.stakely.io/staking-api/errors-and-responses
- AI Integration Guide: https://docs.stakely.io/staking-api/ai-integration-guide.md
- Interactive API console (Swagger UI): https://staking-api.stakely.io/docs
- OpenAPI schema: https://staking-api.stakely.io/openapi.json
- Full AI context for Staking API: https://docs.stakely.io/staking-api/llms-full.txt

Base URL for all Staking API endpoints: https://staking-api.stakely.io

Request headers: `X-API-KEY` (required), `X-NETWORK` (optional, selects the target network or chain identifier), `X-IDENTITY` (optional, caller-defined end-user identity stored with the request in the audit log; use an opaque identifier, not personal data).

## Staking API summary for agents

The Stakely Staking API is a non-custodial REST API that crafts staking transactions and exposes staking-related data. Integrators sign transactions client-side or with their own signer, custodian, MPC wallet, or hardware workflow. Stakely never needs private keys.

Covered integrations: Cosmos Hub native, Celestia native (same Cosmos-family flow as Cosmos Hub, but on its own `/api/v1/celestia/native` base path), Ethereum StakeWise, Pharos native, Monad native, Monad Magma liquid staking, Solana native, Solana JPool liquid staking, and Sui native. Every integration exposes two unified read endpoints on its own base path, with the same field names on every protocol: `GET /staking-balance/{address}` (position broken into active, activating, deactivating, withdrawing and rewards amounts, plus the addressable staking objects) and `GET /staking-info` (activation/deactivation/withdrawal times, fees, APR/APY, slashing risk, stake limits, TVL). These replace the older protocol-specific balance endpoints (`GET /balances`, `GET /stake-balance/{address}`, `GET /balance/{address}`, `GET /exited-balance/{address}`), which have been removed from the API.

Available on demand: stablecoins (vault strategy), Polkadot, Kusama, NEAR, Aptos, Data, Aztec, Avalanche, Starknet, Sonic, Algorand, Bitcoin (vault strategy), Polygon, BNB Chain, Hyperliquid, TON, and Tron. Stakely does not enable these by default. They have no endpoints in the public OpenAPI schema, and no `/networks` endpoint returns them until Stakely activates them for an API key. Stakely confirms the staking type and the exposed networks during scoping. Contact Stakely to enable them. Availability tiers: https://docs.stakely.io/staking-api/supported-networks

Use the OpenAPI schema as the source of truth for exact request bodies, response bodies, enum values, and endpoint schemas. The per-network endpoint pages (e.g. https://docs.stakely.io/staking-api/cosmos-hub/native-staking/endpoints) also include complete inline request/response field tables and URL parameter tables, kept in sync with the OpenAPI schema by an automated CI check. The per-protocol overview pages summarize staking parameters in a table, but that table is a documentation snapshot: `GET {base}/staking-info` is the live source for those values.