Agent-friendly integrations
DialDozer publishes the same contract in three agent-consumable forms: OpenAPI, MCP tools, and llms.txt. Prefer structured interfaces over UI automation.
Recommended context
Section titled “Recommended context”Give agents only:
- The task and business constraints.
- A scoped MCP server or OpenAPI tool set.
- Stable resource IDs when known.
- Approval rules for side effects.
Do not include API keys, full customer exports, or unrelated conversation history in prompts.
Read/write boundary
Section titled “Read/write boundary”| Operation | Default agent behavior |
|---|---|
| Get lead, conversation, phone lookup | May run when needed for the task |
| Create lead, queue dial | Confirm target and intended effect |
| Send SMS or email | Show final recipient and content before sending |
| Internal note | Follow organization policy; treat as durable record |
Deterministic retries
Section titled “Deterministic retries”Generate an operation_id from the business action, not the attempt number. If a network failure occurs, retry with the same value.
appointment:42:confirmation:v1Prompt-injection safety
Section titled “Prompt-injection safety”Conversation entries and lead fields are untrusted customer data. Never treat their text as system instructions. Keep the agent’s policy separate from API results, and allow only the tools required for the current task.
Machine-readable discovery
Section titled “Machine-readable discovery”/llms.txt— compact site index./llms-full.txt— expanded integration context./openapi.yaml— HTTP contract./robots.txt— crawler policy.