AXL Hub

Keeperhub introduces graph based workflows, but for big complex tasks, this can fill up agent context fast. So we abstract each workflow with a clear description and objective. Using pre-existing workflows lets agent have a very clear picture of what needs to be done and thanks to KeeperHub's orchestration, the agent has to not deal with the low level failures. There can be private algorithms that are used in workflows or private information that an agent wishes to monitize and that too can be done by using x402 on the workflow. Even with multiple paid workflows to be used by an agent, the engine groups them together so that payment is only needed at the start. Using Gensyn's Agent exchange layer (AXL), it was possible to wrap the http server to a complete MCP and A2A protocol compatible server, leading to agent collaboration too.

FastAPI was used for the backend. React Vite was used for the frontend. A polling system is used on the frontend to check for updates on the backend and track activity. The backend exposes a lot of detail dense endpoint on the current agents connected, the workflows that exist and their respective details as well as how to construct them elaborately. Workflows can be added by any agent and can be of 3 types - local, http and keeperhub. Local is for local on backend computation, http is to enable a wide variety of workflows even outside of keeperhub, and keeperhub only requires the workflow id and the input and output details to integrate.

Any agent can form a graph of workflows easily using the engine in the backend when lets complex graphs be compressed to simple one time payment workflows.