Ask Skate from your own code

curl -X POST https://api.useskate.com/v1/ask \
  -H "Authorization: Bearer sk_skate_…" \
  -H "Content-Type: application/json" \
  -d '{"site": "s_…", "question": "How do I export invoices?", "user": "u_123"}'

• site: the site id (Settings → Sites, or list_sites over MCP).
• question: 3 to 2000 characters.
• user: optional, your own id for the person asking (up to 80 characters). It groups their questions in Conversations. Do not send an email address.

The key is an API key from Settings → API keys. A read-only key is enough.

The answer

{
  "kind": "answer",
  "answer": "Open Billing → Invoices and press Export CSV.",
  "check": "grounded",
  "answered": true,
  "sources": [{ "kind": "instruction", "title": "Your instruction", "url": "", "text": "To export invoices, open Billing → Invoices and press Export CSV." }],
  "task": "tsk_3f9a1c07b2de"
}

• kind
  • answer: an answer from your sources.
  • link: the question asks for a change in the app. link opens your app with the request ready, and Skate does it there with the person’s approval. The API itself never changes anything.
  • person: one of your “a person handles this” instructions covers it, or the person asked for a human. No model is called and no credit is used.
• check
  • grounded: every number, price and date in the answer is in the sources it cites.
  • ungrounded: the answer states a value its sources do not carry. Do not show it as fact.
  • no_sources: it cites nothing.
• answered: false when your sources did not answer the question. The answer then says so.
• task: the id of this question in Conversations.

Skate never says it did, checked or looked up anything here: it has no page and cannot see the person’s account.

Cost and limits

• One task credit per question, like a widget task, and your daily AI limit applies. A person answer is free.
• 30 questions per minute per key.
• Every question is logged as a conversation, so it counts in Topics, Support and the weekly report like a widget question. Its row carries source: "api".

Errors

Banners, announcements, updates and surveys: /v1/items

Create and publish in-app content from your own code, for example a maintenance banner from your deploy pipeline. Use the same API key (Settings → API keys). Any key can read; changing needs a key made with write access.

# A draft banner
curl -X POST https://api.useskate.com/v1/items \
  -H "Authorization: Bearer sk_skate_…" -H "Content-Type: application/json" \
  -d '{"site":"s_…","kind":"banner","name":"Maintenance","content":{"body":"We are down on **Sunday** from 02:00 to 04:00 UTC.","cta":{"kind":"none"}}}'

# Publish it (use the id from the answer)
curl -X POST https://api.useskate.com/v1/items/bn_…/publish \
  -H "Authorization: Bearer sk_skate_…" -H "Content-Type: application/json" -d '{"site":"s_…"}'

Items are checked by the same rules as the dashboard editor, so the API cannot make anything you could not make there (an https link, a readable colour, a valid audience). An answer carries the item as the editor sees it.

Limits: 60 calls in any 60 seconds per key, reads and writes alike (a sliding window, not a bucket that resets on the minute: the 61st call within 60 seconds of the first gets 429, and Retry-After says when the next one is allowed). 200 items per site. Every call is in the key’s audit log; every change (create, edit, publish, unpublish, archive) is also on the site’s Activity page, by “API key <name>”.