3 min read
Integration readiness
One view of what is available now and what is required to activate the full studio.
In this guide
Current release status
The real Pump launch workflow is implemented, with availability gated by the deployment’s service configuration. A disabled launch control means the required configuration or checks are not ready. The table distinguishes this launch workflow from the deferred AI, treasury, and commerce work.
| Capability | Status | Available or required |
|---|---|---|
| Public site & example brands | Available | Original concept previews, brand directions, docs, and educational economics. |
| Coin identity & brief | Available | Your uploaded image, name, ticker, description, project category, AI brief, and required model selection. |
| Model catalogue | Available | Public OpenRouter catalogue data, subject to provider availability. Selection records a preference. |
| Live AI generation & activity feed | Not active | Funded provider credentials, authenticated jobs, durable event and result storage, model and cost records, usage limits, and budget reservations. |
| Image & mockup generation | Not active | A compatible image service, production-aware templates, storage, and review. |
| Launch records & public metadata | Implemented; configuration required | Neon database and public Blob storage for durable launch records, uploaded images, and metadata. |
| Signed wallet authentication | Implemented; configuration required | Phantom message signature, server-verified one-use challenge, expiry, and wallet ownership checks. |
| Pump token launch | Implemented; configuration required | Verified Solana RPC network, server treasury public key, real simulation, user transaction signature, and server confirmation. An address lookup table may be needed to fit an atomic launch. |
| Creator fee recipient | Set by each launch | One BRAND treasury is recorded as creator. Trading fees accrue in its Pump creator vault; this is not a three-wallet split. |
| Creator fee claims & allocation | Deferred | Claim transactions, per-brand reconciliation, and the internal 90% / 5% / 5% ledger and spending controls. |
| Scheduled AI work | Not active | A durable job scheduler, approval rules, retries, and budget enforcement. |
| Checkout & fulfilment | Not active | Payments, a production provider, sample approvals, order tracking, refunds, and support. |
| Brand-coin & $BRAND buybacks and burns | Not active | Separate 5% allocations are defined. Verified token identities, execution controls, costs, and transaction reporting are still required. |
Activate one complete workflow at a time
A connection is ready only when its complete user workflow is reliable. Adding an API key alone does not establish account permissions, a spending policy, failure handling, or customer support. Each paid action needs a known owner, a cost limit, and a recorded outcome.
The current priority is launch preparation, wallet approval, and reliable on-chain confirmation. AI workers and fee claims come later, followed by reconciled allocations and verified buybacks and burns. A launch does not establish an automatic SOL-to-AI-credit bridge or activate commerce.