3 min read

Integration readiness

One view of what is available now and what is required to activate the full studio.

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.

CapabilityStatusAvailable or required
Public site & example brandsAvailableOriginal concept previews, brand directions, docs, and educational economics.
Coin identity & briefAvailableYour uploaded image, name, ticker, description, project category, AI brief, and required model selection.
Model catalogueAvailablePublic 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 feedImplemented; funding requiredConfirmed brand, supported model, allocated operating balance, durable job history, saved documents, and actual provider costs.
Provider credit synchronisationImplemented; prepaid funds requiredProvider purchase totals enter a finite USD pool once. Synchronisation blocks later manual deposit entries; it does not purchase provider credits.
Collected-fee AI fundingImplemented; both balances requiredFresh SOL/USD evidence, verified available operating fees, and existing prepaid USD support an atomic internal advance. No SOL exchange.
Brand funding isolationEnforcedEach brand’s text work uses only its own collected operating fees. Manual sponsorship grants are disabled.
Image & mockup generationNot activeA compatible image service, production-aware templates, storage, and review.
Launch records & public metadataImplemented; configuration requiredNeon database and public Blob storage for durable launch records, uploaded images, and metadata.
Signed wallet authenticationImplemented; configuration requiredPhantom message signature, server-verified one-use challenge, expiry, and wallet ownership checks.
Pump token launchImplemented; configuration requiredVerified 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 recipientSet by each launchOne BRAND treasury is recorded as creator. Trading fees accrue in its Pump creator vault; this is not a three-wallet split.
Creator fee indexingImplemented; read-onlySupported finalized events and vault history, with gaps and unverified attribution kept unresolved. Indexing does not claim or spend funds.
Collected-fee accountingImplemented; evidence requiredComplete finalized history, shared-vault attribution, and lifetime 90% / 5% / 5% allocations. Remaining budgets subtract spending and reservations.
Treasury transaction controlsImplemented; activation and SOL requiredOne active action, exact budget reservation, protected signing, signed bytes saved before submission, and finalized confirmation or safe recovery.
Scheduled text workImplemented; services and funding requiredMinute-by-minute checks, bounded dispatch, database reservations, and receipt reconciliation. Uncertain paid requests are not automatically retried.
Checkout & fulfilmentNot activePayments, a production provider, sample approvals, order tracking, refunds, and support.
Scheduled claims, buybacks & burnsImplemented; policy and funding requiredNative 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 capacityLookup table requiredA 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.

Provider references