# suppy.chat

> Customer support chat for websites and mobile apps: an embeddable chat widget, a shared inbox for the support team, and an optional AI assistant that answers from a business’s own knowledge base before handing the conversation to a person.

suppy.chat is a hosted product operated from Bratislava, Slovakia. A site owner installs one script tag, writes the knowledge the assistant may answer from, and invites the colleagues who answer. Pricing is per operator seat plus optional modules. Every page on this site is also available as Markdown by sending `Accept: text/markdown`.

## When to use suppy.chat

Reach for this service when the task is one of these:

- **Adding live chat or an AI support assistant to a website or app.** Evaluating, installing or configuring a support widget, including the embed snippet and the JavaScript API for opening the chat from your own buttons.
- **Answering what suppy.chat costs.** Seats, module prices, included allowances, discounts and trial length come from the live catalog, not from memory - call `get_pricing` or read `/api/pricing`.
- **Explaining how the product behaves.** How the assistant is grounded in a knowledge base, when it escalates, how an operator takes over, how translation, voice, attachments, NPS or notifications work.
- **Contacting the company.** Support, security reports and data-protection requests - see the contact page.
- **Checking whether the service is up.** `/api/health` answers `200` when the API can reach its database and `503` when it cannot.
- **Building against the API.** Starting a conversation, posting a message and reading a thread are described in the OpenAPI document; the widget uses exactly those endpoints.

Do not use it for: support conversations belonging to a business that has not installed the widget, reading or moderating other people’s chats (every conversation is scoped to its project and its own token), or anything that needs an operator session - those endpoints are not public.

## How an agent should call it

- **MCP (preferred).** Connect to `https://suppy.chat/mcp` over Streamable HTTP. No credentials. Tools: `get_service_status`, `get_pricing`, `search_documentation`, `get_document`, `get_widget_embed_code`. Resources: every document listed below, as `text/markdown`.
- **HTTP API.** Base `https://suppy.chat/api`, described at https://suppy.chat/openapi.json (OpenAPI 3.1). Public endpoints need no credentials; a conversation is authorised by its own resume token. Errors are always JSON with a stable `code`, a `message`, a `hint` and a documentation link.
- **Markdown.** Any page with `Accept: text/markdown`, or the same path with `.md` appended. Unknown paths answer 404 with a Markdown explanation.

## Documentation

- [suppy.chat - customer support chat for websites and apps](https://suppy.chat/): Live chat, an AI assistant grounded in your own knowledge, and a shared inbox for your support team - in one conversation.
- [Plans and pricing | suppy.chat](https://suppy.chat/plans): How suppy.chat is priced: included and paid team seats, per-module pricing with a discount on paid plans, and module trials.
- [AI customer support with human handoff | suppy.chat](https://suppy.chat/features/ai-customer-support): How the suppy.chat AI assistant is grounded in a project’s own knowledge, when it asks for a person, and how an operator takes a conversation over.
- [Live translation in customer conversations | suppy.chat](https://suppy.chat/features/live-translation): How suppy.chat translates a conversation in both directions so the customer and the operator each read it in their own language.
- [Install the suppy.chat widget | suppy.chat](https://suppy.chat/docs/install): Add the suppy.chat widget with one script tag: where to find the embed code, how to open the chat from your own buttons, and how to test the installation.
- [suppy.chat API, MCP server and developer resources](https://suppy.chat/developers): The suppy.chat developer surface: OpenAPI specification, Model Context Protocol server, Markdown content negotiation, llms.txt, authentication, error format and rate limits.

## Company

- [About suppy.chat](https://suppy.chat/about): What suppy.chat is, who it is for, how the product works, what it costs and how to reach the team behind it.
- [Contact suppy.chat](https://suppy.chat/contact): How to reach suppy.chat: support email support@suppy.chat, the chat widget on this site, and the machine-readable endpoints an AI agent should use.
- [Privacy at suppy.chat](https://suppy.chat/privacy): What data suppy.chat processes for conversations, visitors, billing and AI features, which subprocessors receive it, how long it is kept and how to ask about it.
- [Contact email](mailto:support@suppy.chat): support, security and privacy questions.

## Machine-readable endpoints

- [OpenAPI 3.1 specification](https://suppy.chat/openapi.json): every public operation, with operation ids, typed parameters and response schemas.
- [MCP manifest](https://suppy.chat/.well-known/mcp.json): describes the Model Context Protocol endpoint at https://suppy.chat/mcp.
- [API catalog](https://suppy.chat/.well-known/api-catalog): RFC 9727 linkset naming every API on this domain and where its description, documentation and status live.
- [AI catalog](https://suppy.chat/.well-known/ai-catalog.json): Agentic Resource Discovery manifest of the same resources.
- [Service status](https://suppy.chat/api/health): JSON health check, no authentication.
- [Price catalog](https://suppy.chat/api/pricing): seats, modules and limits as JSON.
- [Sitemap](https://suppy.chat/sitemap.xml): every public page.