Bredgio Documentation
Bredgio is a SaaS dashboard that drives a Chrome extension to publish posts, leave comments, and run outreach workflows on Facebook (with Twitter, Instagram, LinkedIn, Threads on the roadmap) from your team's own browsers.
| Doc | Audience | What it covers |
|---|---|---|
| API Reference | Backend engineers, automation builders | The full HTTP + WebSocket surface — auth, agents, tasks, schedules, logs, extension heartbeat, and the realtime hub protocol. |
| MCP Server Spec | AI tooling integrators (Claude Desktop, Cursor, Cline, …) | A design specification for bredgio-mcp — the Model Context Protocol server that will let AI assistants dispatch tasks, manage agents, and inspect runs. |
Conventions used in this docs site
- Base URL —
https://bredgio.letmesee.ccfor HTTP,wss://bredgio.letmesee.ccfor WebSocket. - Content type —
application/jsonfor all request bodies and responses. - Auth — session cookie (
bredgio_session, set byPOST /api/auth/login) for the dashboard; per-agent agent token for extension-side traffic (heartbeat + WebSocket hub); Personal Access Token (PAT) for external automation and MCP. - Time — every timestamp returned by the API is ISO 8601 in UTC. Inputs accept any ISO 8601 string that
new Date()can parse. - IDs — Mongo ObjectId strings (
agentId,taskId,scheduleId, …) unless noted otherwise.
Stability
The API is currently at v0 — pre-release. Endpoint shapes will change without notice while we stabilise the surface. The MCP server is a specification; it is not yet shipped on npm.
Production URL https://bredgio.letmesee.cc and the WebSocket path
/api/social-agents/ws are stable and used by the extension today.