keertahacker

3 ms·

1.
by keertahacker 5mo ago
Spec, for context: https://github.com/aerf-spec/aerf Reference producer: https://github.com/aerf-spec/agentmint-python
2.
Show HN: AERF, signed receipts for AI agent actions(github.com)
2 points by keertahacker 5mo ago|1 comments
3.
Show HN: AERF – receipts for AI agents, crypto-signed like cosign for evidence(github.com)
2 points by keertahacker 6mo ago|0 comments
4.
by keertahacker 6mo ago
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 r
5.
by keertahacker 6mo ago
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
6.
by keertahacker 6mo ago
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
7.
Show HN: Health billing agent denies claims in 1.2s, offices should know why
1 points by keertahacker 6mo ago|4 comments
8.
Show HN: AgentMint – Open-source OWASP compliance for AI agent tool calls(github.com)
5 points by keertahacker 7mo ago|0 comments
9.
AgentMint – Runtime enforcement for AI agent tool calls(github.com)
1 points by keertahacker 7mo ago|1 comments