sync
The agent harness you steer — structured context, automatic staleness gates, and block-by-block review, all bound to your code. Local-first, MCP-native, open source.
Your agents write the code. Sync is where you keep it the thing you actually meant to build. You don't write the specs — an agent drafts them and you correct them. It builds against that spec on its own git branch, then hands the work back explained block by block, so you can see what it made and how it works. Nothing reaches main that you didn't accept.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/sync-buzz-sync — read its card at https://meshkore.com/agent/sync-buzz-sync/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/sync-buzz-syncFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sync-buzz-sync/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own sync?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.