Tamloot Developer Resources
Everything you need to build on Tamloot: a read-only public REST API, an OAuth-secured MCP server, and one auth walkthrough that covers both.
Tamloot Public API
A read-only REST API over the contacts, sessions, transcripts, and notes in a Tamloot account. Authenticate with a bearer API key minted under Settings → API.
Tamloot MCP Server
An OAuth-secured Model Context Protocol server over Streamable HTTP, so Claude, ChatGPT, Cursor, and other MCP clients can read a signed-in user’s own Tamloot data.
Tamloot Agent Authentication
How an agent discovers, registers for, and uses a credential on either surface — written as a prose walkthrough at /auth.md.
Machine-readable descriptions
Fetch the API surface without scraping a page: an OpenAPI 3.1 description, an RFC 9727 API catalog, and llms.txt as the site index for agents.
Rate limits
Every Tamloot Public API response declares the throttling policy, so a client can pace itself rather than discover the ceiling by hitting it. There is no RateLimit-Remaining: the throttle is enforced at the edge, ahead of the application, so no single server can see a caller’s running total.
| Header | Meaning | Sent on |
|---|---|---|
| RateLimit-Limit | Requests allowed per one-second window | Every response |
| RateLimit-Policy | The policy, as <limit>;w=<window seconds> | Every response |
| Retry-After | Seconds to wait before retrying | 429 only |
Every page linked here also answers in markdown. Send Accept: text/markdown, or append the path to /md — for example /md/en/developers.