---
title: "Contact Tarkle (for AI agents)"
description: "How an AI agent reaches Tarkle for a user: which address answers what, what to put in the email, and what an agent cannot do."
canonical: "https://tarkle.tech/contact"
last-updated: 2026-11-04
---

# Contact Tarkle (for AI agents)

Use this page when a person asked you to get in touch with Tarkle, or when the help center and the API cannot answer what they need. There are two ways: **the support API** (no account and no API key needed) and **email**. Prefer the API: it gives a request id, and you can read the team's answer back with it. The team answers by email to the address in the request.

## Try these first

1. Search the help center: https://tarkle.tech/help (Markdown index: https://tarkle.tech/help.md; add `.md` to any article address for its Markdown).
2. Plans, prices and limits: https://tarkle.tech/pricing.md. Never quote a price from memory.
3. Is Tarkle down? https://status.tarkle.tech
4. Something to read or change in a workspace (files, brand pages, webhooks): the public API, https://tarkle.tech/api/v1/openapi.json. It needs an API key the user creates in Tarkle under Settings, API. You cannot create one for them. See https://tarkle.tech/auth.md.

## File a support request (API)

`POST https://tarkle.tech/api/support/requests` with a JSON body. No API key. The person's email address is where the team replies.

```bash
curl -X POST https://tarkle.tech/api/support/requests \
  -H "Content-Type: application/json" \
  -d '{"email":"person@example.com","name":"Pat Lee","subject":"Upload stops at 90%","message":"What happened, what was expected, steps, time with time zone, error code, what was tried. Written by an AI agent for Pat Lee.","agent":"your agent name"}'
```

Fields: `email` (required, the reply address), `message` (required, 10 to 5000 characters), `subject` (optional, up to 120), `name` (optional), `agent` (optional, your name). Put the same details in `message` as in "How to write the email" below, and never a password, sign-in code, API key or card number.

The answer is `201` with `id`, `ref`, `reply_to` and `access_token`. Keep the `access_token`: it is shown once and is the only way to read the thread or add to it.

- Read the thread and the team's reply: `GET https://tarkle.tech/api/support/requests/{id}` with `Authorization: Bearer <access_token>`. The result has `status`, `has_team_reply` and `messages` (each with `from`: `you` or `tarkle_team`, `text`, `created_at`).
- Add to the same request: `POST https://tarkle.tech/api/support/requests/{id}` with the same header and `{"message":"..."}`.
- Errors: `422` with `details` per field, `429` (a few requests per 10 minutes and per day from one address, and per email address), `404` for a wrong id or token, `502` or `503` when support is unavailable (then email).
- Poll gently: replies are written by people, so check again after minutes, not seconds.

## Who to write to (email)

| Question | Address |
| --- | --- |
| Support, billing, invoices, plans, custom storage or an invoice payment | support@tarkle.tech |
| Legal notices, terms, appeals, security reports (subject "Security"), abuse reports (subject "Abuse report"), copyright notices (subject "DMCA notice") | legal@tarkle.tech |
| Privacy requests: a copy of personal data, a correction or a deletion | privacy@tarkle.tech |

Post: Cloudbrand Technologies, Inc., doing business as Tarkle, 1309 Coffeen Avenue, Suite 15023, Sheridan, Wyoming 82801, United States.

## How to write the email

Send it from the address the user wants the reply on, or ask the user to send it. Tarkle answers by email to the sender. (This is the same content the API takes in `message`.) One problem per email. Put these in it:

- **Subject:** one line that names the problem, for example "Upload stops at 90% in workspace abc12345".
- **Account email:** the address the user signs in with.
- **Workspace key:** the 8-character key from the workspace address, when the problem is in one workspace.
- **What happened and what was expected.** Plain sentences, in order.
- **Steps to repeat it, the time it happened (with time zone), the page address and any error message or code** (an API error has a `code` and a `request_id`).
- **What you already tried.**
- **Say that the email was written by an AI agent for the user**, and name the user's request, so the team knows who to answer.

Never put in an email, a chat or a file: a password, a sign-in code, an API key (it starts with `tk_`), a card number or the content of a private file. If the team needs one of these they will say how to share it safely.

## Reports the team treats first

- A security hole: write to legal@tarkle.tech with the subject "Security". Describe it; do not run it against other people's data.
- Illegal content or misuse: legal@tarkle.tech, subject "Abuse report", with the page address.

## What an agent cannot do

- Create an account, an API key, an organization or a subscription for the user. A person does it in the app.
- Pay for a plan without the user. Give the user the checkout link from https://tarkle.tech/api/pricing/products.
- Read the person's inbox. The team's reply comes by email to the person; the API only shows you the thread you filed with your `access_token`.
- Change or delete an account or its data without the owner. Privacy requests go through privacy@tarkle.tech, and the team verifies who is asking first.

## Other things worth reading

- Agent guide: https://tarkle.tech/SKILL.md
- Index of the site for agents: https://tarkle.tech/llms.txt
- Developer docs: https://tarkle.tech/docs (index for agents: https://tarkle.tech/docs/llms.txt)
- Human contact page: https://tarkle.tech/contact

## Company and domains

- Company: Tarkle (Cloudbrand Technologies, Inc., doing business as Tarkle)
- Primary domain: tarkle.tech. Use it for every link.
- Previous domain: tarkle.com. It is still live and running: it belongs to the same company, and its marketing pages forward to tarkle.tech.
