echoia

Getting started

Echoia developer platform

Publish, read comments and answer messages across ten social platforms — from your own code or from an AI agent. One API key opens all three doors.

Quickstart

Create a token and make your first call in about five minutes.

Connect an agent

Point Claude, Cursor or ChatGPT at your workspace over MCP.

Three ways in

They are not alternatives to choose between once — most people end up using two. All three authenticate with the same token and obey the same scopes and quotas.

Use it whenStart at
REST APIYou are writing code — a script, a backend, an internal tool.API reference
MCP serverYou want an AI client to operate your workspace conversationally.MCP server
Agent skillYou want an agent to know the workflow, not just the endpoints.Agent skill

What you can do

  • List connected accounts with follower counts
  • Create drafts, schedule posts, or publish immediately across ten platforms
  • Read post performance — views, likes, comments, shares — day by day
  • Read comments with AI sentiment and tags, and reply publicly as your accounts

Scoped to one workspace

A token can only ever see the workspace it was created in. There is no parameter to name another one — it is not a check that can be bypassed, it simply does not exist in the interface.

Base URL

Every REST endpoint lives under a single base. The MCP server has its own host — see MCP server.

text
https://app.echoia.io/api/v1

Conventions

  • Requests and responses are JSON. Send Content-Type: application/json on writes.
  • Authentication is a bearer token in the Authorization header.
  • Errors return { "error": "…" } with a 4xx status — see Errors.
  • Timestamps are ISO 8601 in UTC.
Was this page helpful?