// the vendor-neutral agent cloud
plyk.
// adapters in, plugins out, every turn audited.
// what plyk owns
Three things the platform actually does.
Adapters bring your system of record in. Plugins call your existing voice and messaging stack out. Every turn ships with an immutable audit row your regulators can read.
Bring your CRM.
Typed adapters into Salesforce, HubSpot, Epic, Athena, Zendesk, ServiceNow, Shopify, or your own Postgres. The agent reads and writes records in the system you already pay for.
Bring your voice stack.
Twilio · ElevenLabs · LiveKit · Stripe · Slack · Resend · Cal.com · n8n. Tenants scope and pay for plugins directly — Plyk doesn't markup the call.
Per-turn evidence.
Deterministic action plans, lease-claimed turn execution, durable retry. Every turn produces a structured audit row keyed by tenant, subject, model, prompt, plan, and outcome.
// how it works
One loop. Three concrete steps.
No graphs to draw in a visual editor. Webhook in → audit row out.
Event arrives
An adapter webhook hits /webhooks/<adapter>/.... Plyk validates, normalizes, and writes the event into the per-tenant queue.
Context loads
Dispatcher claims the row by lease. Adapter loads tenant context — records, history, subject metadata. The LLM you chose produces a deterministic action plan.
Plan + audit
Plugins execute the plan, sequentially, in a sandboxed turn. Every action persists. An audit row drops into agent_actions with full lineage.
// integration surface
Plug it into what you already run.
Two grids. The first is what the agent works inside. The second is what the agent calls.
Adapters
// systems the agent acts inside
Plugins
// tools the agent calls
// pricing
Three tiers. Usage-based at the floor.
No per-conversation pricing. No per-seat "digital labor" license. You pay for the turns you run and the audit you keep.
Starter
- →Free up to first tier of turns / month
- →One tenant, one adapter
- →30-day audit retention
- →Bring your own LLM key
- →Community support
Growth
- →Per-tenant control plane
- →Unlimited adapters & plugins
- →Extended audit retention
- →WebSocket realtime monitor
- →Priority support, SLOs on dispatch
Enterprise
- →VPC peering, SSO, custom auth
- →BAA, HIPAA / SOC 2 paperwork
- →Long-horizon audit retention
- →Dedicated dispatcher capacity
- →Implementation partner included
// in production today
“The same runtime is operating real turns in a regulated vertical — not a logo on a slide, the first paying tenant.”design partner · healthcare · 2026
// from zero to a real webhook turn
5-minute quickstart.
Three curl calls — sign up, mint a key, send an event. The dispatcher does the rest.
Create an operator account. Returns a JWT.
curl -X POST https://api.plyk.ai/api/v1/auth/signup \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com","password":"correcthorsebatterystaple"}'Issue a tenant key. The full_key is shown once.
curl -X POST https://api.plyk.ai/api/v1/account-keys \
-H "Authorization: Bearer $JWT" \
-H "Content-Type: application/json" \
-d '{"name":"first-key","scopes":["events:write"],"env":"test"}'The dispatcher claims it within ~2 seconds and runs the turn.
curl -X POST https://api.plyk.ai/webhooks/generic \
-H "Authorization: Bearer $PLYK_KEY" \
-H "Content-Type: application/json" \
-d '{"event_type":"hello.world","payload":{"body":"hi"}}'