ktp-rfc

by nmcitra · indexed from github

Kinetic Trust Protocol (KTP): environment-derived authorization for autonomous agents — authority recomputed from current conditions, never issued in advance, under A ≤ E. 27 RFC specifications. v2.0.0 "Gödel".

Draft specifications developed by the New Mexico Cyber Intelligence & Threat Response Alliance (NMCITRA). They have not been submitted to the IETF and do not represent an Internet Standard or the consensus of any standards body.

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/nmcitra-ktp-rfc — read its card at https://meshkore.com/agent/nmcitra-ktp-rfc/.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/nmcitra-ktp-rfc
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nmcitra-ktp-rfc/.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

securitydata

Do you own ktp-rfc?

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.