Artax

Use the left navigation to move between review, account, pricing, and setup pages.

ReviewAccountAdd-on

Migration Guide

Keep devnet for testing. Launch on mainnet-beta cleanly.

Keep devnet for testing, create a separate mainnet-beta key for the same project, fund the live path with prepaid USDC, and keep cluster-specific API keys easy to understand.

Devnet testingSeparate mainnet-beta keyPrepaid USDCNo silent flip

Quick summary

  • Devnet remains the long-lived Artax sandbox for builders, partner QA, and post-launch regression work.
  • Mainnet-beta is the paid path for live traffic and real value movement.
  • The production API can serve devnet and mainnet-beta when the request names the environment explicitly.
  • Account identity and projects stay shared, while API keys remain cluster-bound.
  • Devnet usage stays included and rate-limited.
  • Mainnet-beta usage is the prepaid commercial path backed by real USDC funding.
  • Add a mainnet-beta key to the same project when the live path is ready.
  • Do not mutate a devnet key into a mainnet-beta key in place.
Open quickstartOpen developersOpen pricingOpen billing model

Ongoing testing

Devnet still has a job

  • Teams integrating Artax into their own devnet products still need a safe place to test before launch.
  • Builders can keep devnet alive after launch for QA, partner certification, regression testing, and AI-assisted testing.
  • Production keeps mainnet-beta funding, signer, and worker settings separate while allowing conservative devnet API-key testing through explicit request routing.
  • Devnet success is useful integration evidence, but production certification and launch approval require separate proof.
  • Rate limits and anti-abuse controls still apply, even though normal devnet use is included.

What this does not mean

A working devnet flow is strong integration evidence, but it is not the same thing as Artax platform launch approval, production certification, or a reason to skip the mainnet-beta cutover checklist.

Mainnet-beta migration checklist

Step 1

Freeze the devnet configuration that already works.

Step 2

Use the same Artax project workspace.

Step 3

Create a new mainnet-beta API key for that project instead of promoting the devnet key.

Step 4

Keep the devnet key available for QA and regressions.

Step 5

Fund the shared commercial balance with real USDC.

Step 6

Confirm the balance is available rather than merely pending.

Step 7

Switch your app to the mainnet-beta cluster and the mainnet-beta Artax key.

Step 8

Re-run supported review flows on mainnet-beta with production-safe wallets, recipients, and token mints.

Step 9

Check billing, dashboard usage, and cluster attribution before broad rollout.

Step 10

Keep the devnet project alive for ongoing testing and regressions.

What changes at cutover

  • The Solana cluster
  • The Artax API key
  • The funding posture
  • Any wallet, token-mint, or recipient values that were devnet-only
  • Your rollout expectations, because mainnet-beta is the paid path

Funding and billing differences

  • Devnet usage is included and rate-limited.
  • Mainnet-beta usage is prepaid and backed by real USDC.
  • Devnet usage should not consume the paid commercial path for normal sandbox testing.
  • Cluster attribution remains explicit even when the account-level commercial view is shared.

Keep devnet for testing

Use the sandbox for new feature validation, QA, regression checks, and automation validation without disturbing live traffic.

Open quickstart

Keep mainnet-beta for live traffic

Use the paid path for real users, live value movement, and live traffic.

Open quickstart

Add a live key

Keep the devnet key intact. Add a separate mainnet-beta key under the same project when the live path is ready.

Open quickstart

Quickstart

Follow the dashboard-backed builder sequence from sandbox bootstrap through live promotion.

Open quickstart

Developers

See the API, SDK, embedded review, and guided account setup path in one place.

Open developers

Pricing

Read the simple commercial posture for devnet included usage and paid mainnet-beta traffic.

Open pricing

Billing model

See exactly what is not billed, what stays included, and what becomes prepaid on the live path.

Open billing model

Projects

Manage one project workspace and create devnet or mainnet-beta keys from the API key surface.

Open projects

Add Funds

Use the USDC-only funding path when your mainnet-beta project is preparing for real traffic.

Open add-funds
Artax