Contact

What to include

Say what you were doing and what you saw. If you are signed in, the Google account email is enough for us to look up the account. If a decide call failed, include the HTTP status and the code field from the JSON, and the time in UTC. The account page lists recent usage with the route, the input-token count, the cost, and the time. Those four fields are what the ledger stores.

Do not paste a laya_ secret, a card number, or a ticket that contains passwords or other secrets. If a key has leaked, revoke it on the account page first, then tell us the key prefix (the first characters shown in the list), not the secret. We store keys as a hash. We cannot recover a secret that was shown only once.

Billing mail can name the pack (Spark, Bench, Runway, Floor, or Plant) and the order id if you have one. Credits are added when the payment notification reaches /api/payment/notify/creem and the signature matches. The page the browser returns to after checkout does not add credits. If the status page shows Creem off, checkout is not configured on this deploy and a buy button returns an error instead of charging you. Stripe is used only when this deploy is switched to that provider.

What this mailbox is not

We can answer questions about this website: sign-in, keys, the monthly grant, prepaid packs, the decide and gate routes, and the pages published here. We do not provide support for Convai Innovations, for the upstream maintainers, or for the LayaAir game engine. Those are separate projects. Bug reports and feature requests for the Apache-2.0 package belong on the upstream repository, which is linked from the footer.

The model does not write a reply for you to send to a customer. If a label looks wrong, check the question text and the label glosses first. The support-triage guide walks through one ticket. The API reference is the contract for status codes. The privacy policy explains what we store, including Google Analytics 4 and advertising cookies, and how to opt out of personalized ads.

We read mail sent to support@laya-model.com. We do not promise a response time. For a product question that is already answered on the site, the FAQ and the about page are the faster path.

Look here before you write

• API reference for authentication, POST /v1/decide, batch, the gate, and the application routes.
• Pricing for the monthly grant and the five packs.
• Status for whether live inference and Creem checkout are configured.
• Guides for the decide request, the meter, and support triage.
• Privacy for account data, Google Analytics 4, and advertising cookies, including how to opt out of personalized ads.