Help with ScriptEngine.

What to expect

Support timing and scope.

Email submissions are accepted 24 hours a day. We target an initial English-language reply within two business days, but this is not a guaranteed resolution time or service-level agreement. Complex payment, upstream-provider, legal, or security investigations may take longer. Processor settlement and blockchain confirmation times are outside ScriptEngine's direct control.

Choose a topic

Include the information that identifies the issue.

Protect your credentials

Never send a secret to support.

If an API key may have been exposed, rotate it from the workspace immediately, update each client that used the old key, and then contact support with the masked prefix. If you cannot sign in, use password recovery first; changing the password invalidates existing account sessions.

Before emailing

Check the current source of truth.

• Use the API documentation for the base URL, bearer authentication, model discovery, and current tested interface.
• Use the model catalog for public model and rate information, then confirm availability with authenticated discovery.
• Use the signed-in workspace for your key prefix, balance, order, referral, and recent usage records.
• Use the online withdrawal function to submit a consumer withdrawal statement for an identified order.

What happens next

Verification, investigation, and response.

We may request proportionate information to verify account ownership, locate an order, or reproduce an API issue. A concise report is usually enough: what you expected, what happened, when it happened, and the relevant route, model, request ID, or order ID.

Refund requests are assessed under the Refund Policy and mandatory law. Privacy requests are handled under the Privacy Policy. Suspected service or security incidents should be reported by email because ScriptEngine does not currently publish a status page or uptime SLA.

Operator

Who receives your support request?