Welcome to Flywheel
The Believe Flywheel API transforms your project’s tokenomics into a self-reinforcing cycle where user actions automatically trigger tokens operations, creating sustainable engagement and value.How Flywheel Works
The Concept
Think of a flywheel as a perpetual motion machine for your token economy:- User performs action (buys product, views ad, engages with content)
- Your app calls Flywheel API with proof of the action
- Tokens are automatically burned/airdropped based on your configuration
- Token utility increases, encouraging more user actions
- Cycle continues, creating sustained engagement
Security & Transparency
- Multi-signature protection: Requires approval from both you and Believe
- Public vault address: Anyone can view and verify all transactions
- Proof-based actions: Every token operation includes verifiable proof data
- Daily limits: Configurable caps prevent excessive token movements
Funding Your Flywheel
Important: After registering your flywheel, you must fund the vault address with SOL and your project tokens before any actions can be executed.
Initial Funding (Required)
As the project owner, you’re responsible for:- SOL for transaction fees: Send SOL to cover Solana network fees
- Project tokens: Deposit tokens that will power your flywheel actions
- Minimum balances: Ensure sufficient funds for your planned operations
Community Funding (Optional)
The flywheel wallet address is public and transparent, enabling:- Community contributions: Anyone can send tokens to support your flywheel
- Transparent operations: All transactions are visible on Solana explorers
- Plug-and-play experience: Community members can “plug” tokens into your flywheel
- Shared incentives: More funding enables more rewards and engagement
Example Funding Strategy
API Endpoint Flow
Base URL:https://public.believe.app/v1/
The Flywheel API follows a specific sequence that ensures security and proper setup:
1. Register Flywheel (One-time Setup)
Platform: Believe Web App When to use: Only once per project (web app only)- Sets up your flywheel configuration
- Creates multisig wallet and vault address
- Generates API key with scopes
- Defines proof types for your project
2. Initialize Batch
Endpoint:POST https://public.believe.app/v1/flywheel/batch/init
When to use: Every time you want to execute flywheel actions
- Compile your pipelines into a batch transaction
- Get approval transaction to sign
- Validate all actions and proof data
3. Execute Batch
Endpoint:POST https://public.believe.app/v1/flywheel/batch/execute
When to use: After signing the approval transaction
- Process the approved batch
- Execute all pipeline actions
- Receive detailed execution results
Optional: Monitor Status
Endpoints:- GET https://public.believe.app/v1/flywheel/batch/{batchId}- Check specific batch
- GET https://public.believe.app/v1/flywheel/batch/current- Check current batch for tokens
Complete Example Walkthrough
Let’s walk through setting up a flywheel for an e-commerce store:Step 1: Register Your Flywheel
Registration is now done exclusively through the Believe web app:- Navigate to: https://believe.app/projects
- Create or select your project
- Configure your flywheel:
- Select your token
- Provide your wallet address (for signing transactions)
- Set daily limits (burn/airdrop amounts)
- Choose API scopes (burn, airdrop, etc.)
- Define proof types for your use cases
 
- Save configuration and receive your API key
- Note your vault address for funding
Step 2: Fund Your Vault
Step 3: Create and Execute Batches
When a customer makes a purchase:Best Practices
Funding Management
- Monitor balances: Check vault SOL and token levels regularly
- Set up alerts: Get notified when balances are low
- Community engagement: Share vault address for community support
- Emergency reserves: Keep extra funds for high-activity periods
Batch Operations
- Group related actions: Combine multiple user actions into single batches
- Monitor daily limits: Stay within your configured limits
- Handle failures gracefully: Check execution results and retry if needed
- Use proof data effectively: Include rich context for auditability
Security
- Keep wallet private: Never share your signing wallet private key
- Verify transactions: Always review approval transactions before signing
- Monitor vault activity: Watch for unexpected transactions
- Use appropriate scopes: Only request API key scopes you need
Next Steps
- Register your flywheel via the web app
- Fund your vault with SOL and project tokens
- Review Use Cases for specific implementation patterns
- Check Error Codes for troubleshooting
- Join the community to share experiences and get support
Need Help?
- Technical questions: Review the detailed endpoint documentation
- Business strategy: Explore the use cases for inspiration
- Troubleshooting: Check the error codes reference
- Community: Connect with other projects using Flywheel