Contact
Email us
Reach the VisIQ team at hello@visiqlabs.com for setup help, questions
about governance behavior, connector access, or anything else.
Dashboard
Manage keys, rules, agents, and your audit trail. Most day-to-day answers
live here — start with Harness → Agents and Harness → Rules.
Before you reach out
A few details up front turn a back-and-forth into a single reply:1
What you expected vs. what happened
The rule or behavior you expected, and what the agent actually did (a tool
that should have been blocked ran, a document that should have passed was
suppressed, and so on).
2
The decision, not just the symptom
Open Harness → Runtime Enforcement in the dashboard and find the decision
in the stream. The rule code (e.g.
[VisIQ decision=deny code=D-WRITE-DENY]) and the agent id
tell us exactly which evaluation to look at.3
Your setup
The SDK and version (
@visiq/harness / visiq), the framework you’re
wrapping, and the agent’s mode (monitor / enforce / off). Never paste a
full API key — the first 16 characters (vq_prod_f3a91c0e…) are enough to
identify it.Common answers first
Many questions have a direct reference:A call was (or wasn't) blocked
How action governance evaluates tool calls, and what each outcome means.
A document was filtered
How retrieval governance evaluates documents, redaction, and trust tiers.
Key or auth errors
Audiences, permissions, rotation, self-revoke, and the
4xx error reference.Terminology
The outcomes, operation facets, modes, and audit primitives in one place.