Credits and billing
One balance, spent by the desktop and the API alike. A plan grants credits monthly; they are spent when a job is admitted and returned when it fails. If a charge and a failure do not line up, that is a bug and we want the job id.
Help
Tell us what happened.
Most questions are answered below. Anything else reaches our support team, and we reply by email.
Answers
Start with the answer
Each one is a topic the form offers. “Write about this” opens the form with that topic already chosen.
A generation failed
A failed job is refunded automatically — including one refused for prohibited content, which is a refusal rather than a charge. If the credits have not come back within an hour, send us the job id and we will look at the ledger rather than guess.
Plans and limits
Rate limits are per key and per account, and every refusal names itself: a 429 carries the bucket that answered and the seconds until it refills. There are 353 error codes and each one is documented with what to do about it.
API keys and the desktop app
A key is shown once, at creation, and is stored as a hash — we cannot read it back, so a lost key is replaced rather than recovered. Never paste one into this form: we strip it before storing, but treat a pasted key as leaked and revoke it yourself in Account → API Keys. Our support team revokes it too if it is still live, and the reply tells you so.
Account, data and deletion
Everything you make and upload is deleted seven days after it was made, account or no account. Deleting your account (Account → Profile & Security → Danger Zone) deletes its uploads and results within minutes, stops a paid-up subscription renewing and cancels one that is not paid up; the account itself goes after the grace period shown before you confirm, and signing in before then keeps it and turns back on the renewal the deletion stopped, if the subscription has not ended in the meantime. Unspent credits are forfeited, those bought in credit packs included, and content held after a report, or by our team, is kept as evidence until its hold ends. You can also write from the address on the account and say so plainly: we confirm before anything is removed, and the same steps run.
Report content
Report anything generated on this platform that should not have been. Reports are read by a person, not a filter, and the fastest report is the one carrying the job id or the asset link.
What a refused, failed, stopped or stalled job does to your credits, product by product
Already written to us?
Every request has a page of its own. Give us the address you wrote from and we will email the link there again.
Write to us
Nothing above fits?
Write to us. This is what happens after you press Send.
- 1
One email confirms it
Each request is confirmed by one email to the address you give.
- 2
We answer by mail
After that we answer by mail, and a reply to any of our emails lands on the same conversation.
- 3
It has a page of its own
The conversation has a page you can read, with no account and no key — its link comes in the mail.
Report a page
Something wrong on auray.app?
Pages on auray.app are previews of apps people build with Auray Code. If one asks you for a password or card details, offers a harmful download, or breaks our rules another way, tell us where it is.
A person reads it
Every report reaches our team. A report about a page somebody else already reported for the same reason is added to theirs.
Nobody is told how it ends
We ask for no email, so we cannot write back. To hear back, write to the address under the form instead.
Our team decides
A report takes nothing down by itself. Our team looks at the page and can take it down at once.
Error codes
Every refusal says what to do
Each of the 353 error codes the API can answer has an entry with its cause and its fix, and every refusal carries a request id — the fastest thing you can give us.