Your onchain workspace. And the engine behind it.

Manage wallets, launch and trade tokens in the Nuxus app, trade from the sites you already use with the browser extension, and build your own product on the same engine. Nuxus prepares every transaction; users sign in their own wallets.

Secured by

  • Solana
  • BNB Chain
  • Ethereum
  • Base
  • Robinhood Chain
Explore

Transaction flow

Interactive demo
Solana network
  1. Network
  2. Prepare
  3. Signin your wallet
  4. Broadcast

Step 1 of 4Pick a network to see what the engine can build on it.

// network  "solana:mainnet-beta", sent on every solana.* call
// engine   wss://engine.nuxus.io/ws
// signing  in your user's wallet, never on the engine
// Build methods on this network
//   solana.​transfer
//   solana.​associatedTokenAccount.​createIdempotent
//   solana.​pump.​swap
//   solana.​pump.​createToken
Built for

01 Platform

One engine. Three ways in.

Use the Nuxus app, trade from the browser extension, or build your own product on the engine that runs both.

Nuxus app

Every wallet, one workspace.

Create or import wallets, follow live balances, launch tokens and trade from one place. Nuxus prepares each transaction and your browser signs it.

Wallets
Create, import, rename and export, secured by Turnkey.
Launch
Launch Pump.fun tokens, or start from an existing token’s details with Vamp.
Tools
Token search, token accounts, live SOL, ETH and BNB prices and a Pump.fun migration calculator.
Open the app
Illustration of the Nuxus app wallet workspace, with sample wallets and balances.
Sample data

Browser extension

Trade from the sites you already use.

Pair the extension with your Nuxus account and trade Pump.fun tokens straight from Axiom and GMGN token pages with the Instant Trade panel.

Instant Trade
Buy and sell with preset sizes, signed in your wallet.
Sites
Axiom and GMGN token pages, for Pump.fun bonding-curve tokens.
Pairing
Approve it under Connections in the app, and disconnect it any time.
Illustration of the Nuxus extension’s Instant Trade panel beside a token page.
Sample data

For builders

The app and the extension run on the same platform your product can use.

02 Developers

Build on the engine behind Nuxus.

The Transaction Engine that powers the app and the extension is yours to integrate, with Live Data for everything your product needs in real time.

An unsigned transaction goes from your app to the engine to be built, to the user's wallet to be signed on their device, then back to the engine to be broadcast to Solana.
How a transfer moves

Transaction Engine

Build, sign where the user is, broadcast.

One WebSocket endpoint, engine.nuxus.io/ws. Send JSON-RPC 2.0, get back unsigned v0 transactions, and hand them to whatever wallet your users already trust. The engine never holds their keys.

Transport
WebSocket, JSON-RPC 2.0. HTTP for queries from servers.
Signing
In the user’s wallet, with any Solana v0 signer.
Broadcast
1–16 signed transactions per call, with bounded rebroadcast.
Engine documentation

Build

  • solana.transfer
  • solana.associatedTokenAccount.createIdempotent
  • solana.pump.swap
  • solana.pump.createToken

Query

  • solana.getNativeBalances
  • solana.getTokenBalances
  • solana.getTransfer
  • solana.pump.getSwap

Subscribe

  • solana.subscribeBalance
  • solana.subscribeTokenBalance
  • solana.signatureSubscribe
  • market.subscribePrices

Broadcast

  • solana.broadcastTransaction
Full method reference
Wallet trackers, market data and social sources converge into one stream to your app, metered in credits.
How Live Data flows

Live Data

Real-time data, metered in credits.

Stream balances, confirmations, prices, wallet activity and social sources to your app over one connection. Live Data runs on its own capacity, separate from the engine.

Streams
Balances, signature confirmations, prices, wallet trackers and social sources.
Billing
Credits per data type, apart from transaction fees.
How data credits work

Credit usage

Sample account
Credit balance48,200sample account
Used, last 14 days15,830across 3 data types
Data types3metered separately
Credits per day

Usage by data type

  • Wallet trackers7,280
  • Market data5,060
  • Social sources3,490
View daily values as a table
Sample daily credit usage
DayCredits
Day 1820
Day 2910
Day 3760
Day 41,040
Day 51,180
Day 6990
Day 7870
Day 81,210
Day 91,330
Day 101,150
Day 111,260
Day 121,420
Day 131,380
Day 141,510

03 Pricing

A fixed 0.25% for Nuxus. The rest is yours.

Two meters, kept apart: transactions pay a percentage of volume, and live data is paid for in credits.

Engine

Transaction fees

0.25%fixed Nuxus fee on fee-bearing transaction volume
Your fee
Set a total fee above 0.25% for your app. Everything above the Nuxus fee is yours.
Helper transactions
Run without a platform fee. Network fees and rent still apply.

Live Data

Data credits

Creditsdrawn down per data type, as data is delivered
Balance
Each account holds a credit balance, separate from transaction fees.
Engine
Building and broadcasting transactions never uses credits.

Partner revenue calculator

USD equivalent of fee-bearing transactions.

Minimum 0.25%, the fixed Nuxus fee.

You earn$2,5000.25% of volume, all yours
Nuxus receives$2,5000.25% of volume, fixed
Fee breakdown for $1,000,000 of monthly volume at a 0.50% total fee
ComponentRateAmount
Nuxus fee, fixed0.25%$2,500
Your markup, all yours0.25%$2,500
Total fee paid by users0.50%$5,000

Data creditsBilled separately for Live Data · not included above

How credits work

Transaction fees only. Network fees and rent are chain costs, not Nuxus fees.

04 SDK

Three calls from intent to chain.

The TypeScript SDK wraps the engine’s JSON-RPC methods with typed requests, subscriptions and automatic reconnection. It has no runtime dependencies.

  • Signing stays in your app, with a signer you provide.
  • Subscriptions resubscribe after a reconnect.
Read the quickstart in the docs
transfer.tsTypeScript
import { createClient } from '@nuxus/engine-sdk';
// Your signer, not part of the SDK: base64 unsigned v0 transaction
// in, { signedTransaction (base64), signature } out.
import { signWithYourWallet } from './your-signer';

const client = createClient({
  url: 'wss://engine.nuxus.io/ws',
});

// 1. Build: the engine returns unsigned v0 transactions.
const plan = await client.solana.transfer({
  network: 'solana:mainnet-beta',
  sourceAddresses: [userAddress],
  destinationAddresses: [recipient],
  amountLamports: '50000000',
});

// 2. Sign on the user's device. Keys never reach the engine.
const signed = await Promise.all(
  plan.transactions.map((tx) => signWithYourWallet(tx.unsignedTransaction)),
);

// 3. Broadcast the signed bytes.
const result = await client.solana.broadcastTransaction({
  network: plan.network,
  transactions: signed.map((s) => s.signedTransaction),
});

From first connection to a signed, broadcast transfer.

The docs cover the architecture, a connection example and every engine method.