> ## Documentation Index
> Fetch the complete documentation index at: https://vida.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# API enablement for resellers

> Use Vida APIs to provision, configure, operate, and measure customer Agent deployments.

Vida's APIs let resellers and service providers connect customer onboarding, Agent configuration, communications, operations, usage, and billing to their own systems.

Start with the [API overview](/docs/api-reference/overview) and [authentication guide](/docs/api-reference/authentication). Use the generated endpoint reference for exact request and response schemas.

## 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](/docs/api-reference/agent-guides/overview).

### 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](/docs/api-reference/agent-guides/computer-agents).

### 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](/docs/api-reference/platform-guides/logs-conversations-and-reporting).

## Build account scope into the integration

Store the stable account ID for every customer and Agent. Use `targetAccountId` 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](/docs/api-reference/vida-api-skill) with the OpenAPI reference.