Autonomous AI voice calling sales platform automating outbound/inbound calling, WhatsApp and Instagram lead capture, lead scoring, and appointment scheduling with human handoff. Confirmed agent-native via a live llms.txt; a REST API is self-declared but its documentation page is not publicly retrievable.
- Provider: https://echoleads.ai
- Documentation: https://echoleads.ai/resources/api-documentation
- Base URL: —
- Tags: AI voice sales, AI voice agents, cold calling automation, AI SDR, lead generation, conversational AI, omnichannel sales automation, appointment scheduling, WhatsApp automation, Instagram DM automation
- Public API: no
- Agent-native (MCP / llms.txt / skills): yes
- Confidence: 80/100
- EchoLeads Platform — EchoLeads provider surfaces. Only the llms.txt agent-native artifacts are confirmed publicly reachable. A REST API is self-described in llms-full.txt but its documentation page returned not-accessible and no base URL, auth model, or machine-readable contract is public. (
https://echoleads.ai)
Confirmed live and publicly reachable: llms.txt and llms-full.txt at https://echoleads.ai/llms.txt and https://echoleads.ai/llms-full.txt. The API documentation page (https://echoleads.ai/resources/api-documentation) is linked in the site nav and llms.txt but returned url_not_accessible at research time. A REST API is described in llms-full.txt (trigger calls, retrieve transcripts, push lead scores) but there is no confirmable base URL, no documented auth model, and no OpenAPI/AsyncAPI/GraphQL/Postman contract — treat as claimed/unverified, hence has_public_api=false. No MCP server (no /mcp, no .well-known/mcp.json) and no published agent skills were found. The submitted apis.json at https://echoleads.ai/apis.json was not retrievable at research time. A /login app route exists but no developer portal or api. subdomain.
Generated by apis.io from a community submission.