Tarkle Docs cover what you can build on Tarkle: the API, the MCP server and the AI tools. Pages are grouped by what you want to do. Each product area has a page, even where the API for it does not exist yet, so you can see where it will live and what is available today.
If you want to learn how to use Tarkle as a customer, read the help center.
Start here
Quickstart
Create an API key, list your workspaces, upload a file and download it again.
Authentication
API keys, workspace keys and which workspaces a key can reach.
Core concepts
Organization, workspace, library and API key in plain words.
MCP server
Connect an AI assistant to your Tarkle workspace.
rclone (beta)
Sync files between a computer or server and Tarkle with rclone.
What you can build with
| Product area | What it is | In the API today |
|---|---|---|
| Cloud storage | Files and folders in a workspace library | Yes |
| Brands | Brand pages with logos and download requests | Yes |
| File transfer | Send files by link | Not yet |
| Transfer pages | The page recipients open | Not yet |
| File requests | Collect files from other people | Not yet |
| Feedback | Review and approve files | Not yet |
| Contacts | People you work with | Not yet |
| Client portal | A branded home for each client | Not yet |
| Organization | The account that owns plans and workspaces | Workspace list only |
| Teams | Members, roles and access | Not yet |
| Domains | Your own domain and white label | Not yet |
| Billing and usage | Plans, storage and limits | Storage use only |
| Integrations | Slack and MCP | MCP only |
“Not yet” means the product feature exists in Tarkle but has no public API endpoints. The API reference shows the status of each area.
Reference
- API overview: base URL, headers and versions.
- Errors: every error is an RFC 9457 problem document with a stable code.
- Paging and limits: cursors, rate limits and idempotency.
- AI agents: Markdown pages,
llms.txt, the OpenAPI file and agent skills.