Content Gate

Content Gate allows you to define topics that should only be discussed with authenticated users. When an anonymous visitor asks about a gated topic, the AI responds with a custom message instead of the actual answer.

This is useful for protecting sensitive information like:

• Pricing details and discount structures
• Enterprise features or internal roadmap
• API documentation or technical specs
• Partner-specific information

Topic gating is currently configured through the agent settings API. Update your agent with three settings keys:

• gated_enabled (boolean) — turns topic gating on or off
• gated_topics (array of strings) — the topics to restrict. Be specific — for example, use "enterprise pricing tiers" rather than just "pricing" to avoid false positives.
• gated_message (string) — the message anonymous users see when asking about a gated topic. When empty, it defaults to: "This information is available to registered users. Please sign in or contact us for details."

curl -X PATCH https://api.respondo.ai/api/v1/agents/<agent-uuid> \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "settings": {
      "gated_enabled": true,
      "gated_topics": ["enterprise pricing tiers", "internal roadmap"],
      "gated_message": "This information is available to registered users. Please sign in or contact our sales team for details."
    }
  }'

Content Gate also requires user identification to distinguish authenticated from anonymous visitors. See the User Identification docs for setup instructions.

When a message arrives from the widget, the system checks whether the user has a verified identity:

For Content Gate to work, you need to pass user identity when initializing the widget. Here is a minimal example:

<!-- For authenticated users -->
<script>
  Respondo.init({ agentId: 'YOUR_AGENT_ID' });
  Respondo.identify({
    userId: 'user-123',
    email: 'user@example.com',
    userHash: 'HMAC_SHA256_HASH'  // Required if identity_secret is set
  });
</script>

<!-- For anonymous visitors — just init without identify -->
<script>
  Respondo.init({ agentId: 'YOUR_AGENT_ID' });
  // No identify() call — user is anonymous, gated topics will be restricted
</script>

For HMAC verification setup, see Identity Verification (HMAC).