Support

Send support requests to [email protected]. Include the affected endpoint, an approximate UTC time, the response status, and the ViperCapture request ID when one is available. Do not send API keys, session cookies, target-site credentials, payment details, private source documents, or other secrets. For render failures, a minimal public URL or a redacted request shape is usually enough to begin investigation.

Billing and accounts

For subscription, cancellation, payment, refund, referral-credit, or account-deletion questions, write from the verified email address associated with the account. Paddle is the merchant of record and may need to handle parts of a payment inquiry. ViperCapture will never ask you to send a full card number, raw API key, Clerk session token, or password by email. The refund policy and account controls remain the authoritative self-service paths.

Security and abuse

Responsible security reports and abuse reports use the same email address. Describe the affected ViperCapture surface, expected impact, reproduction steps, and any safe evidence you can share. Do not access other users’ data, disrupt production, run denial-of-service tests, or publish sensitive details before there has been a reasonable opportunity to investigate. Reports about third-party target sites should be sent to those site owners unless the issue is caused by ViperCapture itself.

Documentation before email

Agents and developers can often resolve integration questions immediately through the ViperCapture API documentation, interactive reference, OpenAPI schema, agent guide, and service status page. These resources document authentication, strict request validation, limits, response headers, retries, and supported output formats.