Loading…
Loading…
Documentation
Fyxvo is a decentralized Solana RPC and relay infrastructure network live on devnet today. The managed network already supports 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.
Fyxvo is built as four cooperating layers. The on-chain Anchor program manages project accounts, treasury state, and operator-registry state. The API control plane handles wallet authentication, project management, funding, API keys, analytics, and alerts. The relay gateway prices and routes JSON-RPC traffic through the node pool. The worker handles async tasks such as billing rollups, notifications, digests, and background operational jobs.
Anchor program for project accounts, treasury state, and operator registry on Solana devnet.
Wallet auth, projects, funding, analytics, alerts, assistant workflows, and admin operations.
Scoped API key enforcement, request pricing, balance checks, upstream routing, and request logging.
Async billing rollups, notifications, digests, indexing, and background reliability tasks.
The live network still runs on managed infrastructure today. The protocol already exposes an operator registry on devnet, but the current production path does not yet onboard third-party operators directly into the live relay. That is the transition Fyxvo is preparing for next.
As that operator phase opens up, the intended fee split routes 80 percent of request fees to node operators, 10 percent to the protocol treasury, and 10 percent to the infrastructure fund. Operators will register through onboarding flows that connect infrastructure identity, performance visibility, and on-chain protocol state.
Managed devnet infrastructure proves the funded relay model, control plane, and on-chain project lifecycle with real users.
External operator onboarding expands the node pool beyond the team-managed setup and introduces operator-facing workflows.
A governed open network moves authority and routing participation closer to the protocol and away from one managed signer model.
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. USDC funding is live alongside SOL. Both assets are active.
POST https://api.fyxvo.com/v1/projects/:projectId/funding/prepare
Authorization: Bearer JWT
{
"asset": "USDC",
"amount": "2500000",
"funderWalletAddress": "BASE58_SOLANA_WALLET"
}
Response:
{
"item": {
"fundingRequestId": "uuid",
"transactionBase64": "base64-v0-transaction",
"recentBlockhash": "base58",
"lastValidBlockHeight": 123,
"asset": "USDC",
"amount": "2500000"
}
}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 charges `5,000` lamports for standard RPC, `20,000` lamports for the higher-cost 4x lane, 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
USDC funding is live alongside SOL. Both assets are active.
Default JSON-RPC lane for reads, status checks, and routine application traffic.
Compute-heavy lane
20,000 lamports
USDC funding is live alongside SOL. Both assets are active.
Higher-cost lane for the 4x methods that put extra load on the relay path.
Priority relay
20,000 lamports
USDC funding is live alongside SOL. Both assets are active.
Time-sensitive relay traffic for requests that need the priority lane.
The live gateway charges 5,000 lamports for standard RPC and 20,000 lamports for both priority relay and the higher-cost 4x lane. Volume discounts apply automatically. Once a project crosses 10 million monthly requests the rate drops by 10 percent, and at 100 million monthly requests the rate drops by 20 percent. No action is needed.
programId
protocolConfig
treasury
operatorRegistry
treasuryUsdcVault
managedOperatorWallet
managedOperatorAccount
protocolAuthority
pauseAuthority
Mainnet billing combines subscriptions, self-serve enterprise activation, and treasury-funded pay-per-request usage in one product flow. A project can start on a monthly plan, stay fully metered against its treasury, or move into an enterprise tier without waiting on manual pricing approval. Overage traffic is billed automatically at the published per-request rate, so funded usage keeps flowing without separate invoicing logic.
Subscription and enterprise tiers activate when the project treasury receives the matching monthly USDC funding amount on chain. Teams that prefer not to pre-commit to a monthly subscription can keep the same treasury-funded model and pay by request at the published standard and priority rates.
Volume discounts apply automatically. Once a project crosses 10 million monthly requests the rate drops by 10 percent. At 100 million monthly requests the rate drops by 20 percent. No action is needed.
Unused SOL is managed from the funding page in the dashboard. The current devnet deployment now exposes the withdrawal entry point there, validates ownership and available balance, and returns a clear response about whether the live protocol can complete the withdrawal.
29 USDC / month
A simple self-serve subscription for a solo developer who wants a funded project, scoped keys, analytics, and alerts without managing a large team workspace.
99 USDC / month
A collaborative plan for a product team that wants more traffic headroom, better analytics retention, webhook support, and shared workspace access.
299 USDC / month
A high-volume team plan for applications that need broad project access, full analytics retention, exports, and assistant support without leaving the self-serve flow.
No subscription
A treasury-funded option for teams that prefer to meter usage directly on chain instead of precommitting to a monthly subscription plan.
The pay-per-request lane currently publishes 50,000 lamports or 0.5 USDC for standard RPC and 200,000 lamports or 2 USDC for priority relay. The first automatic volume discount starts at 10 million monthly requests and the second starts at 100 million monthly requests.
The relay and control plane enforce request limits to protect shared infrastructure and maintain predictable latency for funded traffic. Standard relay, priority relay, and public form endpoints all have lane-specific or abuse-specific thresholds, and the gateway returns rate-limit headers so client applications can back off gracefully.
Developers can integrate with Fyxvo using the published JavaScript client instead of writing their own request wrapper. Install it with `npm install @fyxvo/sdk`, create a gateway client with your API key, and send either standard or priority relay requests with the same typed interface.
import { createFyxvoClient } from "@fyxvo/sdk";
const client = createFyxvoClient({
baseUrl: "https://rpc.fyxvo.com",
apiKey: "fyxvo_live_YOUR_KEY",
});
const health = await client.rpc({
jsonrpc: "2.0",
id: 1,
method: "getHealth",
params: [],
});
const priority = await client.priorityRpc({
jsonrpc: "2.0",
id: 2,
method: "sendTransaction",
params: ["BASE64_TX"],
});Resources
The SDK also includes a control-plane client for projects, API keys, analytics, funding preparation, and alerts.
Read the full package guide in the SDK README on GitHub.
If a request fails, start by checking wallet authentication, project funding state, API key scopes, and the live status page. Most integration issues come from expired JWTs, insufficient funded balance, a missing `priority:relay` scope, or sending requests to the wrong lane for the workload.
These routes are safe to call without a JWT or API key. Authenticated project and analytics routes require the wallet challenge flow first.