Documentation
Operate ArcLite with confidence.
Production notes for teams using ArcLite as a wallet-authenticated AI assistant on Solana. This documentation covers the app, API, authentication model, staking surfaces, and operational checks.
Getting started
Connect a Solana wallet, sign a challenge, and open the ArcLite workspace. The app uses wallet ownership for authentication and does not require a password account.
- Open app.arclite.ink
- Connect Phantom, Solflare, or Backpack
- Sign the login challenge
- Start a SolChat session
Wallet authentication
ArcLite issues a short-lived challenge, verifies the signed message, and returns a JWT for authenticated API calls.
- GET /v1/auth/challenge
- POST /v1/auth/verify
- Authorization: Bearer <token>
- Protected routes reject missing or invalid tokens
API reference
The production API is deployed separately from the web client. Client applications should use the configured HTTPS API origin, never localhost.
- GET /health
- GET /v1/status
- POST /v1/chat/completions
- GET /v1/wallet/balance?pubkey=<address>
Staking and access tiers
Staking routes expose account and tier state used by the app interface. Token economics and production balances remain controlled by the backend and Solana integrations.
- GET /v1/staking/balance
- POST /v1/staking/stake
- POST /v1/staking/withdraw
- Tier state is returned with authenticated profile data
Privacy and security
ArcLite is designed around wallet-authenticated access, limited CORS origins, structured errors, and server-side handling of secret keys.
- No client-side secrets
- Production-only CORS allowlist
- Structured API errors
- Private app routes are noindexed
Production status
Use the public health endpoint for uptime checks and the authenticated app for user workflows. Deployment providers should be connected to the main production branch.
- Website: arclite.ink
- Docs: docs.arclite.ink
- App: app.arclite.ink
- API: Render service with /health