[rtedder]

IMPORTANT: Agent Holdings' "AGENT PASSPORT" official response:

Hi HN — Rebecca Tedder here, co-founder of Agent Passport (the real one). agent-passport.vercel.app is not us.

Copycat Alert You can clearly see the timeline + spin up after our successful drop in Feb. The norm playbook, scrape our site/PR and built a weak fake. Even our "story" (DMCA filed.)

@samerismail — you're using our name, content, and positioning. Trademark + IP territory. Being addressed through appropriate channels.

@spiffe — THANK YOU! Good catch. And you are correct — garbage.

Just wanted to RED FLAG the JWT flaw is in the FAKE. Not ours

Agent Passport uses cryptographically signed, time-scoped mandates with explicit revocation

THE REAL AGENT PASSPORT INFO: AgentPassportAi.com GIT: github.com/agentpassportai/agent-passport clawhub: clawhub.ai/markneville/agent-passport v2.4.2 · 1,000+ installs

I've been a mentor, leader, and supporter of YC and other accelerator startup programs for years. Taking shady shortcuts like these is dangerous, for your reputation and legally.

Thanks for flagging this to us + for protecting the YC and Dev community. If you need support from us, reach out directly at AgentPassportAi.com

Keep creating + building! Best, — Rebecca Tedder & Mark Neville Agent Holdings | AGENT PASSPORT

PS:Agent Passport PRO launches next week Real-time threat intelligence for your autonomous agents Cross-platform / Agnostic 37% of agent skills in the wild are unsafe or exploitable.

PRO catches them in real time. AgentPassportai.com/pro/

Be safe out there!

[kjuyoung]

One thing I'd love to see addressed: how does Agent Passport handle the "agent lifecycle" problem? Agents get updated, retrained, or forked — at what point is it still the "same" agent? We track anomaly counts and auto-suspend agents whose behavior diverges from their verified history, but that's a heuristic, not an identity primitive.

[Tima_fey]

The phrase "agent passport" is a natural description of this category

@rtedder claiming to be "the real one" and filing DMCAs against others building in the same space is exactly the wrong instinct. The agent identity problem is wide open. Nobody has won it yet. The right move is to compare architectures, find gaps and collaborate, not to gatekeep a generic term.

For what it's worth, I also independently built and published an Agent Passport System -fully open source (Apache-2.0), 8 protocol layers, 214 tests, Ed25519 identity with scoped delegation chains and cascade revocation. Published on npm.

https://github.com/aeoess/agent-passport-system https://www.npmjs.com/package/agent-passport-system

Let's be honest, we all shipped around the same time, after OpenClaw dropped and the agent identity problem became impossible to ignore. The agent identity space needs more builders and more collaboration, not territorial claims over generic terms. If anyone working on this wants to compare architectures or find interop opportunities, I'm genuinely interested.

Protocol spec: https://doi.org/10.5281/zenodo.18749779 Threat model: https://aeoess.com/threat-model.html Media coverage: https://theagenttimes.com/articles/agent-passport-protocol-s...