nodius.xyz Trading Integration Packs

Runnable client examples for Solana bot developers. Use the existing nodius.xyz RPC, Signals WebSocket, trading builders and Yellowstone gRPC services with keys kept on your machine.

Choose a pack

Download all three packs, or choose one below.

TypeScript trading pack — launch monitoring, read-only inspection, guarded buy/sell construction and signed-transaction submission.
Python trading pack — the same workflow using the Python SDK and local solders signing.
Existing-bot migration pack — standard @solana/web3.js reads and a ready-to-run Yellowstone client, including a wallet transaction filter.

Each download includes source, dependency pins, tests and its own README. Archive checksums and inventory are available separately.

Framework integration

Using Solana Agent Kit? Add the nodius.xyz framework plugin to your existing agent instead of adapting a standalone CLI. It uses the framework wallet interface and adds namespaced methods/actions with host-controlled execution.

Start with observation

Extract the pack and follow its README to install dependencies.
Run its help and read-only planning commands first. Public pricing and recent launch previews can be inspected before buying credits.
Create an API key using the Quickstart. Buy credits with Solana USDC from the wallet associated with that account.
Set NODIUS_API_KEY in your local environment. Authenticated reads and subscribed streams consume credits.
Run a bounded launch monitor or migration check. These commands observe activity; they do not copy trades.

The packs do not automatically fund accounts or place trades. A Signals notification identifies a classified on-chain event; it is not a token recommendation.

Build, sign and confirm

The trading examples keep three operations distinct:

Build: executeSnipe or executeSell returns an unsigned transaction. A successful build is a charged operation, even if you choose not to submit the returned transaction.
Sign locally: the pack checks the transaction against its documented policy and uses a local wallet file. Keep a separate, limited-budget bot wallet. Never send a private key to an API or support channel.
Submit: sendAndConfirm accepts a signed transaction and returns its confirmation outcome. An uncertain response must be reconciled by transaction signature rather than treated as permission to create another trade.

Trade commands default to read-only planning. Execution requires explicit opt-in and limits. Follow the pack README for the exact flags, receipt handling, supported transaction checks and limits. These examples are integration scaffolding, not a trading strategy or an execution guarantee.

Pricing and budgets

Every pack reads live pricing. Buy construction pricing includes a build charge and a notional-based charge. Transaction submission has separate base and confirmed-outcome charges. Network fees, account rent and token-program fees are separate from service credits.

A fee estimate is not an atomic price lock. The server applies its current pricing when the request is admitted. Check the returned fee_credits as the total builder charge. A client check performed after construction can stop signing/submission; it cannot reverse a successful builder charge.

For a method without a published pre-build quote, the execution path requires explicit acknowledgement of the unquoted construction charge. Default planning remains read-only. A build failure refund is distinct from a trade that builds successfully but later fails to confirm.

Migrate an existing bot

Keep your trading logic and local signing. Replace only the infrastructure wiring:

JSON-RPC: https://rpc.nodius.xyz, with an X-Api-Key header.
Signals: wss://rpc.nodius.xyz/ws, authenticated using the SDK transport.
Yellowstone: TLS on grpc.nodius.xyz:443, with x-token metadata.

The migration pack contains a complete Yellowstone client and subscription request so you can run it without generating protocol stubs. Start with bounded slot streaming, then select a wallet transaction filter. For transaction reads, set maxSupportedTransactionVersion: 1.

See the API reference, Streaming Guide and Bot & Agent Guide for the service contracts.