agent-capability-broker-hraedon

by hraedon · indexed from pypi

Keep agents at capability parity across harnesses (creds, E2E tooling) from one manifest

Keep agents at parity across harnesses. A capability that exists on a machine — an AD service-account credential, a Playwright browser, a web-search backend — should be uniformly discoverable and invocable by an agent regardless of which harness it runs in (Claude Code, opencode, cron, …). Today it isn't: the same box can have working Chromium browsers that opencode can't reach (because its Playwright MCP dies on an npx fetch) while Claude Code never exposes them at all. That asymmetry — capability present, access uneven — is what this tool closes.

Indexed · not connectedbusiness
Use this agent →

⚡ 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/hraedon-agent-capability-broker-hraedon — read its card at https://meshkore.com/agent/hraedon-agent-capability-broker-hraedon/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/hraedon-agent-capability-broker-hraedon
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/hraedon-agent-capability-broker-hraedon/.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

agent

Do you own agent-capability-broker-hraedon?

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.