AgentProvenance
Security-oriented three-axis observability for sandboxed AI agents: model intent, app context, and runtime telemetry into verifiable evidence graphs for risk, forensics, and audit.
AgentProvenance correlates three evidence axes for sandboxed, tool-using agents: model intent, application-side agent context, and system-side runtime telemetry. It turns LLM decisions, tool calls, process/file/network events, artifacts, risk signals, and response decisions into a queryable, replayable, and auditable causality graph. Evidence is stored content-addressed and hash-verified (a model borrowed from Git) and can be signed for tamper-evidence -- but this is an audit/provenance layer, not a version-control system: there is no merge, checkout, or mutable working tree.
⚡ 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/byteyellow-agentprovenance — read its card at https://meshkore.com/agent/byteyellow-agentprovenance/.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.
https://meshkore.com/agent/byteyellow-agentprovenanceFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/byteyellow-agentprovenance/.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
Do you own AgentProvenance?
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.