BIZ docs

The human launches. The AI operates within code-enforced authority. Activation requires real integrations and sufficient collected funding.

01Launching

One coin. One dedicated wallet.

LaunchCoin → lead agent → engine → optional initial buy → policy and review

Initial purchaseOptional; tokens go to your own connected wallet

Rewards100% of eligible creator-fee entitlement to the dedicated wallet, verified on chain

RecoverySame signed transaction is reconciled; never duplicate the mint or buy

New policyOperations-only, $0 new-engine spending, no buyback authority

Legacy businessesNo permission or wallet upgrades applied automatically

02Agents

Selected model. Narrow tools.

Configured modelsMuse (muse-spark-1.3) · Claude (claude-sonnet-5-5) · OpenAI (gpt-6-astra) · Grok (grok-4.7)

CallsReserve before provider requests; settle usage afterward

LimitsPer-business and global ceiling, concurrency and retry caps

SubstitutionNever silently switch a business's selected provider

AuthorityAI proposals cannot authorize arbitrary transfers, shell commands or permission changes

03Business engines

Eight categories, explicit prerequisites

Relay miningApproved always-on compute and billing; Verified NKN node software and registration; Isolated NKN-native identity and payout adapter Requirements →

Video-edge infrastructureCompatible CPU/GPU and bandwidth; Theta-native wallet and workload eligibility; Approved Linux/Docker deployment and billing Requirements →

Decentralized bandwidthNetwork-approved provider and region; Sentinel-native wallet and operating assets; Abuse controls, bandwidth caps and provider authorization Requirements →

Onchain monitoringAuthenticated Helius webhook lifecycle; Connected Telegram bot and verified customer destination; Prepaid subscriptions, deduplication and expiration enforcement Requirements →

Web3 security servicesGoPlus Solana API access and supported signal coverage; Paid report fulfilment and private delivery integration; Evidence-backed risk explanations; no safety guarantees Requirements →

Paid onchain APIsCompatible x402 V2 facilitator and /supported verification; Canonical Solana USDC settlement and replay protection; Metered offerings wired into the existing payment ledger Requirements →

Managed hostingExisting isolated Vercel deployment and budget; Customer ownership authorization and delivery terms; Customer hosting order integration; optional domain authorization Requirements →

Specialized compute miningSubnet-specific Bittensor registration and native signer, or eligible Nosana GPU host; Pinned miner software and workload compatibility; Approved compute billing and bounded registration funding Requirements →

04Finance

Funding, revenue and liabilities

Creator fundingCollected creator rewards are not customer sales

Earned salesRecognized only after delivery and refund obligations

Network payoutsNeed verified chain receipts; native assets stay separate

Protected balancesCustomer prepayments, refund obligations, expenses and reserves

InfrastructureProvisioned and metered under bounded, code-enforced authority

Full finance rules →

05Customers

Existing orders remain supported

Token requiredNo

PaymentSOL or canonical Solana USDC; immutable 15-minute quote

VerificationBackend verifies chain payment, recipient, reference, asset and finality

DeliveryPaid orders keep immutable terms and order-scoped funding

RefundsOriginal payer, original asset, capped to verified payment

New servicesSubscriptions, security reports and paid APIs (x402) are integrated and live

06Token operations

Own mint only

Buyback and burn is built end to end: policy-checked swaps through the official Jupiter routers, verified burns, independent chain verification and settled accounting — verified on chain. Transfers to a burn address are not burns.

Buyback readiness →

07Operational readiness

Not all configuration is implementation

DigitalOcean, Telegram, GoPlus, Helius and Jupiter are connected and live: paid security reports delivered, x402 paid-API settlement executed, cloud servers provisioned and destroyed with accounting, and a verified buyback-burn. Native mining registration (NKN) and the GPU engines are live under bounded authority.