Case studiesSEO software

SearchAtlas: agent orchestration around an existing SEO platform

SearchAtlas already had audits, content tools and SEO services. Ego Eimi worked with Afaq Jamshad on an agent system that could plan a goal, use those existing capabilities and retain context through the work.

Business
SearchAtlas
Sector
SEO software
Scope
Agent orchestration and persistent execution
Contributor
Afaq Jamshad
Editorial illustration: a sculptural indexing instrument with an orange tab
AI-generated editorial illustration of the project’s domain.

The platform had the tools, but people still coordinated every step.

An SEO task can cross reports, content, metadata and publishing tools. SearchAtlas had the underlying capabilities, but a person still had to translate a goal into the sequence of actions across them.

The engineering challenge was to add orchestration while retaining the useful platform services. Session state needed to survive agent handoffs and infrastructure scaling.

Make existing services callable and persist the execution context.

Atlas Brain decomposed goals and delegated work to specialized agents. Existing microservices became callable skills through MCP, with RabbitMQ coordinating events and progress updates.

The implementation used the OpenAI Agent SDK with OpenRouter and database-backed state through SQLAlchemy. Composite session and agent keys separated memory, while atomic rollback limited recovery to a failed run. Tiered routing assigned different classes of task to different models.

What the workflow includes

  • Plan work across specialized agents and existing SEO services.
  • Expose platform capabilities as MCP tools.
  • Persist agent-specific context across application instances.
  • Stream progress and recover failed runs through explicit state handling.

Project details

The SearchAtlas agent request flow: user input over a WebSocket layer, a RabbitMQ message broker, Atlas Brain orchestration, sub-agent delegation, tool execution, and streamed responses

Project materials showing the workflows and interfaces described in this case.

Product walkthrough

Agent orchestration and persistent execution. The delivery section explains the workflow demonstrated here.

A goal could move through specialized agents and existing tools.

The delivery added a planning and execution layer over an established platform. Existing services could participate in agent workflows while state, progress and recovery were handled as application responsibilities.

What this means for the technology owner.

Adding agents does not remove the need for platform ownership. Someone must maintain tool contracts, permissions, memory boundaries and the review rules for changes to a customer’s site. A takeover should include those controls alongside the orchestration code.

How we operate AI workflows →

PythonOpenAI Agent SDKOpenRouterRabbitMQMCPSQLAlchemy

Project contribution: Afaq Jamshad. The scope described above identifies the work behind this case.

SearchAtlas — project link

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.