# AI penetration testing for web applications and APIs Source: https://aipentestservices.com/ Publisher: Excession Labs (aipentestservices.com) Last updated: 2026-11-09 AI-assisted penetration testing of web apps and APIs with Incursion, the Excession Labs agent. Every finding is proven with evidence before it reaches you. AI-assisted pentesting by Excession Labs AI pentesting that shows its evidence Incursion, our testing agent, works through your web application and API as each user role you give it. It may only report a finding that links to proof, and Excession Labs checks that proof before the finding reaches your report. Start a pilotSee an example assessment For ordinary web apps and APIs. Testing starts only after written scope and authorization. Demonstration Pinecart (demo app) ยท what the agent claimed, and what held up CandidateCheckVerdict buyer_A reads /v2/orders/ord_test_B1 and gets 200Nonexistent order returns 404. buyer_B's own session shows the same order and total.Confirmed, High /v2/me/orders?user=buyer_B returns 200The response holds buyer_A's own orders. The API ignores the parameter.Dropped Refund endpoint accepts a negative amountState-changing request: rule set to ask. Approved by Excession Labs, run on a test order.Confirmed, Medium Password guessing on /loginRule set to deny for this scope. Not run.Out of scope Every confirmed finding links to its requests, responses and controls. See the full example How a test runsIncursion splits the engagement into tasks and runs them in parallel. Tool rules decide what it may do, and a task ends only when its findings link to evidence. Scope and authorizeHosts, roles, test windows and off-limits actions, signed by the system owner. Set the rulesEach tool runs, asks for approval, or is blocked. Costly and state-changing actions can wait for a person. Test in parallelWorkers test roles, endpoints and flows at the same time, and keep notes. Prove or dropControls and read-back from a second account decide what is real. Review and reportExcession Labs checks each finding's evidence and writes the report. Then we retest your fixes. The full process What it tests Web applications with signed-in user flows, for each role you provide REST and GraphQL APIs, with or without documentation Object-level and function-level authorization between users and tenants Sessions, login, password reset and account flows Input handling: injection, stored scripts, file uploads Admin panels and internal tools exposed to the web Out of scope here: internal networks, physical and social engineering tests, and testing of AI models themselves. For LLM apps and agents see AI red teaming. Why each finding needs evidenceA language model can read a 200 response as a breach when the server simply ignored a parameter. Incursion records the request, the response and the controls for each candidate, so a person can check the claim. In the example above, one candidate looked like a leak until the control showed that the API returned the caller's own orders. We dropped it.How we keep false positives out Who does what StepIncursionExcession Labs Scope and authorizationAgrees it with you in writing Tool rulesFollows themSets them for your scope Mapping and testingRuns tasks in parallel, as each roleApproves actions that need approval EvidenceLinks each finding to requests, responses and controlsChecks the evidence ReportDrafts findings with reproduction stepsWrites and signs off the report RetestReruns the proof against your fixConfirms the result AI-assisted vs manual pentesting You decide what is off limitsWe agree in writing which actions must never run, such as deleting data, sending real email or charging cards. Destructive proofs use only test-owned accounts and records. Tests that cost money, like email sending or paid third-party APIs, are bounded, and the report states what they cost.Safety and control After each releaseOnce your application is mapped and the test accounts exist, testing again after a meaningful release is faster to set up. Testing after releases Guides to AI-assisted testing AI pentesting basicsWhat is AI penetration testing?Scanners with AI, autonomous agents and AI-assisted testers, and what each can do. AI pentesting basicsWhere AI pentesting falls shortBusiness context, novel chains and other limits, stated plainly. How AI testing worksHow AI agents test authorizationDifferential tests across roles and tenants, with a worked example. All guides ## Questions ### What is AI penetration testing? It is penetration testing in which an AI agent runs much of the testing work: mapping the application, sending requests as different users, comparing responses and collecting evidence. In our service the agent is Incursion. Excession Labs scopes the work, checks the evidence for each finding and writes the report. ### Is this the same as testing an AI chatbot? No. This site uses AI to test ordinary web applications and APIs. If you need your own LLM application, RAG system or agent tested for prompt injection and data leakage, see [airedteamingservices.com](https://airedteamingservices.com/). ### Does the agent run without supervision? It runs under tool rules we set for your scope. Each tool either runs on its own, waits for approval, or is blocked. State-changing and costly actions can require approval. Excession Labs checks the evidence before anything goes in your report. See [safety and control](/safety/). ### How is this different from a vulnerability scanner? A scanner sends known payloads and reports pattern matches. The agent works through the application as different users, follows multi-step flows and must link each finding to evidence. Read [AI pentest agents vs DAST scanners](/guides/ai-pentest-agents-vs-dast-scanners/). ### How much does it cost? We quote after scoping, because the work depends on the number of applications, roles, API endpoints and environments. You can start with a [scoped pilot](/pilot/). See [pricing](/pricing/).