Skip to main content
Two equivalent paths. Pick the one that matches how you’re integrating.

​
Option A — Console (browser wallet)

If you’ve got a browser wallet (MetaMask, Coinbase, Rabby, etc.):
  1. Open console.luxxon.dev
  2. Connect wallet → sign the SIWE challenge
  3. New workspace → pick a slug, name, and role (CONSUMER / SUPPLIER) → sign
  4. Mint key → save the plaintext (it’s shown once)
  5. Wallet → Top up pool → pick an amount and sign (first top-up is approve + deposit; subsequent ones are just deposit)
You now have an API key + a funded pool. Sessions debit from it automatically with zero further signatures. Skip to step 6 below to open sessions, or hand the key off to your agent.

​
Option B — curl / SDK

This is the wire protocol the SDK wraps. The flow:
You’ll need a wallet’s private key (or a passkey-backed Smart Wallet) to sign the SIWE challenge. Workspace creation is public — the signature itself is the auth.
The API base URL is https://api.luxxon.dev/api/v1. Examples below use $API — export API=https://api.luxxon.dev/api/v1.Today the platform runs on Base Sepolia testnet only — every API key is TEST-scoped. Mainnet (LIVE keys) lights up when we cut over. Hit GET /config for the active chain + contract addresses.

​
What you just did

You exercised every layer of the platform: SIWE wallet sign-in, public signature-authed workspace creation, wallet-session-gated key minting, scoped API-key calls, SpiceDB authorization (via ZedTokens), per-second pricing, on-chain pool deposit, the session lifecycle, and on-chain settlement composition — all without any SDK and with a single wallet signature beyond the workspace bootstrap.

​
Next