Antigen's docs index (llms.txt, the file AI assistants and crawlers read) lists 176 pages. About 110 are excellent product docs. The other 65 are a starter template that was never replaced: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center", "Subprocessors" is an "Illustrative list of subprocessors for this demo" that names nobody, and "EU data residency" describes options "in this demo help center". There are also pages on editor drafts, projects and Salesforce and HubSpot connectors that have nothing to do with pentesting, and the help-center home shows unrendered code. A security reviewer, or an AI assistant asked "does Antigen publish its subprocessors?", lands on placeholder text from a vendor asking for access to production.
First action
Remove the help-center group from the docs navigation and from llms.txt today.
How to measure it
Template pages in llms.txt
- Now
- –
- Target
- 0 (from 65)
- By
- 7 days
Steps
List the template pages
All 65 help-center entries in llms.txt (items under /docs/help).
Founder & CTO 1 hour
Unpublish or noindex
Remove them from navigation and llms.txt; return 410 or redirect to the docs home.
Founding Engineer 2 hours
Write the diligence set
Subprocessors, DPA/MSA request, retention, data location, engagement model, support, deletion.
Founder (CEO) 3 days
Check against the site
Make every statement match the Enterprise and Government pages and the Trust Center.
Founder & CTO 1 day
Publish and link
Link from the Trust Center, the Enterprise page and the docs home.
Founding Engineer 1 day
Ask the assistants
Run ten diligence questions through AI assistants and search; note which pages they cite.
Founder (CEO) 2 hours
Add a review owner
Quarterly check that docs, Trust Center and site still agree.
Founder & CTO quarterly
Why it works
In one week: unpublish the 65 template pages (or noindex them and drop them from llms.txt), then publish a small set of real replacements built from what the Enterprise and Government pages already say: Subprocessors (the actual vendors, with a change-notice process), DPA and MSA (how to request them), Data retention (30, 90 or custom days, on-demand purging, KMS encryption), Data location (what runs where for managed vs dedicated deployments), Engagement and plans (how a managed or dedicated engagement is scoped, even without prices), Support (dedicated expert, office hours) and Account and data deletion. Link each page from the Trust Center and the Enterprise page so diligence starts in the right place.
Security buyers read vendors' docs and legal pages before a demo, and AI assistants increasingly answer vendor-diligence questions from llms.txt. Removing placeholder legal text removes an easy reason to fail review, and real pages turn existing enterprise claims into something a reviewer can cite.
Ready to use
ChecklistDiligence pages to publish in place of the template
[ ] Subprocessors: real vendor list, purpose, region, change-notice window [ ] DPA and MSA: how to request, standard terms [ ] Data retention: 30 / 90 / custom days, on-demand purge, KMS encryption [ ] Data location: managed vs dedicated (Helm chart or container image) [ ] Engagement model: how scope, targets and approvals work [ ] Support: dedicated expert, office hours, response times [ ] Account and data deletion [ ] Remove /docs/help template pages from llms.txt and navigation [ ] Link all of the above from trust.antigen.sh and /enterprise
Risks and how to handle them
Deleting pages breaks inbound links
Redirect each removed URL to the closest real page.
New legal pages overstate commitments
Have counsel review the subprocessor and DPA pages before publishing.
Evidence
- Your websiteDocs index llms.txt (checked November 9, 2026): 176 entries. About 110 are real product docs (Asset Map, Runs, tCell, SDK, CLI with CI/CD integration, a "Pentest after a deployment" example, 21 integrations including GitLab, Jira, ServiceNow, Cursor Cloud and Devin, and an API reference). The other 65 are a help center from a template: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center"; "Subprocessors" is an "Illustrative list of subprocessors for this demo" naming none; "EU data residency options in this demo help center"; plus pages on editor drafts, projects, keyboard shortcuts and Salesforce and HubSpot connectors. The help-center home shows unrendered code.Source
- Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
- Your websiteGovernment page: "Security testing built for government boundaries"; dedicated on-premises deployment as a Helm chart or container image; SSO, SCIM and audit streaming to Splunk, Sentinel and others; support for GovRAMP and FISMA reporting work (stated as not a certification); mapping to NIST, CJIS, FERPA and CIRCIA; sectors: state and local government, public utilities and education; procurement through Pursuit, a public-sector reseller, plus cooperative purchasing.Source