Support policy¶
This page is the single published source for response targets. The Terms of Service reference it; no other page restates these numbers.
What a response target measures¶
A response target is the time to first human acknowledgment and the start of triage — not the time to resolution. We do not commit a resolution time during beta; resolution is best-effort and worked in priority order. Acknowledgment clocks run only during published support hours; a message arriving outside those hours starts its clock at the next opening.
Support hours¶
Human support operates Monday–Friday, 09:00–18:00 America/Mexico_City, excluding Mexican public holidays and any reduced-coverage dates announced on the status page. Outside those hours, automated monitoring and the public status page remain live continuously; human replies resume at the next opening.
Human support is by email at [email protected]. What to include is in Getting help.
Severity and response targets¶
Every account shares one table and one queue during beta.
| Severity | Definition | First-response target (business hours) |
|---|---|---|
| P0 | Platform-wide outage, data loss, or a security incident | Within 4 business hours; status posted on detection, 24/7 |
| P1 | Major degradation affecting many accounts, or a fault that hard-blocks one account's collectors, fits or swarms | Within 1 business day |
| P2 | Single-account, non-catastrophic: a payment or access question, one silent collector, one non-converging fit | Within 2 business days |
| P3 | General and pricing questions, non-blocking bugs, feature requests, docs feedback | Within 3 business days |
What runs around the clock¶
24/7 automated monitoring and a public status page; human response during support hours.
Expected behavior is not an incident¶
A 402 with insufficient DATA token balance or
insufficient COMPUTE token balance, an access gate such as
live reconciliation requires the Pro tier or higher, and
concurrent-collector cap reached are the platform enforcing your unit
balance and your account's access — the action was refused, not charged.
Top-ups are not open yet, and gated features are open to selected accounts;
Units and the 402 error and Feature access give the
next step for each. Once top-ups open, a top-up that stays uncredited is the
case that belongs in email:
I paid but my units are not credited says when to
send it and what to include.
Payments and refunds¶
- Units are prepaid, non-transferable service credits, not money.
- Top-ups are not open yet: the public top-up status reads
disabled, shown as OPENS SOON. They open first on Solana devnet, for listed testers only (OPEN · DEVNET); mainnet comes later. Every status word is in Top-ups over x402. - Once open, top-ups are paid in USDC on Solana from your own wallet over x402 v2. Coinbase Developer Platform, as facilitator, verifies and settles each payment. Aetelier never receives or stores wallet keys, and support never needs them.
- Bundle purchases are final except where the law requires a refund (Terms of Service §6). Send refund requests to [email protected] as described in Refunds.
How these targets are bounded¶
These response targets are operational objectives, not contractual guarantees, and do not modify the Terms of Service. A missed target earns no service credits during beta (Terms of Service §9).
Related¶
- Getting help — the escalation path itself
- Official channels — where we are, and where we are not
- Units and the 402 error — what units fund, and how top-ups will work
- I paid but my units are not credited — receipts by memo, and refunds