- Sub-100ms response times via hybrid CNN-LLM architecture
- Live video streaming to observe sessions in real-time
- Human-in-the-loop with guardrails and manual takeover
- Flexible integration via REST API, WebSocket, MCP, or OpenAI-compatible endpoints
Get Started
π Quickstart
Run your first task in 5 minutes
π Integrations
REST, WebSocket, OpenAI, n8n
π€ MCP Setup
Claude Desktop & Cline setup
π Live Stream
Watch sessions in real-time
What Can Enigma Do?
Research & Data Extraction
Gather information from multiple sources, extract structured data, and compile research reports automatically. Example: βSearch LinkedIn for engineering managers in San Francisco, extract their profiles, and compile contact information into a structured list.βForm Automation
Fill out complex forms, handle multi-step workflows, and submit applications with conditional logic. Example: βGo to this insurance quote form, fill it out using the customer data I provide, and return the final quote.βE-commerce Operations
Search for products, compare prices, add items to cart, and even complete checkout flows with human approval. Example: βFind the top 3 wireless keyboards on Amazon under $50, add the best-rated one to cart, and show me the checkout page.βDynamic Testing
Test web applications with natural language instructions, adapting to UI changes without brittle selectors. Example: βNavigate through the signup flow, try to register with invalid data, and report any validation errors you encounter.βHow It Works
Sessions & Tasks
A session is an isolated browser instance controlled by an AI agent. A task is a single objective for the agent to complete within that session.Response Model
Most browser tasks complete in 10-40 seconds. Enigma waits up to 50 seconds for your task to finishβmeaning you typically get results inline, in a single request.Guardrails
When the agent needs human inputβcredentials, clarification, approvalβit triggers a guardrail and pauses. Your application detects this and provides the input. Common triggers: Login forms, purchase confirmations, CAPTCHAs, ambiguous instructions. Learn more about GuardrailsChoose Your Integration
Which endpoint should I use?
REST vs WebSocket?
- REST: Simpler. Good enough for 90% of use cases. Poll for results.
- WebSocket: Only if you need live agent thoughts or sub-second event handling.
Integration Methods
| Method | Best For | Real-time Events |
|---|---|---|
| REST API | Simple integrations, serverless, stateless workflows | Poll for updates |
| WebSocket | Live dashboards, interactive UIs, real-time agent thoughts | Yes |
| OpenAI-Compatible | LangChain, LlamaIndex, Vercel AI SDK, existing OpenAI tooling | Poll or stream |
| MCP Server | Claude Desktop, Cline, any MCP-compatible AI assistant | No |
| Workflows | n8n, Make.com, Zapier | Poll for updates |
Quick Links
- REST API Integration
- WebSocket Integration
- OpenAI-Compatible API
- MCP Server Setup
- Workflow Integration (n8n, Make, Zapier)
Enigma vs. Traditional Automation
| Enigma | Playwright/Puppeteer | |
|---|---|---|
| Input | Natural language | Code |
| Adaptability | AI agent adapts to UI changes | Scripts break on changes |
| Maintenance | Self-healing | Manual updates required |
| Latency | Sub-100ms decisions | ~50ms per action |
| Best for | Dynamic tasks, scraping, form-filling | Regression testing, CI/CD |