llms.txt
Compare with other sites' llms.txt files →# Xalgorix
> Hosted autonomous AI pentesting. Runs a 22-phase offensive methodology against web apps and APIs and ships verified, evidence-backed findings on demand.
Xalgorix is a SaaS that turns the `xalgo` offensive engine into a click-to-scan service. Users pick a target, choose a scan mode (single / wildcard), and receive live phase progress, severity-rated findings with evidence, and a branded PDF report. Pricing is credit-based with monthly subscriptions and one-time top-up packs.
The engine is open source (Apache-2.0) at https://github.com/xalgorix/xalgorix and can be self-hosted; [Cloud vs self-hosted](https://www.xalgorix.com/hosted-vs-self-hosted) compares the two.
## Pages
- [Home](https://www.xalgorix.com/): Product overview, 22-phase methodology, scan modes, and a sample finding.
- [Methodology](https://www.xalgorix.com/methodology): The 22 phases Xalgorix runs on every engagement.
- [Sample reports](https://www.xalgorix.com/sample): Two real Xalgorix reports from live targets, with severity, CVSS and downloadable PDFs. No login.
- [Pricing](https://www.xalgorix.com/pricing): Subscription plans (Hacker $49/mo, Pro $119/mo, Max $279/mo) and one-time credit packs from $10.
- [Use cases](https://www.xalgorix.com/use-cases): How developers, AppSec teams, founders, MSSPs, compliance teams and bug bounty hunters use Xalgorix.
- [Bug bounty use case](https://www.xalgorix.com/use-cases/bug-bounty): Running Xalgorix within a bug bounty program's rules: identifying headers, rate limits, scope and exclusions, and what it can't enforce.
- [Cloud vs self-hosted](https://www.xalgorix.com/hosted-vs-self-hosted): Run the open-source engine on your own infrastructure, or let Xalgorix Cloud run models, compute and out-of-band listeners.
- [GitHub App](https://www.xalgorix.com/github-app): Free security review comment on every pull request. No workflow file, API key or account.
- [Integrations](https://www.xalgorix.com/integrations): GitHub App, REST API, signed webhooks, alerts, and LLM provider settings.
- [Blog](https://www.xalgorix.com/blog): Exploit-verification guides, AppSec field notes, and weekly threat digests. RSS feed: [/rss.xml](https://www.xalgorix.com/rss.xml).
- [Docs](https://www.xalgorix.com/docs): Install and run the self-hosted CLI: configuration, flags, environment variables and local API.
- [API docs](https://www.xalgorix.com/docs/api): Public REST API: start scans, poll status, pull findings, plus webhooks, status badges, and the GitHub Action.
- [Sign up](https://www.xalgorix.com/signup): Create an account (credit packs from $10).
## Comparisons
- [Open-source AI pentesting tools compared](https://www.xalgorix.com/compare): License, approach, hosted pricing and model requirements side by side.
- [Xalgorix vs Strix](https://www.xalgorix.com/compare/strix): License, hosted pricing, setup, PR reviews and when to choose each.
- [Xalgorix vs Shannon](https://www.xalgorix.com/compare/shannon): Shannon open source is white-box and Keygraph Pro adds black-box; Xalgorix tests the running app.
- [Xalgorix vs XBOW](https://www.xalgorix.com/compare/xbow): Enterprise, quote-based platform vs open source with self-serve Cloud.
- [Xalgorix vs PentestGPT](https://www.xalgorix.com/compare/pentestgpt): A research-born, open-source-only agent strong on CTFs vs exploit-verified web and API pentests, self-hosted or hosted.
## Guides
- [A signed token is not proof: verifying OIDC flaws](https://www.xalgorix.com/blog/verifying-openid-connect-relying-party-flaws): A validly signed ID token can still be forged, replayed, minted for another app, or from the wrong provider. How to verify OpenID Connect sign-in flaws.
- [Verifying SQL injection: proof, not a DB error](https://www.xalgorix.com/blog/verifying-exploitable-sql-injection): A DB error or a slow response is a lead, not proof of SQL injection. How to tell a real, exploitable SQLi from an innocent blip, confirm it safely, and fix it.
- [Verifying exploitable XSS: proof, not a popup](https://www.xalgorix.com/blog/verifying-exploitable-xss): An alert(1) proves a sink ran, not that the XSS is exploitable. How to tell self-XSS and neutralized payloads from impact in a victim's session, and fix it.
- [SSRF DNS rebinding: why filters fail, how to pin](https://www.xalgorix.com/blog/ssrf-filter-dns-rebinding-resolve-and-pin): An SSRF filter that validates one DNS lookup, then lets the client connect on another, falls to DNS rebinding. Why it happens and the resolve-and-pin fix.
- [Verifying web race conditions: proof, not luck](https://www.xalgorix.com/blog/verifying-web-race-conditions): A limit that breaks once could be luck, not a race condition. How to tell a timing fluke from a real concurrency bug, confirm it safely, and fix the window.
- [An accepted upload is not proof: verifying file upload](https://www.xalgorix.com/blog/verifying-exploitable-file-upload): A server accepting or storing your file is not proof of a bug. How to verify an exploitable file upload — RCE or stored XSS — and the fixes that hold.
- [A 9.8 is not a priority: CVSS vs exploitability](https://www.xalgorix.com/blog/cvss-score-is-not-a-priority): A CVSS 9.8 measures worst-case severity, not your risk. How to rank vulnerabilities by exploitability and reachability using EPSS, KEV and SSVC.
- [A missing token is not proof: verifying CSRF](https://www.xalgorix.com/blog/verifying-csrf-vulnerability): A missing or unvalidated CSRF token is not proof of a vulnerability. How to verify a real cross-site request forgery in the browser, and the fixes that hold.
- [Verifying XXE: proving external entity injection](https://www.xalgorix.com/blog/verifying-xxe-injection): A parsed entity or an XML error is not proof of XXE. How to verify a real external entity injection — file read or SSRF — safely, plus the fix that holds.
- [Verifying prompt injection in LLM applications](https://www.xalgorix.com/blog/verifying-prompt-injection-llm-applications): A model echoing an injected instruction is not proof of a vulnerability. How to verify a real prompt injection — a trust boundary actually crossed — safely.
- [Verifying broken function level authorization (BFLA)](https://www.xalgorix.com/blog/verifying-broken-function-level-authorization): A reachable admin function and a 200 are not proof of BFLA. How to verify a real broken-function-level-authorization escalation safely, and the fixes that hold.
- [A reflected Origin is not proof: verifying CORS](https://www.xalgorix.com/blog/verifying-exploitable-cors-misconfiguration): A site echoing your Origin in Access-Control-Allow-Origin looks like a bug but often proves nothing. How to verify an exploitable CORS misconfiguration safely.
- [A 302 is not proof: verifying OAuth account takeover](https://www.xalgorix.com/blog/verifying-oauth-redirect-uri-account-takeover): A 302 bouncing an OAuth login to your server looks dramatic but proves little. How to verify a redirect_uri account takeover safely, and the fixes that hold.
- [How to confirm HTTP request smuggling safely](https://www.xalgorix.com/blog/confirming-http-request-smuggling-safely): A timing blip is not proof of HTTP request smuggling. How to confirm a desync safely, without poisoning other users, and the fixes that hold.
- [{{7*7}} is not RCE: proving template injection](https://www.xalgorix.com/blog/proving-server-side-template-injection): A template that evaluates {{7*7}} to 49 proves evaluation, not RCE. How to tell detection from an exploitable sandbox escape and actually verify SSTI.
- [Verifying IDOR and BOLA: a 200 is not proof](https://www.xalgorix.com/blog/verifying-idor-bola-access-control): Changing an ID and getting a 200 isn't proof of IDOR. Confirm broken object level authorization with a two-account test and scope it without touching real data.
- [GraphQL security beyond introspection: what holds](https://www.xalgorix.com/blog/graphql-security-introspection-batching-dos): Auth on, introspection off, a rate limit set — yet a GraphQL login still brute-forces. How aliasing and batching beat throttles, and the limits that hold.
- [How to Verify SSRF Is Actually Exploitable](https://www.xalgorix.com/blog/verifying-ssrf-exploitability): Finding SSRF is easy; proving it is hard. Confirm it with out-of-band detection, see why blocklists and DNS rebinding fail, and the controls that stop it.
- [When an AI Pentester Escapes the Lab: Agent Safety Lessons](https://www.xalgorix.com/blog/when-an-ai-pentester-escapes-the-lab): Anthropic disclosed AI agents reaching real systems during CTF evals. Lessons on scope, egress and credentials for safe autonomous pentesting.
- [What It Costs to Self-Host an AI Pentester](https://www.xalgorix.com/blog/what-self-hosting-an-agentic-pentester-costs): Self-hosting Xalgorix is free, but LLM tokens, infra and upkeep are not. A cost model for agentic scans, and how Cloud credits compare.
- [Xalgorix Hands-On Guide: Setup, Scans & Trade-offs](https://www.xalgorix.com/blog/xalgorix-review): A hands-on walkthrough of Xalgorix by its founder: install paths, the 22-phase methodology, verification, strengths and limits.
- [Free AI Security Review for GitHub Pull Requests](https://www.xalgorix.com/blog/xalgorix-reviews-your-pull-requests): Install the free Xalgorix GitHub App for automatic security reviews on every pull request. No workflow file or API key. Comment to re-run.
- [Exploit-Verified Pentesting: Why Detection Isn't Proof](https://www.xalgorix.com/blog/detection-is-not-proof): Most scanners flood you with maybes. See how Xalgorix exploits each finding and re-verifies it independently, so every result is evidence.
## API & integrations
- REST API (Bearer `xlg_live_…` keys): `POST /api/public/v1/scans` to start a scan, `GET /api/public/v1/scans?id=` for status, `GET /api/public/v1/findings?scan_id=` for findings. 30 scans/min per key.
- Webhooks: register HTTPS endpoints to receive a signed `scan.completed` event (HMAC-SHA256 over `${timestamp}.${body}`, `X-Xalgorix-Signature` header).
- Status badge: `GET /api/public/v1/badge?slug=<trust-page-slug>` returns an SVG for embedding in a README (params: `metric`, `label`). No auth.
- GitHub Action: `xalgorix/scan-action@v1` (https://github.com/xalgorix/scan-action) runs a scan in CI and can fail the build on findings above a severity threshold.
## Optional
- [Changelog](https://www.xalgorix.com/changelog): Release history for Xalgorix Cloud.
- [Security](https://www.xalgorix.com/security): How customer data and scan evidence are handled.
- [Vulnerability disclosure](https://www.xalgorix.com/vdp): Scope, rules and safe harbor for reporting Xalgorix vulnerabilities.
- [Status](https://www.xalgorix.com/status): Live service checks.
- [About](https://www.xalgorix.com/about): Who builds Xalgorix and why.
- [WordPress RCE in KEV, Rails File Write: AppSec Digest](https://www.xalgorix.com/blog/weekly-appsec-threat-digest-oct-30-nov-6-2026): Oct 30–Nov 6, 2026: a WordPress upgrade race in KEV, a CVSS 9.8 Rails Active Storage flaw, two Ivanti zero-days, Node-RED attacks and a hijacked analytics tag.