Integrations & API

The chat UI isn't the only way in. An authenticated API and an event ingest let other systems start threads, feed automations, and stream results.

REST + SSE API

The /api/v1 surface lets CI, scripts, or another service drive threads programmatically. It's guarded by a single bearer token.

• Create a thread with a first prompt — spins up a fresh sandbox and branch and queues the turn.
• Follow-up turns on an existing thread.
• Read a thread's status and message history.
• Stream events over Server-Sent Events as the agent works — the same event spine the browser rides, so a client on one server can stream an agent running on another.

A thread created this way is a normal chat thread; you can open it in the UI and take over.

GitHub webhooks

Point a repo's webhook at darting.dev and an issue or PR comment is routed straight to a project's chat agent — so a comment can kick off a thread. When a webhook secret is set, the payload signature is verified.

Inbound hooks

Any external system can POST an event onto a project's event spine — Sentry issues, Stripe events, a feedback relay (directly, or through Zapier / n8n). Automations subscribe to those events and react. External payloads are always treated as data to summarize, never as instructions, so an inbound hook can't tell an agent what to do.

Hosted previews

A project can opt into a hosted deployment at its own subdomain. It runs from the project's snapshot, scales to zero when idle, and wakes on the next request. When main moves, it redeploys — so the preview always reflects the latest merged code.