REST API

Generate one in your dashboard. Keys start with awg_ and carry the same access as your account — treat one like a password, keep it server-side, and revoke it in the dashboard if it leaks.

Every request needs an Authorization header. This call touches nothing else, so it is the quickest way to confirm a key is good:

curl https://mcp-server-kpgyjzyfka-uc.a.run.app/v1/me \
  -H "Authorization: Bearer awg_your_key_here"

It returns the site the key controls. Every other endpoint works on that site and no other — the key decides which data you see, so there is no account or domain parameter to pass anywhere in this API.

curl https://mcp-server-kpgyjzyfka-uc.a.run.app/v1/ask \
  -H "Authorization: Bearer awg_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"question": "Do you ship to Japan?"}'

Check the answered field rather than reading the answer text. It is false when the agent had nothing to go on — that is your cue to escalate to a human, or to add the missing knowledge.

Base URL https://mcp-server-kpgyjzyfka-uc.a.run.app/v1. All responses are JSON.

{
  "domain": "example.com",
  "url": "https://example.com",
  "plan": "premium",
  "subscriptionStatus": "active",
  "apiVersion": "v1"
}

{ "question": "Do you ship to Japan?" }

{
  "question": "Do you ship to Japan?",
  "answer": "Yes — delivery takes 3–5 working days.",
  "answered": true,
  "sources": [
    { "title": "Shipping", "uri": "https://example.com/shipping" }
  ],
  "domain": "example.com"
}

{
  "domain": "example.com",
  "days": 7,
  "total": 42,
  "questions": [
    {
      "question": "Do you ship to Japan?",
      "answer": "Yes — delivery takes 3–5 working days.",
      "answered": true,
      "askedAt": "2026-07-31T04:37:03+00:00",
      "channel": "whatsapp"
    }
  ]
}

{
  "domain": "example.com",
  "days": 7,
  "total": 3,
  "questions": [
    {
      "question": "Do you integrate with Zendesk?",
      "answer": "I don't have enough information to answer that yet.",
      "answered": false,
      "askedAt": "2026-07-31T04:37:03+00:00",
      "channel": "web"
    }
  ]
}

{
  "domain": "example.com",
  "pageCount": 48,
  "uploadCount": 2,
  "pages": ["about.md", "index.md"],
  "uploads": ["kb-refund-policy.md"]
}

{ "title": "Refund policy", "content": "We refund within 30 days…" }

{
  "ok": true,
  "title": "Refund policy",
  "filename": "kb-refund-policy.md",
  "domain": "example.com"
}

{
  "started": true,
  "url": "https://example.com",
  "message": "Re-crawl started. It runs in the background and usually takes a few minutes."
}

{
  "domain": "example.com",
  "pagesIndexed": 48,
  "lastUpdated": "2026-07-31T04:37:03+00:00",
  "samplePages": ["index.md", "about.md"]
}

The endpoint most people automate first. Pull what your agent couldn't answer, and send it wherever your team already works:

const key = process.env.AIWEBGPT_API_KEY;
const res = await fetch('https://mcp-server-kpgyjzyfka-uc.a.run.app/v1/questions/unanswered?days=1', {
  headers: { Authorization: `Bearer ${key}` },
});
const { questions } = await res.json();

for (const q of questions) {
  await postToSlack(`Nobody could answer: "${q.question}" (via ${q.channel})`);
}

Answer one of them once, and every future visitor gets it — POST /v1/knowledge takes effect immediately, with no re-crawl.

Failures return {"error": {"code", "message"}} with a matching status. The message is written to be shown to a developer, not a visitor.

Credentials are checked before the path is matched, so a mistyped path without a valid key returns 401 rather than 404. With a valid key, an unknown path returns a plain 404 without the JSON error envelope.

60 requests per minute per key. Going over returns 429 with a Retry-After header. It is there to stop runaway loops — if you have a legitimate reason to need more, tell us and we will raise it.

The path carries the version. Anything that would break your code — a removed field, a renamed endpoint — arrives as /v2, and /v1 keeps working. New fields can appear in existing responses, so parse leniently and ignore what you don't recognise.