Common reseller workflows
Provision customer accounts
Create the required account hierarchy, retain the returned Vida IDs alongside your own customer identifiers, and create the Agent accounts each organization needs. Confirm product and billing impact before creating paid resources.Configure and publish Agents
Use the normal staging, test, and publish lifecycle. Discover supported models, voices, functions, and apps for the selected account instead of relying on a copied catalog. See Agent API Guides.Operate Computer Agents
Provision and monitor Computers, install skills, connect credentials and channels, manage workspace artifacts, and assign Computer Tasks through the authenticated Computer Agent APIs. See Computer Agent configuration.Connect communications
Assign phone numbers, configure SIP where required, create Tasks for outbound communication, and read complete conversation details after work finishes. Test routing under the exact customer account before announcing a channel.Measure usage and outcomes
Use usage records for billing and reconciliation. Use logs, reporting fields, and time-series metrics for operational and customer outcomes. Define the population and denominator for every metric. See Logs, conversations, and reporting.Build account scope into the integration
Store the stable account ID for every customer and Agent. UsetargetAccountId to select the authorized account for a request and use the endpoint’s explicit organization, reseller, or partner selector only when its schema requires that level.
Read current state before a mutation, apply the smallest intended change, and read the resource again. An accepted asynchronous job, queued Task, or publish response is not proof that the resulting capability works.
If an AI agent will perform these workflows, give it the Vida API Skill with the OpenAPI reference.