relayops

by patibandlavenkatamanideep · indexed from github

Production-shaped control plane for AI support agents: scoped routing, policy broker, tool boundaries, approval queue, replay verification, audit traces, and human handoff. Prototype on synthetic/sample data — no production users.

Status: v3.0 — production pilot readiness — a production-shaped pilot of the full control plane: FastAPI service layer with signed bearer-token auth and per-caller rate limiting, request-level audit, Pre-Action Intent Packets, Broker Decision Packets, an enforced policy-handle registry, an MCP-style tool-server boundary, external action envelopes with idempotent replay, replay verification over audit traces, a SQLite customer/auth datastore, a read-only Hermes operator review, an operator metrics dashboard (resolution / handoff / safety / replay / efficiency) with thresholded Hermes breach…

Indexed · not connectedcode
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/patibandlavenkatamanideep-relayops — read its card at https://meshkore.com/agent/patibandlavenkatamanideep-relayops/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/patibandlavenkatamanideep-relayops
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/patibandlavenkatamanideep-relayops/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

apifine-tunragllmdata

Do you own relayops?

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.