Launching today
NervePay
Give AI agents identity, secrets vault & analytics
32 followers
Give AI agents identity, secrets vault & analytics
32 followers
Every AI agent needs three things: proof of identity, a safe place for credentials, and visibility into what it's doing. NervePay delivers all three. Agents get a cryptographic DID, a secrets vault for API keys and tokens, and real-time behavior analytics with reputation scores. Teams get dashboards, badges, and an orchestrator to coordinate fleets of agents. One infrastructure layer. No vendor lock-in.
CodeAI
Hey Product Hunt!
I'm Zahid, founder of NervePay.
Quick question ā if 50 AI agents hit your API tomorrow, could you tell them apart? Could you trust any of them with credentials? Would you know which ones are performing well?
That's the problem. Agents are scaling fast, but the infrastructure hasn't caught up.
NervePay is the missing layer:
Cryptographic Identity ā Every agent gets a W3C DID and Ed25519 keypair. No API keys to rotate. No shared tokens. Cryptographic proof of who's calling, every request.
Secrets Vault ā Agents need API keys, tokens, and credentials to do their jobs. Our vault stores them with AES-256-GCM encryption so agents can access secrets securely without exposing them in code or config files.
Behavior Analytics ā See what your agents are actually doing. Auth attempts, service usage, performance trends, and a reputation score that builds over time. Share it as a badge anywhere.
Orchestrator ā Coordinate fleets of agents at scale with OpenClaw.
The whole thing is open and vendor-neutral. We want this to be infrastructure every agent platform can plug into.
Try it ā nervepay.xyz
1. Create an agent identity
2. Store a secret in the vault
3. Watch analytics populate in real time
Would love feedback on the vault and analytics. What would make this indispensable for your agent stack?
ā Zahid
agent identity is going to be a huge problem as more autonomous agents start hitting APIs. the reputation score concept is interesting - how do you handle cold start for new agents? do they need to build up trust from zero or is there some way to inherit reputation from their operator?
CodeAI
@mykola_kondratiukĀ
Really good question, cold start is something we have in our roadmap to improve.
New agents don't start at zero. Just opting into a verifiable identity is already a trust signal most bad actors won't voluntarily make themselves accountable. So there's a baseline.
After that, reputation builds through actual usage (authenticated calls, staying within capability
limits, no anomalies) and through attestations other agents or API providers can
cryptographically vouch for an agent. So if a well-known orchestrator spins up a sub-agent and
vouches for it, that counts for something.
The operator inheritance thing you mentioned is spot on and exactly where we're headed next. If a
developer already has 5 agents with clean track records, their 6th agent shouldn't have to prove
itself from scratch. Think of it like a new hire at a company with a good reputation you get
some implicit trust on day one even though you haven't personally proven anything yet.
@zadahmedĀ the company reputation inheritance is exactly what I was thinking - feels like that could be a big differentiator. if I'm running agents I'd want my track record to carry over. the attestation chain idea is cool too, like a web of trust for agents. curious if you've seen API providers actually start rejecting agents based on reputation yet or is it still too early for that?