Which API to use

The platform exposes five HTTP APIs. Picking the right one is mostly a question of who holds the keys and what you are reading.

API	Base URL	Purpose	Auth
Chain data	https://api.testnet.kriptonyx.com/api/v2	Blocks, transactions, addresses, tokens, logs	None
Platform REST	https://endpoint.testnet.kriptonyx.com	Managed wallets, tokens, pools, swaps	Password
Bridge	https://bridge.testnet.kriptonyx.com/api	Cross-chain swaps, webhooks	None / bearer
ICO	https://ico.testnet.kriptonyx.com/api	Launchpad	Wallet signature → JWT
Explorer services	https://explorer.testnet.kriptonyx.com/api	Accounts, watchlists, DeFi data	Bearer JWT

Choosing

Reading chain state. Use the chain data API for anything historical — it is indexed, so a query that would take thousands of JSON-RPC calls takes one. Use JSON-RPC directly for current state and for eth_call.

Signing your own transactions. Use JSON-RPC with ethers.js or viem. Your users keep their keys. This is the right default for anything user-facing.

Letting the platform hold keys. Use the Platform REST API. It stores an encrypted key per wallet and signs for you, authenticated by a password. Convenient for server-side integrations where there is no user wallet to prompt.

Moving assets across chains. Use the bridge API.

Reacting to events. Use WebSocket in a browser and webhooks on a server.

Common conventions

All five APIs speak JSON over HTTPS. Response shapes differ — the chain data API returns resources directly, the Platform REST API wraps everything in a { success, data } envelope — so see Errors and conventions.

Rate limits

The chain data API and the bridge API are not rate limited for normal use. The explorer services API limits authentication and public forms; see Explorer services API.

Be reasonable regardless: paginate rather than requesting everything, and cache what does not change.