Contact

Talk to us

Four addresses, each going to the person who handles it. No ticket maze, no phone tree, and no chatbot that asks you to rephrase the question.

Support hours
Mon–Fri, 09:00–18:00 WITA (UTC+8)
First reply
Within 1 business day
Security reports
Acknowledged within 24 hours

Support

Account, billing and API questions. Include your invoice number for anything payment related.

[email protected]Replies within 1 business day

Privacy

Requests about your personal data: access, correction, deletion, portability.

[email protected]Answered within 30 days by law, usually sooner

Security

Vulnerability reports and suspected key exposure. If a key leaked, say so in the subject line and we will revoke it before reading the rest.

[email protected]Acknowledged within 24 hours

Sales

Team plans, contractual SLAs, invoicing in a currency we do not list, or reselling the gateway.

[email protected]Replies within 2 business days
Operating entity
Opsora
Operator
Claudius Weinert
Location
Bali, Indonesia
Support hours
Monday to Friday, 09:00 to 18:00 WITA (UTC+8)
API status
api.useopsora.com/health
Payments
Stripe for cards, Midtrans for Indonesian rails

1.Before you write

A few answers are faster to find than an email is to answer.

  • Where do I get an API key? The dashboard issues one on the API keys tab. The gateway authenticates with Authorization: Bearer opsk_… — create the key next to your account, not in your source code.
  • Why is my request returning 401? The key is missing, revoked, or the header is malformed. Send it as Authorization: Bearer <key>, not as a query parameter.
  • Why 429? You have hit your plan's rate limit or monthly quota. /v1/usage shows both. Moving up a plan takes effect immediately.
  • Which models are live right now? /v1/models is the authoritative list. A model that appears in an article but not in that response is not routable.
  • Where are the API docs? Interactive reference at api.useopsora.com/docs, raw schema at /openapi.json.

We do not offer telephone support. Email reaches the person who can actually fix the problem, and it leaves a written record both sides can point at.

2.Security and abuse reports

Send anything about a vulnerability, a leaked credential or abusive traffic to [email protected]. Include the affected endpoint, what you observed, and how to reproduce it. Please do not test against another customer’s account, and do not run a denial-of-service test at any time.

We will not pursue anyone who reports a problem in good faith, and we will credit you in the fix note if you would like that.