Quickstart

Base URL is https://www.enso.bot. Everything speaks JSON. Read endpoints need nothing; write and signal endpoints take a key header; the MCP endpoint speaks OAuth 2.1.

curl -sS https://www.enso.bot/api/public/v1/company | jq '.name, .agents[].name'

Authentication

Publish on-brand landing pages at /p/{slug}. Send content only - the enso design system supplies layout, styling and customer logos. Every write passes a brand quality gate.

curl -X POST https://www.enso.bot/api/public/content/pages/generate \
  -H "x-api-key: $CONTENT_API_KEY" \
  -H "content-type: application/json" \
  -d '{"slug":"agentic-seo-for-fintech",
       "topic":"Getting fintech brands cited inside AI answers",
       "icp":"Growth leads at Series B fintech companies",
       "proof":["64 citations placed","47 still live after 90 days"],
       "cta_label":"Book a call","cta_href":"/book-a-call"}'

Reference: /content-api.md

Every touch a person or account has with enso.bot - form fills, URL submissions, reads and unlocks, newsletter signups, wizard progress, email opens and clicks - normalized into one pollable event stream.

curl -sS "https://www.enso.bot/api/public/v1/signals?days=7&limit=500" \
  -H "x-api-key: $SIGNALS_API_KEY"

curl -sS https://www.enso.bot/api/public/v1/signals/accounts/acme.com \
  -H "x-api-key: $SIGNALS_API_KEY"

Reference: /signals-api.md · /signals-agent.md

Open, read-only JSON about enso: the company, the blog, the research ledger and open roles. No key, no rate-limit signup, CORS enabled.

curl -sS https://www.enso.bot/api/public/v1/research | jq '.experiments[0]'
curl -sS https://www.enso.bot/api/public/v1/company | jq '.agents'

Reference: /openapi.json

Model Context Protocol server over streamable HTTP, protected by OAuth 2.1 with Dynamic Client Registration. Point Claude, Cursor or any MCP client at it and the enso knowledge base becomes tool-callable.

{
  "mcpServers": {
    "enso": { "url": "https://www.enso.bot/mcp" }
  }
}

Reference: Setup guide

Errors and limits

Signal ids are stable (source:row_id) so they double as idempotency keys. Poll the signal stream on next_since rather than a fixed interval, and keep account lookups - they return seen: false instead of a 404, so they are safe as an enrichment check.

Machine-readable files

Site map

Every public surface on enso.bot, grouped by intent. Content routes are server-rendered, so a plain HTTP GET returns the full HTML - title, headings, body copy and links - on the first byte.