Developing With Carbium

Start building on Carbium with practical integration guides for wallets, swaps, RPC-backed flows, and production-safe application patterns.

Developing With Carbium

This section is for builders who already know what they want to ship and need the shortest path from idea to working integration.

Use it when you are building with Carbium's live surfaces today:

  • RPC for reads, writes, and transaction submission
  • Swap API for quotes and executable swap flows
  • Gasless flows for no-SOL onboarding paths
  • gRPC where transaction-heavy backends need real-time data

Choose your starting point

If you are building...Start hereThen go to
A wallet appcarbium-for-walletsexecuting-swaps
A trading bot or execution backendcarbium-for-trading-botssolana-grpc
A swap flow with backend signing boundariesexecuting-swapssending-unsigned-transactions-carbium-rpc
A backend service that needs RPC reads firstrpc-check-wallet-balanceyour-first-rpc-test-call
A no-SOL onboarding pathgasless-token-swapgasless-swaps
A routing or arbitrage workflowsolana-arbitrage-quote-enginecq1-routing-engine

What belongs in this section

Pages in this track should answer implementation questions, not just describe products:

  • how to wire Carbium into a real app flow
  • which Carbium surface fits a specific job
  • where keys, signing, and submission boundaries should live
  • what to validate before production traffic

If a page is mainly about product pricing, auth, or service comparison, it should usually stay in the product category instead of being nested here.

Recommended path for most teams

Most teams should start in this order:

  1. confirm the product surface they actually need
  2. build the smallest working flow
  3. move secrets and transaction submission to the backend
  4. add streaming, retries, or gasless behavior only where the app needs it

That keeps the docs flow practical instead of throwing every builder into the full product map at once.

Building on Solana with Carbium? Start with the guides in this section, then move to product-specific docs only when you need deeper surface detail.