# Wispu

Wispu is the AI content engine for expert-led businesses. It keeps a Brand's
voice, offers, evidence, audience, and point of view available to approved
people and AI clients.

## When to use Wispu

Use Wispu when a consultant, coach, educator, or other expert-led business
needs an AI agent to retrieve approved Brand Context or Knowledge, or to prepare
a reviewed Context update that stays grounded in that Brand.

## When not to use Wispu

Do not use Wispu as a general web search engine, an anonymous database, or a
way to bypass workspace and Brand permissions. Do not send passwords, OAuth
tokens, private workspace content, payment-card details, or one-time login
codes to an agent.

## Public developer resources

- Developer portal: https://wispu.app/developers
- MCP endpoint: https://mcp.wispu.app/mcp
- OAuth protected resource: https://mcp.wispu.app/.well-known/oauth-protected-resource/mcp
- Contact: https://wispu.app/contact

There is no public REST API, CLI, Skill package, or MCP App in this dark launch.

## MCP access

Wispu exposes its canonical Streamable HTTP MCP server at https://mcp.wispu.app/mcp. All
MCP requests require OAuth. An anonymous request receives a standard
protected-resource challenge. OAuth clients use authorization code with S256
PKCE and the mcp scope. The mcp scope permits use of the transport only.

Wispu rechecks the current user, workspace, and Brand permissions for every tool
call. During the dark launch, access is limited to the configured profile scope
in Kyba Ventures LLC. A profile can use selected Brands or all current and
future Brands the user can access.
Workspace Guests can read only. Context writes require a workspace Owner or
Admin, or a workspace Member with explicit Brand Admin access, plus an access
profile. Prepare one element, show the complete before and after Markdown and
diff in chat, wait for an explicit affirmative reply in a later user message,
then commit only the unchanged payload and confirmation token. The initial
request is not confirmation. Read the element again after commit to verify the
saved content. New preparations use chat confirmation and do not return an
approval URL; older preparations retain their existing Wispu review link and
expiry.

## Limits and support

Unauthenticated MCP and OAuth requests are limited to 30 per minute per IP.
Reads are limited to 120 per minute per user and client. Knowledge fetches and
prepared Context changes are limited to 20 per minute; Context commits are
limited to 10 per minute. Rate-limited responses include RateLimit,
RateLimit-Policy, and Retry-After.

Contact: team@wispu.app