For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Spree Studio is the partner-facing console for managing your branded loyalty program on Spree. From Studio you deploy your branded SP token, configure who can mint and hold it, run pSP campaigns, and manage on-chain authority.

Studio is self-serve. You deploy and operate your program without Spree intervention in the standard flow. The only inputs Spree provides are the supported chains and the executor service that auto-grants your wallet the operational roles when your deployment completes.

Where to Access

Production: studio.spree.finance.

Studio supports any RainbowKit-compatible wallet — MetaMask, Rainbow, WalletConnect, and the major hardware wallet integrations.

Studio vs Dashboard

Studio is the partner console — for your team to manage campaigns, treasury, whitelists, and roles.

Dashboard (dashboard.spree.finance) is the end-user-facing leaderboard view — for your customers to track their loyalty status and rewards. Different audience, different auth, separate URL. The rest of these docs cover Studio.

What's in This Section

Page
Purpose

What you need before signing in

Studio account access and the on-chain role model

One-paragraph description of each Studio page

First-time deploy walkthrough

Mint, transfer, redeem allowlists; partner delegation worked example

Granting and revoking on-chain roles

Run a campaign end to end

Same Operation, Three Ways

Every operational guide in this section ends each procedure with a small table showing the same operation via the Studio UI, the published TypeScript SDK (@spree-finance/spree-evm-sdk), and the HTTP API. The three paths produce the same on-chain transaction. Partners can drive operations from the dashboard, from a backend, or from automation infrastructure depending on what suits the team.

For SDK-level deep dives (full code samples, ABI references, role hex constants), see Developer Guides → Stable Points (SP). The Studio guides in this section walk through the same operations at the partner-operator level with SDK code as a parallel; the Developer Guides cover the SDK surface in depth.

Last updated