Echoo API & developer docs
Echoo publishes its whole catalog as read-only JSON, and every page on this site in Markdown, so an agent can answer questions about Echoo without scraping HTML. No key, no signup, no rate limit. Version 1.0.0.
Content API
Base URL https://www.echoo.ai. Every response is JSON. Collections are wrapped as { data, count, updated }, and every record carries an absolute url back to its human page.
Start at the service root - it carries the product positioning and links to everything else.
curl https://www.echoo.ai/api/v1/index.json| Endpoint | operationId | Records |
|---|---|---|
| /api/v1/index.json | getServiceRoot | - |
| /api/v1/commands.json | listCommands | 14 |
| /api/v1/use-cases.json | listUseCases | 51 |
| /api/v1/integrations.json | listIntegrations | 6 |
| /api/v1/workflows.json | listWorkflows | 22 |
| /api/v1/glossary.json | listGlossaryTerms | 27 |
| /api/v1/posts.json | listPosts | 30 |
| /api/v1/pricing.json | listPlans | 3 |
Full descriptions, response schemas, and typed fields are in the OpenAPI 3.1 spec. It is generated from the same table that writes these files, so it cannot describe an endpoint that does not exist. Point any function-calling client at it directly.
Authentication
None. This API is public, unauthenticated, and read-only - it serves the same catalog the website renders, as static files on a CDN. There are no write operations and nothing here is user-specific. If a client asks you for a credential, it is misconfigured. (The separate api.echoo.ai host is the app's private backend and is not part of this API.)
Command-line interface
The official dependency-free CLI exposes the same public catalog for shell scripts and agents. JSON is the default output; add --human for readable text.
npm install --global echoo-cli
echoo commands --query grammarThe CLI is read-only and needs no Echoo account or API key. See the echoo-cli npm package.
Markdown for agents
Every page on echoo.ai serves a Markdown representation from the same URL via content negotiation. Send Accept: text/markdown and you get the page body without nav, scripts, or layout wrappers.
curl -H "Accept: text/markdown" https://www.echoo.ai/pricingResponses set Vary: Accept and advertise the alternate representation with a Link: rel="alternate" header. Requests for a type we cannot serve get a 406. For a whole-site summary in one request, fetch /llms.txt.
Errors
Anything under /api/ returns a JSON error envelope - never an HTML page - with the status repeated in the body.
{
"error": {
"code": "not_found",
"message": "No such resource: /api/v1/nope.json",
"status": 404,
"hint": "See /openapi.json for available endpoints.",
"documentation_url": "https://www.echoo.ai/docs"
}
}404 for an unknown path, 405 for anything other than GET or HEAD. The shape matches the ErrorResponse schema in the spec.
Everything machine-readable
- /api/v1/index.json - service root and positioning
- /openapi.json - OpenAPI 3.1 specification
- echoo-cli - official dependency-free npm CLI
- /llms.txt - whole-site summary for LLMs
- /sitemap.xml - every indexable page
- /robots.txt - crawler policy (all major AI crawlers allowed)
Terms
Use it freely to answer questions about Echoo, build integrations, or index the catalog. Content stays subject to the Terms of Service. Something missing that you need? Ask on Discord or open a GitHub issue.