Skip to main content
Roark connects to your agent platform in two directions: it pulls production conversations in for monitoring and scoring, and it drives simulated conversations out for testing. Which of those you get depends on the platform. This page is the map. Start with the capability matrix, then jump to the setup guide for your platform.

​
Capability Matrix

Supported out of the box  ·  Possible with extra setup  ·  Not supported

​
Notes on specific cells

LiveKit is a real-time transport, not an agent framework, so it doesn’t expose prompts or worker source code. Roark imports the named agents configured in your LiveKit project purely so calls can be attributed to the right agent. If you want prompts and tool definitions in Roark, use the self-hosted SDK integration, which captures the system prompt as a tracked prompt revision.
Roark acts as an OpenTelemetry collector at https://api.roark.ai/v1/traces, so any platform can send traces over OTLP/HTTPS. Step-by-step guides exist for VAPI, LiveKit, and custom integrations. Platforms marked work through the custom-integration path: you instrument your own code and correlate spans to the call yourself.
No provider currently pushes production chat transcripts into Roark. Text conversations reach Roark either from a chat simulation or by posting them to the /v1/chat API yourself, which is why Custom / API is the only row with chat import.
A WebRTC endpoint can be attached to any Roark agent whose underlying agent speaks LiveKit or SmallWebRTC. The matrix marks the platforms where that’s the native, documented path. If your VAPI or ElevenLabs agent is fronted by one of those transports, you can wire up a WebRTC endpoint for it too.

​
What Each Capability Means

​
Browse Integrations

​
Voice agent platforms

VAPI

Sync assistants and stream calls in over webhooks

Retell AI

Sync agents and analyze conversations

ElevenLabs

Voice and chat, the only platform that does both

Bland AI

Monitor Bland phone agents via pull-based sync

Leaping

Sync Leaping AI agents, prompts, and tools

​
Real-time frameworks & self-hosted

LiveKit Cloud

Dashboard-managed webhook integration, plus WebRTC endpoints

LiveKit (self-hosted)

Drop observe_session into your own Agents worker

Pipecat

Drop the Roark observer into your Pipecat pipeline, self-hosted or on Pipecat Cloud

​
Chat agent platforms

Google CES

Chat simulations against Customer Engagement Suite apps

Kore AI

Chat simulations against Kore Agent Platform apps

Custom / API

Any platform: send calls and chats with the API or SDKs
Don’t see your platform? Custom integrations cover every capability in the matrix. Send an audio file or a message transcript and Roark handles the rest.

​
Simulation Transports

Whether a simulation runs as a call or a chat is decided by the endpoint type on the agent target. You don’t pick a modality separately.
ElevenLabs WS endpoints resolve to chat, not voice. To test an ElevenLabs agent over audio, use a Phone endpoint instead.

​
How Integrations Work

1

Choose your platform

Pick your platform from the cards above and open its setup guide.
2

Authenticate

Connect with an API key, OAuth, or (for self-hosted frameworks) a Roark API key dropped into your worker.
3

Configure sync

Select which agents to track and how far back to backfill historical calls.
4

Start monitoring and testing

Calls flow in and get scored automatically. Synced agents become targets you can point run plans at.
Data reaches Roark one of three ways, depending on the platform: webhooks (VAPI, Retell, LiveKit Cloud), scheduled pull (ElevenLabs, Bland, Leaping), or a drop-in SDK you add to your own code (LiveKit self-hosted, Pipecat, custom).

​
One Integration, Many Agents

A single integration syncs every agent in the connected account:
  • Single setup: configure once, sync all agents
  • Centralized management: monitor every agent from one integration
  • Unified analytics: compare performance across agents and across platforms
  • Simplified testing: target any synced agent in a run plan

​
Security & Privacy

  • Encrypted connections: TLS on every data transfer
  • Secure storage: credentials encrypted at rest and referenced by ID, never embedded in plans
  • Access control: role-based permissions for integration management
  • Audit logging: every integration activity is recorded
  • Data isolation: customer data separated by organization
  • PII redaction: strip sensitive data from transcripts and recordings with PII redaction
For network-level controls, see IP whitelisting.

​
Next Steps

Generate an API key

Every integration path starts here

Set up collectors

Score every imported call automatically

Build a run plan

Turn a synced agent into a test suite

Webhooks

Push Roark events into your own systems