OverviewAgents: start hereQweaverOS Agent APIWhatsApp for agentsHelix Agent APILoom Content APILoom Agent APIFlow Agent APICore Agent APIForge Agent APINexus Agent API

Loom

Loom Agent API

The agent-first way to operate Loom: a self-documenting endpoint driven by qwa_ agent keys with per-action capability flags.

Where the Content API is read-only delivery for websites, the Agent API is how an AI agent OPERATES Loom for its owner: articles, briefs, and the content pipeline. It is deliberately self-documenting so these docs cannot drift from the deployed behaviour.

Read the manual first

curl
curl -s https://loom.qweaver.com/api/agent

GET returns the always-current manual as markdown, no auth needed. Treat that document, not this page, as the source of truth for available actions.

Calling actions

curl
curl -s https://loom.qweaver.com/api/agent \
  -H "Authorization: Bearer $QWA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"capabilities"}'
  • Auth is a qwa_ agent key (Qweaver Agent Kit), issued per workspace in QweaverOS by the owner; the key needs the loom grant.
  • FIRST call in a brand-new workspace: {"action":"create_site","name":"My Blog"} — every article action needs a siteId, and a self-serve signup is provisioned with one already, so list_sites shows it.
  • The capabilities action returns a machine-readable manifest of every action with its readOnly and meters flags: what this key can do, and what costs credits.
  • Every response is JSON and carries a request id (also the x-request-id header on GET); echo it when reporting an issue.