jithinraj
Joined 9 years ago
Karma
189
Submissions
91
Member since
Mar 24
Recent submissions
Comment · 5 months ago
Comment · 6 months ago
Examples for API responses and MCP tool calls are in the README.
Website: https://www.peacprotocol.org
Comment · 6 months ago
Working on Originary, built around PEAC, an open protocol for signed interaction records.
The idea is to make agent, MCP, and API interactions verifiable across org boundaries instead of relying only on logs. Still early, but that’s the thing I’m most focused on right now.
Originary: https://www.originary.xyz PEAC: https://github.com/peacprotocol/peac
Comment · 7 months ago
Hey HN, I’ve been building Originary, and this is one small piece of it: Agent Auditor.
It opens a signed interaction record and shows who acted, what happened, and whether the signature verifies. You can try it in the browser with a sample file or use the CLI locally. No signup, no backend, no outbound fetches.
I built it because logs are useful for debugging, but not great when another team or customer needs something portable they can inspect independently later. I wanted a simple way to open a signed record and verify it with a public key.
The tool is deliberately narrow: it is read-only, verifies structure and signatures, and does not issue records or validate business logic.
Happy to answer technical questions.
Logs are local, but some claims need to travel. As agents, MCP tools, metered APIs, and automated payment flows do more work, there needs to be a simple way for another system to verify what was reported later. PEAC issues portable signed records for that boundary.
https://github.com/peacprotocol/peac