Build on BotGentz
Ten paths, one platform — browser apps and AI agents, extensions, hardware SDK integrations, APIs, content, ad tools, e-commerce, creator tooling, voice control and learning apps, all built on the same infrastructure already running BotSurf.
As the ecosystem matures, building on BotGentz — publishing an app, running an agent, integrating hardware, calling the API, or building any of the other paths below — is expected to require holding BOT, not just accepting it as an optional payment method. It isn't a one-time fee for a listing; it's a stake that keeps you an active, verified part of the developer ecosystem, scaled to what you're actually building and how much of the platform's capacity you're using. Each path below explains exactly what that looks like for that specific kind of development.
Apps & Agents
Browser tools, AI agents, and Web3 apps that run inside BotSurf.
7 build paths →Extensions
Chrome, Firefox, Edge and cross-browser extensions built on the BotGentz SDK.
4 build paths →Hardware Integration
Voice SDK integration for Smart TVs, speakers, gaming platforms and IoT devices.
6 build paths →API Integration
Voice, agent, content, ad and payment REST APIs, all under one platform.
7 build paths →Content Creation
Video, audio, news and book apps built on the BotGentz content system.
5 build paths →Ad Campaigns
Programmatic ad campaigns, sets, creatives and serving, built on the BotGentz ad stack.
5 build paths →E-Commerce
Checkout, carts and payment processing for apps and hardware orders.
4 build paths →Creator & Referral Tools
Creator dashboards, referral tracking and monetisation tools.
4 build paths →Browser & Voice Control
The Surfa voice engine, browser automation, and voice-controlled site categories.
4 build paths →Education & Learning
Voice-controlled learning, language and accessibility apps built on BotGentz\u2019s reading platform.
3 build paths →The Voice API documentation covers speech recognition, text-to-speech, browser automation and agent integration in depth, with its own request/response reference.
Explore the Voice API