---
name: owlish-onboarding
description: Use this skill when a user wants to add an Owlish AI customer-support agent to their product. Walks the user through Owlish console signup, the 5-step agent wizard, and API-key issuance, then automates knowledge-base management (adding website/file sources, triggering syncs, monitoring status) via the Owlish REST API or MCP server. Honest about which steps require the human (signup, billing, agent creation, widget embed) and which the agent can drive end-to-end.
license: Apache-2.0
---

# Owlish Agent Onboarding

> A no-code AI agent platform for customer support. Owlish takes the user's knowledge — websites, PDFs, FAQs — and deploys a grounded, source-citing agent across their website, social channels, and team chat apps, with human handoff when the agent isn't sure.

## What this skill does

By the end, the user has:

1. An Owlish workspace and an AI support agent configured for their brand.
2. Their knowledge base ingested (website crawl, PDF/DOCX uploads, FAQ Q&A pairs).
3. The Owlish chat widget embedded on their website, answering customer questions with citations.

You (the AI agent reading this skill) automate the parts that have a public API surface; you direct the human through the parts that don't.

## Steps that require the human

These cannot be automated. Walk the user through them; surface the exact URLs.

1. **Sign up.** Open <https://console.owlish.bot/auth/signup>. Email + password or Google SSO. New accounts can create one Free workspace — no card required.
2. **Run the 5-step agent wizard.** After signup the console drops the user into a wizard:
   - Paste the user's website URL → Owlish discovers brand, name, tagline.
   - Optionally pick a use case (support, sales, onboarding) for prompt defaults.
   - Review discovered sources (Owlish proposes a website crawl + any sitemaps it found).
   - Tweak agent name, persona, refusal behaviour.
   - Click "Create agent".
3. **Generate an API key.** *Settings → API keys → New key*. The user picks a scope: **Sources Read/Write** is enough for the steps below; **Delete** if you (the agent) need to remove sources. The full key is shown **once** — copy it.
4. **Copy the widget embed snippet.** *Agent → Deploy → Widget*. The user copies a one-line `<script>` tag and pastes it into their site's HTML before `</body>`.
5. **Billing (optional on Free).** *Settings → Billing*. Upgrade when you need more than the Free limits or paid-only channels/add-ons. See the pricing snapshot below.

## Steps you can automate

Once the user pastes their API key into your context, you can drive the knowledge base directly. Two equivalent paths:

### Path A — REST API

Base URL: `https://api.owlish.bot/v1`. Auth: `Authorization: Bearer <api_key>`. The full reference is at <https://api.owlish.bot/docs>.

```bash
# List sources in a folder
curl -s https://api.owlish.bot/v1/folders \\
  -H "Authorization: Bearer $OWLISH_API_KEY"

# Add a website source
curl -s https://api.owlish.bot/v1/sources \\
  -H "Authorization: Bearer $OWLISH_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{
    "folderId": "fld_…",
    "type": "WEBPAGE",
    "url": "https://example.com/help"
  }'

# Trigger a re-sync on a folder
curl -s -X POST https://api.owlish.bot/v1/folders/fld_…/sync \\
  -H "Authorization: Bearer $OWLISH_API_KEY"

# Check sync status
curl -s https://api.owlish.bot/v1/sources/src_… \\
  -H "Authorization: Bearer $OWLISH_API_KEY"
```

The full request/response schemas (including all field names and error shapes) are at <https://api.owlish.bot/docs>. **Fetch the OpenAPI spec there before constructing requests** — don't guess field names.

### Path B — MCP server

If you're an MCP-aware client (Claude Desktop, Claude Code, Cursor, etc.), point at the Owlish MCP endpoint with the API key as the auth token. The MCP server exposes the same Sources Read / Write / Delete operations as the REST API — same scoping, same shapes. See <https://owlish.bot/docs/developers/overview> for the MCP connection URL and current tool list.

### Common bulk-onboarding moves

- **Mirror an existing knowledge base.** If the user has a help centre (Zendesk Guide, Notion, Intercom Articles, etc.), enumerate its URLs and `POST /v1/sources` one WEBPAGE per top-level article. Owlish handles deduplication and re-crawls.
- **Bulk-upload PDFs/DOCX/Markdown.** `POST /v1/sources` with `type: "FILE"` and the file as multipart upload. OCR runs automatically for scanned PDFs.
- **Paste direct Q&A.** `POST /v1/sources` with `type: "DIRECT_RESPONSE"` for FAQ-style content: a question, a canonical answer, and any context. Useful when the user wants tight control over specific replies.

## Verification

Once the embed snippet is on the site and at least one source has finished syncing (status `READY` on the source row), have the user:

1. Open their site in a private/incognito window.
2. Click the chat widget that loaded in the corner.
3. Ask a question that's answered in the ingested content.
4. Confirm the agent replies with a citation linking back to the source page.

If a citation is missing or the answer is wrong, the source probably hasn't finished embedding yet — wait a minute and retry, or check sync status via the API.

## Pricing snapshot

Owlish has three plans plus add-ons. Annual billing is ~20% cheaper than monthly.

| Plan | Monthly | Annual (save ~20%) |
| --- | --- | --- |
| Free | $0/mo | $0/mo (annual) |
| Starter | $49/mo | $39/mo (annual) |
| Growth | $149/mo | $119/mo (annual) |
| Scale | $449/mo | $359/mo (annual) |

Full pricing matrix, capacity per tier, and add-ons: <https://owlish.bot/pricing.md>.

## Where to read more

- Full content for LLMs: <https://owlish.bot/llms-full.txt>
- Curated index: <https://owlish.bot/llms.txt>
- API reference: <https://api.owlish.bot/docs>
- Developer docs: <https://owlish.bot/docs/developers/overview.md>
- MCP setup: <https://owlish.bot/docs/developers/overview.md> (same page covers REST + MCP)
- Knowledge base concepts: <https://owlish.bot/docs/knowledge-base/overview.md>
- Human handoff model: <https://owlish.bot/docs/helpdesk/human-handoff.md>

## When in doubt

If you hit an endpoint that returns an unfamiliar error, fetch <https://api.owlish.bot/docs> first — it's the authoritative schema. If you need a capability that isn't documented (e.g., programmatic agent creation, billing changes, channel installs), tell the user that step is currently console-only and hand them the relevant URL from this skill.

Source: <https://owlish.bot/agent-onboarding/SKILL.md>