API Reference

Authentication

There are no secret keys. Every request carries your public sitekey, and the endpoints that do work (/api/search, /api/ask, /api/handoff) enforce the request's Origin: it must be your site's registered hostname or a subdomain of it. Requests from anywhere else get a 403.

Config

Everything a client needs to render an assistant for a site: names, branding, suggested questions, and whether the site is currently over its monthly cap (limited — when true, ask is unavailable and clients should fall back to search).

GET https://assist.edge.network/api/config?sitekey=ea_your_sitekey

{
  "name": "Example Inc",
  "assistantName": "Edge Assist",
  "hostname": "example.com",
  "welcome": "Hi! Ask me anything about Example.",
  "placeholder": null,
  "position": "bottom-right",
  "theme": { "accent": "#0BC95E" },
  "prompts": ["How can we help?"],
  "suggested": ["What does it cost?", "How do I get started?"],
  "explore": [{ "title": "Pricing", "url": "/pricing" }],
  "badge": true,
  "whiteLabel": false,
  "handoff": true,
  "extended": false,
  "limited": false
}

Search

Instant full-text results over the ingested content — no AI call, free and unlimited. Queries under 2 characters return an empty list; up to 8 results, one per page, best-matching first. Snippets mark matched terms with square brackets.

GET https://assist.edge.network/api/search?sitekey=ea_your_sitekey&q=storage+pricing

{
  "results": [
    {
      "url": "/storage/pricing",
      "title": "Storage Pricing",
      "section": "storage",
      "snippet": "…[Storage] is billed at $0.015 per GB per month…"
    }
  ]
}

Ask

Composes an answer over the ingested content and streams it. Questions must be 3–500 characters. Include history (the prior turns of the conversation) to make follow-ups work; include page so questions like "is there a limit on this page?" resolve against the page the visitor is reading.

POST https://assist.edge.network/api/ask
Content-Type: application/json

{
  "sitekey": "ea_your_sitekey",
  "question": "How much does storage cost?",
  "history": [],              // optional: prior turns [{ role, content }]
  "page": "/storage/pricing", // optional: page the visitor is on
  "conversationId": "…"       // optional: groups turns in your question log
}

The response is Server-Sent Events: a sources event first (retrieval is instant), then delta events carrying JSON-encoded answer fragments (decode each with JSON.parse — that's how newlines survive SSE framing), then done:

// Response: Server-Sent Events
event: sources
data: [{ "url": "/storage/pricing", "title": "Storage Pricing", … }]

event: delta
data: "Storage is billed at "

event: delta
data: "$0.015 per GB per month…"

event: done
data: {}

Answers are markdown with inline citations as relative links. Each answered question is one metered question — including answers served from the cache.

When a site is over its monthly cap, ask returns:

HTTP/1.1 429 Too Many Requests

{ "error": "monthly-limit", "limited": true }

Handoff

Hands the conversation to a human. Requires a handoff email configured on the site (Control → Widget) — otherwise returns 404. The visitor's email, message, and recent transcript are forwarded to that address; replying to the email reaches the visitor directly. Handoffs are free (no metered question).

POST https://assist.edge.network/api/handoff
Content-Type: application/json

{
  "sitekey": "ea_your_sitekey",
  "email": "visitor@example.com",
  "message": "I'd like a demo",          // optional
  "page": "/pricing",                    // optional
  "transcript": [                        // optional: recent turns (max 12)
    { "role": "user", "content": "Can I talk to someone?" },
    { "role": "assistant", "content": "Of course — …" }
  ]
}

{ "success": true }

Errors & Rate Limits

Errors are JSON with an error message: 400 for invalid input, 403 for a disallowed origin, 404 for an unknown sitekey, 429 when rate-limited or over the monthly cap. Rate limits are per visitor IP: