Account and access
Sign in, find your private dashboard, and review the runs and credits attached to your account.
Sign inSupport center
Get unstuck without losing the evidence.
Find the right next step for account access, prepaid credits, benchmark runs, reports, exports, and the public readiness tools. Sensitive account and payment details stay private.
Choose a help route
Start with the part of the product you are using.
Benchmarks and reports
Understand run status, provider coverage, evidence, scoring, exports, and comparable reruns.
Read benchmark helpBilling and credits
Review prepaid credits and billing controls. Keep the Stripe receipt for any purchase investigation.
Open billing controlsFree tools and API
Troubleshoot the readiness checker, MCP endpoint, downloadable templates, and public API surfaces.
Open the free checkerBefore escalating
Three details make support faster.
Preserve enough context to reproduce the problem without sharing private report or payment data in public.
- 01
Open the affected item
Use the same signed-in account and open the exact run, report, export, checkout return page, or public tool that has the problem.
- 02
Preserve the identifiers
Copy the benchmark run ID and note the time, browser, action, and visible error. For billing, keep the Stripe receipt private.
- 03
Choose a safe route
Use private account or receipt channels for sensitive issues. Use GitHub only for reproducible public-site or API problems with secrets removed.
Include useful context
- • Run ID or exact public URL
- • Time of the problem and action attempted
- • Browser, export type, or public endpoint used
- • Exact visible error text and a safe reproduction sequence
Keep sensitive details private
- • Do not post receipts, tokens, or account email addresses
- • Do not attach private reports or raw benchmark answers
- • Do not disclose security findings in a public issue
- • Use the private route on the applicable receipt or service notice
Common questions
Resolve the most common issues first.
I cannot sign in. What should I check first?
Return to the sign-in page in the browser and email account used for checkout. If the problem follows a purchase, keep the Stripe receipt and checkout return link available, but do not post either one publicly.
My payment succeeded but I do not see a credit.
Open the checkout return link in the same browser that started payment, then refresh the dashboard. If the credit still does not appear, use the private route on the Stripe receipt or applicable service notification and include the receipt plus the account email used at checkout.
Why is a provider missing from my report?
A provider call must succeed and return valid web sources to be score-eligible. Failed, unsupported, or unsourced calls remain visible in coverage rather than being counted as silent misses. Open the run to review the recorded exclusion reason.
What should I send when an export fails?
Include the run ID, export type, time of the attempt, browser, and visible error text. Do not attach a private report to a public issue. First try the export again from the run page after the benchmark is complete.
Where should I report a public checker or API bug?
Use the public GitHub issue tracker for a reproducible problem involving public pages, downloads, the readiness API, or MCP endpoint. Remove private domains, tokens, receipts, personal data, and report contents before posting.
Still need help?
Use the route that matches the sensitivity of the issue.
Account, billing, privacy, and security issues need a private path. Reproducible public-site, download, checker, or API bugs can use the public issue tracker after sensitive details are removed.