Gateway Architecture: The HLD Dispatcher
The HLD Fleet operates as a unified Agent Cluster orchestrated through a high-performance FastAPI Gateway. This architecture enables both precise individual agent targeting and collective, multi-agent problem solving.
Dual-Mode Operation
The gateway at https://agent.api.highlimitdesigns.com exposes two primary operational patterns:
1. Sovereign Routing (Individual)
Users and services can target specific agents directly for specialized tasks. Each agent maintains its own sovereign endpoint where it operates within its specific domain of expertise.
- Pattern: POST /{agent_name}/run
- Use Case: Security audits (Cipher), visual generation (Prisma), or system monitoring (Pulse).
2. Orchestrated Dispatch (Collective)
The /dispatch endpoint triggers a cluster-wide operation where multiple agents work together on a single goal.
- Endpoint: POST /dispatch
- Logic: The gateway analyzes the request and notifies the relevant agents. They "pick up the line" collectively, using their diverse tools and skills to accomplish the objective.
- Efficiency: Parallel processing where Cipher handles the code, Prisma handles the UI, and Axon supervises the workflow.
Machine-Native Utility
HLD agents are not isolated LLM instances; they are Server-Native Workers. Every agent in the Fleet is granted access to the machine's local utilities:
Shared Fleet Intelligence
Agents continuously pull and push data to: - The Mind (Fleet Notes): Collective memory and task state. - Skill Routes: Dynamic loading of new operational skills and bug fixes. - Documentation: Real-time access to this documentation portal.
Machine Tooling
Agents can execute local programs and interact with the server environment to perform real-world tasks: - Terminal Execution: Command-line operations for deployment and analysis. - FileSystem Access: Direct interaction with project files and data. - External APIs: Bridging the Mesh to the wider web.
The Gateway is the entry point. The Server is the engine. The Fleet is the worker. 👊💥