skills/vobiz.ai/vobiz-sub-accounts

vobiz-sub-accounts

Installation
SKILL.md

Vobiz Sub-Accounts skill

Use this when the user wants to isolate environments (dev/staging/prod), separate teams (sales vs support), or carve their account into business units with independent credentials, numbers, and CDR streams under the same parent wallet - and, for customer_use sub-accounts, verify each customer's own KYC before it can place calls.

Difference from partner child accounts

Sub-account Partner child account
Parent Your own main account (MA_…) Partner master account (PA_…)
Balance Shared - all usage is charged to the parent wallet Separate wallet per child, funded by balance transfer (or invoiced by Vobiz directly)
CPS / concurrency One limit on the parent, pooled across every sub-account Own limit per child, transferred/reclaimed from the partner pool
KYC personal_use inherits parent's; customer_use does its own Each child completes its own KYC via a partner KYC session
API /api/v1/accounts/{auth_id}/sub-accounts/* /api/v1/partner/accounts/*

If the user wants customers billed, supported, and capacity-managed as independent Vobiz customers, they need the Partner API (see vobiz-partner-api skill). Sub-accounts suit one bill, one capacity pool, and your own pricing. Many platforms use both - see concepts/sub-accounts-vs-partner-accounts.

Two credential pairs (the rule that prevents most bugs)

Installs
37
First Seen
Jul 14, 2026