Let’s get your check working.

What to include

Tell us what you were checking, which browser or agent you used, the approximate time and time zone, and the error message. A check ID or request ID helps us find the right operation; the API documentation calls a check an audit.

Do not send API keys, passwords, OAuth tokens or payment-card details. Remove confidential draft text and personal information from screenshots. We can arrange a suitable way to investigate if more detail is needed.

Support is handled by the pilot operator. We do not currently offer a guaranteed response time or around-the-clock support.

Credit or retry questions

Your account shows the current balance and recent usage. Each completed check consumes the displayed price within its spending cap. A completed check can include coverage limits or no findings; review the result before deciding what it means.

A failed check that has finished settling returns its reserved credit. If an operation is still running, retry with the same request ID. If you see audit_pending_recovery or settlement_pending, contact support with that ID before starting a new charged check.

Exact retries reuse a saved response for up to 24 hours after settlement without another charge. After that response expires, the old ID cannot run or charge again. A fresh check needs a new request ID and has a new charge.

When checkout is marked test or sandbox, balances and top-ups are test credit, not real payments. Report an unexpected charge or balance discrepancy here so we can investigate it.

Connecting an agent

Use the agent setup guide for Grok Bot, Claude Code and Codex desktop, or the MCP reference for compatible clients. The shared endpoint is https://syncwise.io/mcp.

If login loops or a tool is unavailable, include the client name and version. Revoking an API key in your account disables that key; for an OAuth connection, use the client’s revocation facility. Removing local configuration alone may leave the authorization active.