Hacker News: keertahacker

Show HN: AERF – receipts for AI agents, crypto-signed like cosign for evidence

keertahacker — Thu, 07 May 2026 13:53:27 +0000

Article URL: https://github.com/aerf-spec/aerf

Comments URL: https://news.ycombinator.com/item?id=48049489

Points: 2

# Comments: 0

New comment by keertahacker in "Show HN: Health billing agent denies claims in 1.2s, offices should know why"

keertahacker — Fri, 17 Apr 2026 00:48:40 +0000

Agent-vs-agent makes the trust problem sharper, not necessarily easier. Each side needs verifiable evidence of what the other committed to. They cant do with just vendor logs. The "one side controls the record" assumption breaks right after the human-on-the-other-end one. Plus, its like waiting for the police after an incident with out a first-aid kit.

New comment by keertahacker in "Show HN: Health billing agent denies claims in 1.2s, offices should know why"

keertahacker — Thu, 16 Apr 2026 18:55:02 +0000

Both, the insurer installs this to produced portable evidence that end users can consume. Would mainly be the startups building AI agents that interact with insurers on behalf of hospitals. If a hospital needs to process 100,000 claims made by agents and verify them, its their records pitted with vendor logs. This lets the vendor hand over a folder the hospital verifies independently with openssl. No vendor trust required. The incentive: customers (clinics) can process deterministic evidence independent of the vendor or tool (my code) and the vendors agents build up a track record of trust by themselves without engineers spending their time triaging.

New comment by keertahacker in "Show HN: Health billing agent denies claims in 1.2s, offices should know why"

keertahacker — Thu, 16 Apr 2026 17:01:54 +0000

A doctor friend asked me about billing agents their mixed experience not being able to dispute the agent due to abstractions. Wanted your thoughts. I feel agents should prove they are trustworthy and transparent to the human in the loop as in the end user, not the developer.

I built a tool where every AI agent action gets an Ed25519 signed receipt, hash-chained, and exported as a folder anyone can verify with openssl. No vendor software needed to verify.

The demo runs 20 simulated insurance claims sessions — standard agents and rogue agents. Every action is signed. Rogue actions are blocked and the blocks are signed too.

$ pip install agentmint && python -m agentmint.demo.healthcare

Cross-patient access: 10 attempts → 10 blocked Auto-deny (no review): 10 attempts → 10 blocked Prompt injection: 10 attempts → 10 caught before LLM

To run it: clone then cd agentmint-python/ Verify: cd healthcare_evidence && bash VERIFY.sh GitHub: https://github.com/aniketh-maddipati/agentmint-python/tree/m...

Also Would love to hear: Should verification require zero dependency on the vendor, or is that overkill?

Tear it apart, tell me what I can do to make it better. If you have thoughts on ways to make trust a currency for agents, comment below

Show HN: Health billing agent denies claims in 1.2s, offices should know why

keertahacker — Thu, 16 Apr 2026 16:53:41 +0000

Comments URL: https://news.ycombinator.com/item?id=47796200

Points: 1

# Comments: 4

Show HN: AgentMint – Open-source OWASP compliance for AI agent tool calls

keertahacker — Thu, 09 Apr 2026 16:55:39 +0000

Article URL: https://github.com/aniketh-maddipati/agentmint-python

Comments URL: https://news.ycombinator.com/item?id=47706092

Points: 5

# Comments: 0

AgentMint – Runtime enforcement for AI agent tool calls

keertahacker — Tue, 24 Mar 2026 13:35:29 +0000

Article URL: https://github.com/aniketh-maddipati/agentmint-python

Comments URL: https://news.ycombinator.com/item?id=47502379

Points: 1

# Comments: 1