Where to send your request
Use email for private account details, subscription questions, billing, partnerships, sales and service inquiries.
Ask public usage questions about Nexscope tools, REST APIs, MCP integrations and documented ecommerce workflows.
Report expected and actual behavior, steps to reproduce and a non-sensitive error code. Redact all credentials and customer data.
Describe the goal, expected output and current workaround so the request can be evaluated in context.
Do not publish suspected vulnerabilities. Follow the security reporting guidance before sending evidence.
Include the page URL, the exact claim, the proposed correction and a primary source when available.
What to include
- Your goal and the Nexscope tool, page or endpoint involved.
- The marketplace, locale and relevant non-sensitive input.
- Expected behavior and what actually happened.
- A timestamp, request identifier or redacted screenshot if useful.
Do not post API keys, passwords, tokens, cookies, payment details, private customer data or unredacted screenshots in GitHub Discussions or Issues.
Response expectations
The Nexscope team checks public Q&A and actionable issue reports on business days and aims to acknowledge them within one business day. This is a response target, not a guaranteed resolution time. Private product and service inquiries are generally reviewed within one to two business days.
Search existing discussions and issues before opening a duplicate. A clear, safely redacted report is usually easier to investigate.