A21Agent21.ai

Vulnerability Disclosure & Bug Bounty

Last updated: August 5, 2026

Agent21 takes the security of our platform and our customers' data seriously. We welcome reports from security researchers and will work with you to understand and resolve issues quickly. This page describes how to report a vulnerability, what's in scope, and the protections we extend to good-faith researchers.

Report a vulnerability

Email security@agent21.ai with a description of the issue, the steps to reproduce, affected URLs/endpoints, and any proof-of-concept. Please give us a reasonable time to remediate before public disclosure. Machine-readable contact: /.well-known/security.txt.

Our commitment

  • We acknowledge new reports within 3 business days.
  • We provide an initial assessment (triage) within 7 business days.
  • We keep you updated on remediation progress and let you know when the issue is fixed.
  • We won't pursue or support legal action against researchers acting in good faith under this policy.

Safe harbor

If you make a good-faith effort to comply with this policy during your research, we will consider your actions authorized, will not initiate legal action against you, and will work with you to understand and resolve the issue quickly. This authorization does not extend to actions that harm Agent21, our customers, or third parties (e.g., data destruction, service disruption, or accessing more data than necessary to demonstrate the issue).

In scope

  • agent21.ai and its subdomains, and the Agent21 web application.
  • The Agent21 public API (/api/v1/*) and the Agent21 Slack app.
  • Authentication/authorization flaws, tenant-isolation bypass, injection, SSRF, RCE, and sensitive-data exposure.

Out of scope

  • Findings from automated scanners without a demonstrated, exploitable impact.
  • Denial-of-service (DoS/DDoS), volumetric, or rate-limit testing.
  • Social engineering, phishing, or physical attacks against Agent21 staff or facilities.
  • Vulnerabilities in third-party services we integrate with — report those to the respective vendor.
  • Missing best-practice headers or email (SPF/DKIM/DMARC) config without a concrete exploit.

Rules of engagement

  • Only test against your own account/data or accounts you have explicit permission to test.
  • Do not access, modify, or delete other customers' data. Use the minimum access needed to prove an issue.
  • Do not publicly disclose the issue until we've confirmed it is resolved.

Recognition & rewards (bug bounty)

Agent21 runs a private, invitation-based bug bounty. For valid, in-scope reports we offer recognition (with your permission, a place in our security researcher acknowledgements) and, at our discretion, monetary rewards scaled to the severity and impact of the finding. Reward eligibility and amounts are determined solely by Agent21. To keep the program fair: the first researcher to report a previously unknown, reproducible issue is eligible, and duplicates or already-known issues are not.

Security questions that aren't a vulnerability report? See Security at Agent21 or contact security@agent21.ai.