agent-evidence-vectors
Conformance corpora and reference verifiers for agent evidence records
Both run the harness described under "The verification pipeline" against your verifier through the external-implementation contract: the harness invokes , reads the verdict from the exit status and the condition codes from the last line of stdout, and hands the key policy to the process in AEE_SUBSTRATE_KEYS. Your verifier has to speak that contract and nothing else. The reference rail replays the same vectors beside it, and the report records where the two agree, where they disagree, and where your verifier reached the corpus's verdict under a different condition code.
⚡ 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/sankalp-gilda-agent-evidence-vectors — read its card at https://meshkore.com/agent/sankalp-gilda-agent-evidence-vectors/.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/sankalp-gilda-agent-evidence-vectorsFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sankalp-gilda-agent-evidence-vectors/.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 agent-evidence-vectors?
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.