Loading…
Loading…
Documentation
Fyxvo is a Solana devnet control plane with wallet authentication, on-chain project activation, funded relay usage, scoped API keys, analytics, alerts, and public trust surfaces.
01
Connect a wallet and sign the auth challenge.
02
Create a project and sign the activation transaction.
03
Prepare and verify SOL funding for the treasury.
04
Issue an API key with the scopes you need.
05
Route traffic through /rpc or /priority and monitor it from the workspace.
Authentication is a challenge-sign-verify flow. The client requests a wallet-specific message, signs it locally, and exchanges the detached signature for a JWT.
POST https://api.fyxvo.com/v1/auth/challenge
{
"walletAddress": "BASE58_SOLANA_WALLET"
}
Response:
{
"walletAddress": "BASE58_SOLANA_WALLET",
"nonce": "UUID",
"message": "Fyxvo Authentication\nWallet: BASE58_SOLANA_WALLET\nNonce: UUID\nBy signing this message you prove wallet ownership and start a JWT-backed session.\nNo private keys are ever transmitted to or stored by Fyxvo."
}POST https://api.fyxvo.com/v1/auth/verify
{
"walletAddress": "BASE58_SOLANA_WALLET",
"message": "exact challenge message",
"signature": "BASE58_SIGNATURE"
}
Response:
{
"token": "JWT",
"user": {
"id": "uuid",
"walletAddress": "BASE58_SOLANA_WALLET"
}
}Creating a project returns an activation transaction. Funding then follows a prepare, sign, and verify sequence so the on-chain treasury and workspace balance stay in sync.
POST https://api.fyxvo.com/v1/projects/:projectId/funding/prepare
Authorization: Bearer JWT
{
"asset": "SOL",
"amount": "1000000000",
"funderWalletAddress": "BASE58_SOLANA_WALLET"
}
Response:
{
"item": {
"fundingRequestId": "uuid",
"transactionBase64": "base64-v0-transaction",
"recentBlockhash": "base58",
"lastValidBlockHeight": 123
}
}After the funding transaction is signed, verify it through `POST /v1/projects/:projectId/funding/verify` with the funding request ID and the confirmed Solana signature.
Use `rpc.fyxvo.com/rpc` for standard JSON-RPC traffic and `rpc.fyxvo.com/priority` for time-sensitive relay traffic. Both paths require an API key. The priority lane also requires the `priority:relay` scope. The live gateway currently publishes `5,000` lamports for standard RPC and `20,000` lamports for priority relay.
curl https://rpc.fyxvo.com/rpc \
-H "Content-Type: application/json" \
-H "X-Api-Key: fyxvo_live_YOUR_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"getHealth","params":[]}';
curl https://rpc.fyxvo.com/priority \
-H "Content-Type: application/json" \
-H "X-Api-Key: fyxvo_live_YOUR_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"sendTransaction","params":["BASE64_TX"]}'API Explorer
Paste a JWT if you want to test authenticated routes. Public routes can be called without a token. Responses are shown below exactly as the live API returns them.
Response
Explore and the public project page system are opt-in. A project only appears on a public page after the owner opens project settings, enables the public page, assigns a public slug, and turns on discoverability for that workspace.
Once enabled, the public page can expose request volume, latency, success rate, and a public slug under `/p/[publicSlug]` without exposing private workspace data.
Standard RPC
5,000 lamports
Default lane for everyday JSON-RPC reads and standard gateway traffic.
Write and compute-heavy methods
20,000 lamports
Higher-cost traffic is billed at the live 4x lane when methods or writes put more pressure on upstream nodes.
Priority relay
20,000 lamports
Low-latency path for time-sensitive transaction submission with its own scope and routing lane.
The live gateway currently publishes 5,000 lamports for standard RPC and 20,000 lamports for both priority relay and the higher-cost 4x lane. Discounts apply automatically at one million requests per month for 20 percent off and at ten million requests per month for 40 percent off. There is no free tier in the live devnet deployment.
programId
protocolConfig
treasury
operatorRegistry
treasuryUsdcVault
protocolAuthority
pauseAuthority
These routes are safe to call without a JWT or API key. Authenticated project and analytics routes require the wallet challenge flow first.