Interaction Mode 2 — API Provisioning
Paste a URL. Get a trained agent in 90 seconds.
Workforce Wave reads the business website, extracts services and hours, writes the system prompt, and activates the agent on the phone number — all triggered by a single POST to /v2/agents.
$50 free API credit on signup. No credit card required.
90s
From business URL to live voice agent.
Workforce Wave reads the site, writes the agent, activates on the number. Fast enough to run inside a user signup flow.
The Entire Provisioning Request
POST /v2/agents
Authorization: Bearer $WFW_API_KEY
{
"businessUrl": "https://smiledental.com",
"verticalType": "dental",
"phone_number": "+18435551234",
"white_label_id": "your-platform-id"
}
// 202 Accepted
{
"operation_id": "op_8kz2..."
}What Breaks Without It
Manual agent setup doesn't scale.
If your platform can't provision agents programmatically, your growth is gated by your operations team's bandwidth.
Problem
Manual setup doesn't scale past 10 agents
Your team can configure one agent by hand. When you need 50, or 500, manual setup becomes a full-time job. You can't grow a platform on point-and-click admin work.
Problem
Generic AI needs extensive prompt engineering
Building voice agents on raw LLMs means writing system prompts from scratch for every business — their services, hours, tone, escalation rules. It's months of work per vertical.
Problem
No API means no integration
If you're building a SaaS platform, your product needs to provision agents as part of its own workflow — on signup, on upgrade, on location creation. That's not possible without a real API.
How It Works
POST → 202 → agent live. Four steps.
The provisioning pipeline is deterministic and fully observable. Every step is trackable via the operations endpoint or the agent.activated webhook.
POST /v2/agents — one API call
Send the business URL, vertical, phone number, and optional white-label ID. That's the entire request body. The response is a 202 Accepted with an operation ID.
GET /v2/operations/{id} — poll for completion
Workforce Wave researches the business URL: reads the site, extracts services, hours, staff, specialties, and tone. It writes the system prompt and populates the knowledge base. Typically completes in 60–90 seconds.
agent.activated webhook fires
When the agent is live, your registered webhook receives agent.activated with the agent_id, phone_number, and status. No polling required after this — the event is the signal.
Agent takes calls immediately
The provisioned agent is fully trained, live on the phone number, and ready to handle inbound calls. Workforce Wave continues monitoring the business URL daily, keeping the KB in sync.
Full API Flow
The complete provisioning sequence.
Three API calls. The third one is optional — you can subscribe to the webhook instead and let the event drive your downstream logic.
Step 1 — Create
POST /v2/agents
{
"businessUrl": "https://...",
"verticalType": "dental",
"phone_number": "+1..."
}
→ 202 Accepted
{
"operation_id": "op_8kz2..."
}Step 2 — Track (Optional)
GET /v2/operations/op_8kz2
→ 200 OK
{
"status": "running",
"progress": 60,
"stage": "kb_build"
}
// ~90s later:
{ "status": "complete",
"agent_id": "agt_7rx9..." }Step 3 — Confirm
GET /v2/agents/agt_7rx9
→ 200 OK
{
"id": "agt_7rx9...",
"status": "active",
"phone_number": "+1843...",
"verticalType": "dental",
"kb_doc_count": 47
}Or: Skip Polling Entirely — Use the Webhook
Subscribe to agent.activated and your system gets called the moment the agent is live. No polling loop required.
// Webhook payload — fires ~90s after POST /v2/agents
{
"event": "agent.activated",
"agent_id": "agt_7rx9...",
"phone_number": "+18435551234",
"status": "active",
"verticalType": "dental",
"provisioned_at": "2026-04-17T14:23:01Z"
}Real Scenarios
Who uses API provisioning.
Any platform that manages businesses at scale needs this capability.
A user signs up for your practice management platform. Your backend fires POST /v2/agents with their website URL. Before they finish onboarding, a trained voice agent is live on their number — no configuration step in your UI required.
Your dental support organization has 40 practices. Instead of configuring 40 agents manually, your DevOps team runs a script: one POST per practice, Workforce Wave provisions each from the practice's own URL. Done in under 2 hours.
A franchise with 200 locations uses your platform. Each new franchisee gets a voice agent the moment they register. No manual work from your team — the entire provisioning pipeline runs inside your existing onboarding flow.
Performance Benchmark
90s
Average time from POST /v2/agents to agent active and taking calls.
Workforce Wave parallelizes site research, entity extraction, KB build, and system prompt generation. The 90-second target is maintained even for complex multi-service businesses across all supported verticals.
Start Building
Your platform should provision agents, not configure them.
The WFW API is live. $50 free credit on signup. Full OpenAPI 3.1 spec, webhook catalog, and MCP server included — no SDK required.
Full OpenAPI 3.1 spec at /.well-known/openapi.json