Tawak developer portal

A public, read-only API and two MCP servers. No API keys, no sign-up.

Everything Tawak publishes about itself is available programmatically: the app's metadata, its pricing, its feature list, and every document it publishes for agents. The API is read-only and needs no credentials, so you can call it right now.

Quickstart

No key is required. Send a plain GET:

curl https://www.tawak.app/api/v1

That returns the service descriptor: the full endpoint list, the authentication posture, the versioning policy, and the error format. From there:

curl https://www.tawak.app/api/v1/app
curl https://www.tawak.app/api/v1/pricing
curl https://www.tawak.app/api/v1/features?category=Prayer
curl https://www.tawak.app/api/v1/docs
curl https://www.tawak.app/api/v1/docs/llms

Tawak API endpoints

Method	Path	Returns
`GET`	`/api/v1`	Service descriptor and endpoint list
`GET`	`/api/v1/health`	Liveness probe
`GET`	`/api/v1/app`	App name, bundle identifier, platforms, price, store URLs
`GET`	`/api/v1/pricing`	Machine-readable pricing. Tawak is free
`GET`	`/api/v1/features`	Feature list, optionally `?category=`
`GET`	`/api/v1/docs`	Published documents, cursor-paginated
`GET`	`/api/v1/docs/{slug}`	One document in full

The complete machine-readable description is the OpenAPI specification.

Authentication

None is required, and none is possible. Every endpoint is public, read-only, and returns the same data to everyone, so there are no API keys to issue and no OAuth flow to complete. Do not send an Authorization header; it has no effect. See auth.md for the full posture.

Sandbox

No separate sandbox exists, because it is not needed: this API has no write surface. There is nothing to damage, so the live endpoints are safe to call freely while you build.

Errors

Every response is JSON, including every error, because an agent that cannot parse a failure cannot recover from one. Failures share a single shape with a stable machine code, a message, and a hint that says what to do next.

{
  "error": {
    "status": 404,
    "code": "not_found",
    "message": "No document matches slug \"nope\".",
    "hint": "Call GET /api/v1/docs for the list of 8 valid slugs.",
    "documentation": "https://www.tawak.app/developers"
  }
}

Tawak MCP servers

Two stateless MCP servers over Streamable HTTP, both public and unauthenticated. They answer both the current (2026-07-28) and legacy (2025-11-25, 2025-06-18) protocol eras.

Server	Endpoint	Tools
Product	`POST /mcp`	get_download_link, get_app_features, get_pricing, get_app_metadata
Documentation	`POST /mcp-docs`	search_docs, get_doc, list_docs

curl -s https://www.tawak.app/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tawak discovery documents

/openapi.json, the OpenAPI 3.1 specification
/llms.txt, the short index for language models
/llms.md, the full agent overview
/pricing.md, pricing in markdown. Tawak is free
/auth.md, the authentication posture
/.well-known/api-catalog, the RFC 9727 resource catalog
/.well-known/mcp/server-card.json, MCP server card
/sitemap.xml, every indexable page

Contact

Questions, bug reports, and suggestions are welcome at tawakapp@gmail.com.