Contact
Reach a person, by email.
Every channel below is an email address that reaches a monitored inbox. There is no ticket portal, live chat or phone line, and this page does not submit a form on your behalf.
API and account support
Errors, authentication, routing, keys and model availability. Include the request ID when the problem is a specific call.
Billing and invoices
Charges, invoices, receipts, plan changes and refund questions. Include the invoice number so the record can be found.
Enterprise and sales
Negotiated limits, team access, contract billing and procurement. Start from the enterprise page for the fields that speed this up.
Security reports
Potential vulnerabilities or suspected key exposure. Rotate any credential you believe was exposed before you send the report.
What to include
The details that resolve a request fastest.
- Account emailThe address the account is registered under, so the right record is opened.
- Request ID, when a call failedThe
x-prbycode-request-idresponse header, or the row in the activity log. Without it the exact call has to be guessed from timestamps. - What you sent and what came backThe model ID, the error type and the status code. Do not paste a live API key or a customer prompt.
- Invoice number, for billingThe number from the billing section, which identifies the charge directly.
Direct addresses
One inbox, routed by subject.
https://api.prbycode.com/v1Response times are not published as a commitment. Priority routing for support requests depends on the plan the account is on; the plan's included support is listed on the pricing page.
Before you write
Two checks that answer most questions.
Do not send
Keep these out of email.
/security