Platform REST API

A managed-wallet API. The platform stores an encrypted key per wallet and signs on your behalf, so a client never handles private keys.

Base URL: https://endpoint.testnet.kriptonyx.com

Use it for server-side integrations where there is no user wallet to prompt. For anything user-facing, prefer letting users sign with their own keys.

Groups

Group	Covers
Wallets	Create, import, balances, transfers
Tokens	Deploy and inspect ERC-20s
Pools	Add and remove liquidity
Swaps	Execute trades

Authentication

Every route except the two registration routes requires the wallet password, accepted from — in order of preference:

Source	Notes
x-user-pwd header	Preferred. Never lands in access logs
user_pwd in the JSON body	POST routes
user_pwd query string	GET routes. Logged by nginx — avoid

There are two levels:

• User-level — proves you own the user_id.
• Wallet-level — proves you own a specific wallet address. Required by anything that spends funds.

curl -H "x-user-pwd: $PASSWORD" \
  "https://endpoint.testnet.kriptonyx.com/api/wallet/balance/0xYourAddress?user_id=alice"

Failures are deliberately vague

Authentication failures always return the same generic message, so the API does not reveal which user IDs or wallet addresses exist. A 401 does not tell you whether the account exists or the password was wrong.

Response envelope

{ "success": true,  "data": { } }
{ "success": false, "error": "Human-readable message" }

See Errors and conventions for status codes.

Health

curl -s https://endpoint.testnet.kriptonyx.com/health

{ "status": "ok", "timestamp": "2026-09-18T19:31:15.427Z",
  "chainId": "3009", "rpcConfigured": true }

No authentication. Useful as a liveness probe.