EchoLeads
EchoLeads is an autonomous AI voice sales platform out of T-Hub, Hyderabad, India, that replaces manual SDR work with AI agents running a full omnichannel workflow: outbound cold calling and inbound response, real-time BANT qualification, WhatsApp Business follow-up, Instagram DM lead capture, live intent-based lead scoring, human handoff, CRM sync, and calendar booking during the call. It sells into real estate, insurance, SaaS, healthcare, financial services and e-commerce, supports English, Hindi and regional Indian languages, and claims TRAI-compliant outbound calling. It is backed by Google for Startups, T-Hub and Math Nuage (DST, Government of India). Agent-native surface is real and verified — a live llms.txt, a full llms-full.txt content index, an RFC 9116 security.txt, and an AI-crawler-permissive robots.txt. The API surface is not: a REST API is self-declared in llms-full.txt (trigger calls, retrieve transcripts, push lead scores) but the documentation page returns 502, api.echoleads.ai has no listener, and no OpenAPI, AsyncAPI, GraphQL SDL, Postman collection or MCP server is published on any host.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles EchoLeads the way a machine reads it — 5 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — EchoLeads scores 16.0/100 (emerging), with a separate agent-readiness read of 6/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
EchoLeads links a REST API page from its nav and its own llms.txt, but https://echoleads.ai/resources/api-documentation returns 502 Bad Gateway on every probe while prerendered marketing routes on the same host serve 200 — the Next.js origin behind the uncached routes is down — and api.echoleads.ai resolves to 13.203.84.238 with TCP 80 and 443 both closed, so there is no reachable documentation and no OpenAPI, GraphQL SDL, AsyncAPI, Postman collection or MCP server on any EchoLeads host.
The documentation is public — a person can read it, but a machine cannot. This one is EchoLeads's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://echoleads.ai/resources/api-documentation→ HTTP 502https://echoleads.ai/openapi.json→ HTTP 502https://cmsapi.echoleads.ai/openapi.json→ HTTP 404https://echoleads.ai/llms.txt→ HTTP 200https://echoleads.ai/.well-known/security.txt→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from EchoLeads's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/echoleads/"
title="EchoLeads on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/echoleads.svg"
alt="EchoLeads Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/echoleads/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/echoleads/"
title="EchoLeads on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/echoleads/card.svg"
alt="EchoLeads Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile EchoLeads
Each block below is one kind of artifact we hold for EchoLeads. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
EchoLeads Platform
EchoLeads provider surfaces. The agent-native artifacts (llms.txt, llms-full.txt, security.txt) are confirmed publicly reachable and are saved verbatim in this repo. A REST API ...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Echoleads Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for EchoLeads — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/echoleads · machine-readable index on apis.io
This is an independent, third-party profile of EchoLeads, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.