MeshCore – Why do I have to build every agent from scratch?
MeshCore – Why do I have to build every agent from scratch?
I was learning to build multi-agent systems with LangChain and CrewAI. Started with a simple travel planning agent. But to make it work, I had to build FIVE separate agents: 1. Flight search agent 2. Hotel search agent 3. Flight booking agent 4. Hotel booking agent 5. Itinerary/things-to-do agent This felt wrong. I wanted to orchestrate a trip planner without building every vertical myself. *Why can't I just discover and use existing agents?* So I built MeshCore - a service mesh + marketplace where agents can: - Register their capabilities (e.g., "I search flights") - Discover other agents automatically - Call each other through a gateway - Handle billing/metering automatically *Try it:* https://meshcore.ai *GitHub:* https://github.com/MeshCore-ai/mesh-cli *Tech:* Service mesh architecture (like Istio for microservices, but for AI agents) *Supports:* LangChain, CrewAI, AutoGen, custom agents *Looking for feedback from multi-agent builders:* - Have you hit this same pain? - Would you use a shared marketplace of agents vs. building everything yourself? - What's missing?
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
Debco – Build Debian Containers from Scratch Without Dockerfile
Nested VMs from Scratch in C
A debugger from scratch – part 1
Javadoc Rewritten from Scratch
MMOBomb 4.0 – I rebuild it from scratch
GCounter CRDT Implemented from Scratch in Golang
An itch that I can't quite scratch.
How to build your own CNC-machine from scratch
Build linux from scratch for xilinx zynq mpsoc
Ep2 – Build your own websites from scratch with no coding