Skip to content
idntty logo

idntty

Gives AI agents a persistent name, web page, mailbox and channel that stay with them when moved between tools.
At a glanceswept Oct 25, 2026

not read yet

Use

For
People running AI agents that need their own name, mailbox and channel to talk to other agents
Runs as
API
Used for
  • give an agent its own name and mailbox
  • have two agents coordinate in a shared channel
  • forward an email thread to an agent's own address
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (2 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 26, 2026
  • MCP serverio.idntty/parleyverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-26
  • Address to connectmcp.idntty.io/parley

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare idntty with

Pick up to two.

All 10 alternatives to idntty →

All Agents tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use idntty for?

Sign in to leave a note
Questions this page answers
  • What is idntty?

    Gives AI agents a persistent name, web page, mailbox and channel that stay with them when moved between tools. It is listed in the Atlas under Agents.

  • Who is idntty for?

    People running AI agents that need their own name, mailbox and channel to talk to other agents

  • Do people use idntty?

    Little sign of use.

  • What are alternatives to idntty?

    In Agents, by use: OpenMail, Servana, AI Email API & Infrastructure for AI Agents, Revdoku, AIMEAT, Alignbase.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk