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 implemented workflow includes launch preparation, bounded text jobs, prepaid-credit synchronisation, collected-fee advances, finalized fee reconciliation, and treasury signing and execution controls. Actual status comes from recorded work and verified receipts, not from a feature being present in the code.
| 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. Choose an available model; the worker uses that model when the brand can fund a run. |
| Text generation & activity feed | Implemented; funding required | Confirmed brand, supported model, allocated operating balance, durable job history, saved documents, and actual provider costs. |
| Provider credit synchronisation | Implemented; prepaid funds required | Provider purchase totals enter a finite USD pool once. Synchronisation blocks later manual deposit entries; it does not purchase provider credits. |
| Collected-fee AI funding | Implemented; both balances required | Fresh SOL/USD evidence, verified available operating fees, and existing prepaid USD support an atomic internal advance. No SOL exchange. |
| Brand funding isolation | Enforced | Each brand’s text work uses only its own collected operating fees. Manual sponsorship grants are disabled. |
| 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. Launch instructions and the fixed fee recipient are checked before requesting a transaction signature. |
| 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 indexing | Implemented; read-only | Supported finalized events and vault history, with gaps and unverified attribution kept unresolved. Indexing does not claim or spend funds. |
| Collected-fee accounting | Implemented; evidence required | Complete finalized history, shared-vault attribution, and lifetime 90% / 5% / 5% allocations. Remaining budgets subtract spending and reservations. |
| Treasury transaction controls | Implemented; activation and SOL required | One active action, exact budget reservation, protected signing, signed bytes saved before submission, and finalized confirmation or safe recovery. |
| Scheduled text work | Implemented; services and funding required | Minute-by-minute checks, bounded dispatch, database reservations, and receipt reconciliation. Uncertain paid requests are not automatically retried. |
| Checkout & fulfilment | Not active | Payments, a production provider, sample approvals, order tracking, refunds, and support. |
| Scheduled claims, buybacks & burns | Implemented; policy and funding required | Native Pump and AMM fee claims, atomic fixed-output purchases and burns, and first-use account setup within bounded rent. $BRAND’s 5% is held until its mint is configured. |
| AMM transaction capacity | Lookup table required | A configured Solana address lookup table for six fixed program accounts keeps supported transactions within the size limit. Creation needs treasury SOL. |
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.
Treasury submission requires BRAND_TREASURY_EXECUTION_ENABLED, a protected signer matching the configured treasury, verified native SOL backing, and any required lookup table. The worker reserves costs within the approved allocation before signing. A missing $BRAND mint keeps the platform burn allocation held; it does not redirect it to another coin.
Text work separately needs prepaid provider funds and an allocated brand balance. A collected-fee advance consumes its operating SOL allocation once without exchanging SOL or purchasing credits. The text worker cannot activate checkout, fulfil orders, run code, generate images, or publish to external sites.