Build Voice Command APIs
What this is
Voice command APIs let an external application send a spoken instruction to BotSurf and get back a structured action, following the same request pattern already established by bg_ad_serve() and the platform's other ?action=api endpoints — authenticated, single-purpose calls rather than a sprawling general-purpose API surface.
How it works
Requests route through the existing ?action=api dispatcher, which hands off to botgentz_api.php — the same file already handling install, subscription-check, verify-install and renew-install actions. A voice_command action follows that established pattern: authenticate, process, return structured JSON, nothing more exotic than the endpoints already live.
Holding BOT for this path
This is the API category most directly tied to per-request cost, which makes it the clearest case for BOT-based access: voice command volume is expected to be metered against your held BOT the same way ai_monthly_limit already meters AI agent usage — more usage, more BOT expected to be held.
Related paths in API Integration