Getting help¶
Support is async and email-only. There is no live chat, no phone line, and no 24/7 human response. Most answers are faster than an email — the platform is built so that errors are actionable and this knowledge base resolves on the exact string you saw. Work the self-serve path first, then escalate by email.
1. Is it down? Check the status page¶
The public status page is external and shows live service state:
- Status: https://status.aetelier.xyz
Check it first for any "is it down / is this an outage" question. If an incident is posted there, the fix is to wait for it to clear — email will not speed it up.
2. Search your exact error first¶
Each documented error string is quoted verbatim on its page. Paste the string into
the docs search, or fetch the page's Markdown directly (append .md to any docs
URL). Common ones:
| You saw | Start here |
|---|---|
insufficient DATA token balance / insufficient COMPUTE token balance |
Units and the 402 error |
this fit costs {cost} compute tokens |
Units and the 402 error |
managed agents are not included in the {tier} tier |
Feature access |
live reconciliation requires the Pro tier or higher |
Feature access |
concurrent-collector cap reached |
Feature access |
Not converged after {iterations} iterations (a fit 400) |
MCP errors are data |
| Deployed but no data landing | Collector: no data |
| A top-up not credited (top-ups are not open yet) | Payment not credited |
Any API error with a code field |
Error-code index |
If a search returns nothing: we document what is live, so a capability you cannot find most likely does not exist yet — check Platform limits for the enforced boundaries. Email us and we will say plainly whether it exists, is planned, or is out of scope.
3. For agents: platform_health first, then the Markdown¶
An agent should triage before it asks a human:
- Call
platform_healthfirst — it reports each backing service asok, or why it is not. - Read errors as data. Every machine-side failure maps to an in-loop action; see MCP errors are data, not failures.
- Fetch the whole documentation set in one request:
https://aetelier.xyz/docs/llms-full.txt. Any single page's source is fetchable by appending.mdto its URL.
4. Ask the community¶
Community links, for usage questions, ideas, and talking to other builders, appear only inside your dashboard under Settings → Community (see Official channels).
Community channels follow the same async response targets as email (see the support policy). Anything touching your account, billing, a payment, an API key, or personal data is handled only over email — we will never resolve those in a community thread.
5. Still stuck? Email us¶
If the status page is clear, the error page did not resolve it, and platform_health
reads ok for every service, email support:
- Email: [email protected] — the system of record, and the only channel for account, billing, refund, and data-subject requests. Report a security issue privately, by email or through a public repository's Security tab on GitHub, never in a public thread.
- Hours and targets: Monday–Friday, 09:00–18:00 America/Mexico_City; replies come within business hours. Severity definitions and first-response targets are in the support policy.
- Include: what you did, the exact error string and any
code, anyservice_idorfit_id, and the approximate time (with timezone). Once top-ups open, add a top-up'smemo, transaction signature and network. - Never send your API key, wallet private key or seed phrase. Support never needs them.
The more of that you include, the faster a single async round-trip resolves it.