NewThe Claude Code plugin is in beta

Docs, support and AI answers for teams that ship

A help center, an AI agent and a shared inbox, built on the docs you already write. Embed the agent in two lines, and let your coding agent draft articles from your pull requests.

Join the beta Read the API docs

Private beta · Free for 14 days

index.html

<!-- the AI agent, answering from your docs -->
<script src="https://app.sapanbase.com/widget.js"></script>
<script>
  SapanBase.init({ companyId: "sapancal" })

  // optional: tell it who is asking
  SapanBase.identify({ userId: user.id, email: user.email,
    hmac: "hmac-sha256…" })
</script>

$ claude
> /sapanbase:draft-articles

● Reading PR #482 · Add availability buffers
● 2 articles mention availability
✓ Drafted "Set working hours and buffers"
✓ Updated "Query free/busy across calendars"

  2 drafts are waiting for review in SapanBase

$ curl https://api.sapanbase.com/v1/articles \
  -H "Authorization: Bearer $SAPANBASE_KEY" \
  -d title="Rotate an API key" -d status=draft

{
  "id": "art_8f2k",
  "status": "draft",
  "url": "https://help.sapancal.com/rotate-an-api-key"
}

Works withGitHubLinearClaude CodeCursorOpenAPIAny MCP client

Product

Everything support needs, on one set of docs

Your help center, AI agent, inbox, developer docs and changelog share the same articles, customers and search. Fix a doc once and every part of support gets the fix.

help.sapancal.com

Help center

Semantic search, a block editor, your domain and your brand. Run separate help centers for product, developer and internal docs.

Learn more →widget.js

AI agent

Answers from your articles and links the one it used. Two lines to embed, and it hands off to a person when it should.

Learn more →inbox

Inbox

Email, chat hand-offs and forms in one thread, with contact history and two-way Linear sync for bugs.

Learn more →openapi.yaml

Developer docs

A versioned API reference generated from your OpenAPI file, in the same search as your guides.

Learn more →/changelog

Changelog

Publish release notes in your help center or on their own domain. Draft ahead and ship when you do.

Learn more →github

Docs that keep up

Merged pull requests flag the articles they change, with a suggested rewrite waiting as a draft.

Learn more →

Docs that keep up

Your product ships. Your docs keep up.

Docs don’t go stale all at once. They drift one merged pull request at a time. Connect GitHub and SapanBase checks every merge against your help center.

01A pull request merges into main
02Articles that describe the changed behaviour are flagged
03A suggested rewrite waits as a draft. A person publishes it.

PR #482 merged · Add availability bufferssapancal/api · 14 files

Set working hours and buffersUpdate suggested

Use the hosted connect pageStill current

Query free/busy across calendarsUpdate suggested

- Availability uses your working hours.

+ Availability uses your working hours,

+ minus the buffers around each event.

SapanCal supportAnswers from SapanCal’s docs

How do I read free/busy?

Call GET /v1/free-busy with a connection_id, start and end, and we’ll return the busy blocks in the time zone you ask for.
Query free/busy across calendars

And can I cache it for an hour?

The docs don’t cover caching free/busy, so I’ve passed this to the SapanCal team with our chat attached. They usually reply within a few hours.
Handed off to the team

AI agent

Answers from your docs. With a source on every one.

The agent searches your published articles, answers in your tone and links the article it used. When the docs run out, it says so.

Cites every answer. Customers can check the source, and you can see which article did the work.
Hands off cleanly. Escalations land in your inbox with the transcript and the articles it tried.
Stays on budget. A monthly AI budget you set, enforced on our side. No surprise bills.

See the AI agent →

Inbox

One inbox for email, chat and forms

Every channel lands in the same shared inbox. Hand-offs from the AI agent arrive with the transcript, every customer has a history, and bugs go to Linear and back.

Billed for a deleted connectionNeeds youUnassigned

Priya · via chat

We deleted a connection on 2 October but it's still on our invoice. Can we get a credit?

AI agent

Sorry about that. Billing changes need someone on the SapanCal team, so I've passed this on with our chat attached. You'll hear back by email.

Tried: Per-connection billing · Delete a connection

Private note · Sam

Checked Stripe, the deleted connection is still counted. Mia, can you credit it?

Hi Priya, thanks for flagging this. I can see the connection was deleted on 2 October…

Priya N.priya@northwind.io

PlanPro

Customer sinceMarch 2024

Conversations4

Came in byAI hand-off

Every channel, one thread

Email replies thread properly, and chat hand-offs and form submissions arrive in the same list.

Context travels with them

Each customer has a profile with their plan and every past conversation, so nobody starts cold.

Bugs go to Linear and back

Turn a conversation into a Linear issue in one click. When it’s fixed, the customer hears back.

For your agents

Your coding agent can write the docs too

Connect Claude Code, Cursor or an agent you built yourself. It reads what you have published and drafts what has changed.

MCP server

Any MCP client can search your published docs and draft articles, changelog entries and doc updates.

// .mcp.json
{
  "mcpServers": {
    "sapanbase": {
      "url": "https://mcp.sapanbase.com"
    }
  }
}

Claude Code plugin

Point Claude at a branch or pull request and it drafts the article, release note or API doc update.

> /sapanbase:draft-changelog

● Reading 6 merged PRs since v2.3
✓ Drafted "v2.4 · Faster search"

  Waiting for review

API and webhooks

Everything in the dashboard has an endpoint. Signed webhooks tell you when anything changes.

# signed with HMAC-SHA256
article.published
article.updated
support_request.created
support_request.updated

Pricing

One plan for the whole workspace

Not a stack of add-ons. Every plan includes the API, webhooks, the MCP server and a monthly AI budget.

Starter

Docs and AI drafting for a small team.

$29 /mo

1 help center
AI writing help in the editor
API, webhooks and MCP

Join the beta

Pro

Enterprise

No limits and a custom AI budget.

Custom

Unlimited help centers
Unlimited seats
Custom monthly AI budget

Join the beta

Initial beta pricing. If prices come down, beta members get the lower price. Compare plans →

FAQ

Questions, answered

What is SapanBase?

A help center, an AI agent, a shared inbox, developer docs and a changelog in one workspace. They all run on the same articles, customers and search, so fixing a doc once fixes it everywhere.

Is it live yet?

We're in private beta. The product is real, and we're onboarding teams in small batches so we can work closely with each one. Join the beta and we'll reach out as spots open; new ones free up every week.

Can I bring my existing help center across?

Today you can import from Help Scout and Notion, with your articles, structure and images. More sources are on the way. We don't import from Zendesk or Intercom yet.

How does the AI agent avoid making things up?

It only answers from the docs you publish, using the same semantic search as your help center, and it links the article behind every answer. If your docs don't cover a question, it says so and hands off to your team.

Can my coding agent write docs?

Yes. Connect Claude Code, Cursor or your own agent through the MCP server, or use the Claude Code plugin. Agents can read published docs and write drafts. Only a person can publish.

Ship docs like you ship code.

Point SapanBase at your docs and your help center, AI agent and inbox are live in an afternoon.

Join the beta Read the docs

Private beta · Free for 14 days · New spots every week