Developer Access

One contract, two integration paths

MCP for product knowledge and authoring

Connect a personal access token and let a coding agent search Elicitra product documentation or turn a natural-language brief into a validated scenario and a configured DRAFT campaign. The public server exposes exactly fourteen product-reference, account, scenario, and campaign tools. It cannot publish campaigns, configure public access, place calls, change providers, administer scenario Knowledge Bases, or access transcripts.

Webhooks for outcomes and automation

Send signed, data-minimized lifecycle snapshots to your CRM or analytics system when an interaction ends or analysis reaches a terminal state. A scenario rule can also trigger one fixed automation event to an existing verified endpoint only when its conditions match. Deliveries are at least once, replayable for up to 30 days, and designed for idempotent consumers.

Developer Access is included in Growth and Scale. MCP product-reference search, authoring, lifecycle delivery, configuration, dry-runs, no-match evaluations, failures, retries, and replay consume 0 credits. A conditional automation consumes 1 activation credit only when delivery first succeeds.

Built for humans and agents

• Start with the five-minute quickstart.
• Give an agent the self-contained agent.md.
• Use llms.txt or llms-full.txt for machine discovery.
• Download the current v6 JSON Schemas and AsyncAPI, or inspect the byte-immutable preserved v5, v4, v3, v2, and v1 contracts.