Integrate against explicit security boundaries.
Public reads are simple. Every mutation is either retired, scoped, or governed. TLS verification is mandatory; examples never disable certificate validation.
https://valkx.net/api/v1X-VALKX-API-KEYPublic Reads
curl -sS https://valkx.net/api/v1/health curl -sS https://valkx.net/api/v1/chain/health curl -sS https://valkx.net/api/v1/coins curl -sS "https://valkx.net/api/v1/balance?symbol=ROCX&address=BIX..."
Read-Only Key
Self-service keys are constrained to:
health:read wallet:read market:read
Use the secure console to issue a session-scoped read key.
Mutation policy
| Operation | Status | Required control |
|---|---|---|
| Server wallet creation | Retired | Client-side Ed25519 only |
| Server private-key signing | Retired | Client-side signing |
| Mint / issuance request | Governed | asset:issue_request |
| NFT mint | Scoped | asset:nft_mint |
| NFT transfer | Scoped | asset:nft_transfer |
| Social writes | Scoped | social:write |
| Paper trading | Scoped | trade:paper |
| Live request | Scoped | trade:live_request |
| Live approval | Administrative | trade:live_approve |
FIX Connectivity
ValkX supports FIX 4.2/4.4 components, execution-report intake, BBO connectivity and reconciliation. Raw FIX is not an anonymous Internet endpoint. Production sessions are provisioned, allowlisted and will move to TLS/mTLS commissioning.
VIX Transaction v2
Core VIX secure transaction v2 uses Ed25519 signatures, nonce/expiry replay protection and public-key/address verification. Legacy server signing is retired.
Security Baseline
Always verify TLS. Never use curl -k. Never transmit wallet private keys to ValkX APIs. Treat elevated keys as production credentials and scope them narrowly.