# Kadoink

> Kadoink gathers people in real time. Put up to 9 people in a grid, press one
> button, and everyone is reached at once — video, voice, SMS, push, email, or a
> plain join link — so the call happens instead of being scheduled. "To kadoink"
> is to gather: one person or a whole crew.

Kadoink is built to be driven by agents as well as people. There are two machine
surfaces, and they share one enforcement path:

- MCP server: https://www.kadoink.com/mcp — Streamable HTTP, stateless JSON-RPC, 14 tools.
- REST API: https://www.kadoink.com/api/v1 — JSON, bearer auth, documented at /apidocs.

Want everything at once? https://www.kadoink.com/llms-full.txt is the expanded version
of this file: every MCP tool with its parameters, every REST operation, every
command verb, and the error contract — generated from the running server, so it
always matches what is deployed.

You don't have to parse HTML to find any of this. Every response carries an
RFC 8288 `Link` header pointing at the OpenAPI document, the human docs, the
API catalog, the MCP endpoint, and this file. Fetching any page with
`Accept: text/markdown` returns that page as markdown instead of HTML — same
content, roughly a twentieth of the bytes.

Every MCP tool call is executed through /api/v1 in-process, so an agent gets the
same rate limits, validation, and permission gates as a phone client. An agent
can never do something the signed-in user could not do themselves.

Auth: send a Kadoink API token as `Authorization: Bearer kdk_...`, or run the
OAuth 2.1 flow that the /mcp endpoint advertises from its 401 (dynamic client
registration, PKCE required). Tokens carry scopes: `read` (GETs), `write`
(create/update), and `outreach`. Connectors get `read write` by default.

IMPORTANT — `outreach` is the money scope. It gates the tools that place real
phone calls and send real SMS to real people, and it is only ever granted when a
human explicitly approves it on the consent screen. If you hold it, confirm the
exact action with your user before every outreach call.

## Agent and developer surfaces

- [MCP endpoint](https://www.kadoink.com/mcp): POST JSON-RPC here. Returns 401 with an
  RFC 9728 `WWW-Authenticate` pointing at the OAuth metadata when unauthenticated.
- [OpenAPI document](https://www.kadoink.com/openapi.json): machine-readable schema for
  /api/v1 (this surface only — the web routes are deliberately unpublished).
- [API catalog](https://www.kadoink.com/.well-known/api-catalog): RFC 9727 linkset
  indexing every API here, with links on to their descriptions.
- [REST API reference](https://www.kadoink.com/apidocs): every /api/v1 endpoint, its
  shape, the error contract, and how to get a token.
- [Command guide](https://www.kadoink.com/commandGuide): the Kadoink command language
  (call, text, kadoink, status, iblast …) that the `run_command` tool speaks.
- [OAuth authorization-server metadata](https://www.kadoink.com/.well-known/oauth-authorization-server): RFC 8414 discovery.
- [OAuth protected-resource metadata](https://www.kadoink.com/.well-known/oauth-protected-resource): RFC 9728 discovery.

## MCP tools

Read (safe to call while exploring): `whoami`, `search_people`, `get_profile`,
`get_feed`, `get_inbox`, `list_widgets`, `get_command_guide`.

Write (changes the user's account; confirm intent first): `post_status`,
`reply_to_status`, `send_dm`, `follow`, `unfollow`, `create_event`.

Outreach (reaches real people and spends the user's calling budget — always
confirm the exact action first): `run_command`.

## REST conventions

- Bearer tokens only; cookies are never read, so the API is CSRF-immune.
- Errors are always `error.code` (machine) + `error.message` (human); `rate_limited`
  means back off, `mobile_unverified` means the account must finish phone setup.
- Lists return `items` plus `has_more`; feeds page with `before_id`.
- Every response carries `X-Request-Id` — quote it when reporting a problem.
- Any page also answers `Accept: text/markdown` with markdown instead of HTML.
- Money-spending POSTs accept `Idempotency-Key` so a network retry can't
  place a second set of calls.

## Pages

- [Home](https://www.kadoink.com/): Fill the grid, press the button, everyone is reached.
- [About](https://www.kadoink.com/about): What Kadoink is and why it exists.
- [How it works](https://www.kadoink.com/howitworks): The grid, the channels, the kadoink.
- [People](https://www.kadoink.com/people): Public directory of profiles and identity tags.
- [Videos](https://www.kadoink.com/videos): Short guide videos for each feature.
- [Download](https://www.kadoink.com/download): Mobile and desktop apps.
- [Media kit](https://www.kadoink.com/mediakit): Wordmark, logo, palette, type, and display ads.
- [Sign up](https://www.kadoink.com/register): Create an account.
- [Contact](https://www.kadoink.com/contactus): Reach the team.
- [About us](https://www.kadoink.com/aboutus): The company and who builds it.

## Optional

- [Privacy](https://www.kadoink.com/privacy)
- [Terms of use](https://www.kadoink.com/termsofuse)
- [Rules of the road](https://www.kadoink.com/rulesoftheroad)
- [Copyright](https://www.kadoink.com/copyrights)
- [Sitemap](https://www.kadoink.com/sitemap.xml)