Documentation

Welcome to the Aiqaramba documentation. Whether you are just getting started or looking for a specific API endpoint, you will find everything you need right here. If something is missing or unclear, let us know. We are always improving these docs.

What is Aiqaramba?

Aiqaramba is a testing platform that uses AI agents to test your web application for you. You describe what you want to test in plain language, and our agents go do it on a real browser. No test code to write, no selectors to maintain, no flaky CI to debug at 2am.

The core idea behind Aiqaramba is surprisingly simple, but building and maintaining it at scale is where the real challenge lies. These four pillars explain what distinguishes Aiqaramba from any other agentic system.

  • Virtual devices. Our agents operate through virtual devices on live browsers. Most browser automation tools work through the Chrome DevTools Protocol, which is powerful but hits its limits quickly on complex pages with heavy JavaScript. Think drag-and-drop, pinch-to-zoom, or anything that relies on real pointer and keyboard events. Because our agents use virtual devices, they can do everything a real user can.
  • Scale. You can run many agents concurrently and in a structured way. You define the journeys you care about, assign personas, group them into schedules, and Aiqaramba takes care of running them all at the right time. You do not need to worry about orchestration, parallelism, or scaling infrastructure. You just describe what needs testing, and we handle spinning up browsers, distributing work, and collecting results.
  • Tests that don't break. This addresses perhaps the biggest pain point for anyone who has ever maintained a test suite: tests breaking every time the application changes. Since our agents understand natural language, they adapt to even significant UI changes. A test like "try to sign in" will keep working even if you completely revamp your login page.
  • Integrate with your tools. Aiqaramba plugs into the tools you already use. When an agent finds a problem, it can automatically create a GitHub issue or a Linear ticket with all the details. Hook up Slack and your team gets notified the moment something breaks. Results flow back into your existing workflow so nothing gets lost between "bug found" and "bug fixed."

For developers

If you are the kind of person who skips the tutorial and goes straight to the API docs, we respect that. Here is your API reference and you can grab an API key from your account settings. Go build something cool.