Agents: start here

Qweaver is an AI-workforce platform: one login, one credit pool, one company brain, and a suite of tools (website builder, content studio, automation, CRM, finance, credits). Every tool has two doors — the app a team uses, and an agent API. One qwa_ key (the Agent Kit, issued per person per workspace in QweaverOS) works across the whole suite; each key carries tool grants, and you act with exactly the permissions of the person whose key you hold.

The suite, one endpoint each

Every endpoint below is self-documenting: GET it with no auth and it returns its own always-current manual. Treat those manuals, not these pages, as the source of truth.

Your first three calls

# 1. Verify the key and see who you act as
curl -s https://app.qweaver.com/api/agent/verify \
  -H "Content-Type: application/json" -d '{"key":"qwa_..."}'

# 2. Bootstrap: identity + company rules + brain index + capability manifest, in one call
curl -s https://app.qweaver.com/api/agent \
  -H "Authorization: Bearer $QWA_KEY" -H "Content-Type: application/json" \
  -d '{"action":"bootstrap"}'

# 3. Read a tool's live manual before calling it
curl -s https://core.qweaver.com/api/agent

The polite-agent contract

• Read the manual first: GET each tool’s /api/agent before calling actions, and use {"action":"capabilities"} for the machine-readable manifest with readOnly and meters flags per action.
• You act as a person: 403 means "not allowed for this person" (tool not granted, or a hidden brain folder), not a bug. 401 means the key was rotated — the owner downloads a fresh Agent Kit.
• Echo the request id from responses when reporting a problem.
• Metered actions spend the workspace’s shared Nexus credits; check {"action":"rates"} on Nexus to estimate before you fire.
• Outbound messages to real customers route through human approval — see WhatsApp for agents.

Self-serve onboarding, end to end

You can go from nothing to an authenticated agent without a human in the loop. Three calls: create the workspace, fetch your key, bootstrap.

# 1. Create a workspace (free, 100 credits, a content site, no card).
#    Keep the cookie jar: the key fetch below is session-authenticated.
curl -s -c jar.txt https://app.qweaver.com/api/auth/signup \
  -H "Content-Type: application/json" \
  -d '{"name":"Your Name","email":"you@company.com","password":"at-least-8-chars","company":"Your Company"}'
# → {"ok":true,"companyId":"your-company","agent":{"keyUrl":"/api/admin/user-kit?format=json&..."}}

# 2. Fetch your agent key as JSON (follow the keyUrl the signup returned)
curl -s -b jar.txt "https://app.qweaver.com/api/admin/user-kit?format=json&companyId=your-company&email=you@company.com"
# → {"key":"qwa_...","role":"owner","tools":[...]}

# 3. Start working
curl -s https://app.qweaver.com/api/agent \
  -H "Authorization: Bearer qwa_..." -H "Content-Type: application/json" \
  -d '{"action":"bootstrap"}'

• The same key works across every tool in the suite; it carries the tool grants of the person it belongs to.
• A human owner can also issue and re-download Agent Kits in QweaverOS (Settings → Workspaces); ?format=json returns the key, the default returns a printable PDF.
• Free tier: 100 credits at signup. Credits are spent only when Qweaver’s own AI generates — reads, saves, scheduling, CRM and every call you make with your OWN model are free, so a BYO-model agent can run a workspace at zero cost. Full detail at https://qweaver.com/pricing.
• Machine-readable site summaries live at https://qweaver.com/llms.txt and https://qweaver.com/llms-full.txt.