Overview
Choose the right integration path for HTTP clients, workflow tools, application code, CLI usage, and agent-driven access.
by @saifyxpro
Start with HTTP API if you want the most portable integration path. Move to workflow tools or language-specific clients after you validate the request shape.
Integration paths
Recommended order
- Test the route in the HeadlessX dashboard or with cURL.
- Move the request into your integration platform or application code.
- Use queued jobs for longer website crawl flows.
Core surfaces
- Website scraping and crawl routes under
/api/operators/website/* - Search providers under
/api/operators/google/ai-search/*,/api/operators/tavily/*, and/api/operators/exa/* - YouTube extraction under
/api/operators/youtube/* - Job inspection under
/api/jobs/* - Remote MCP under
/mcp