Skip to content
x401 logo

x401

Defines an HTTP handshake where a route demands signed identity proof and agents return a credential to retry.

Actively maintained

At a glanceswept Oct 17, 2026

not read yet

Use

For
Developers of services and AI agents that must prove identity over plain HTTP requests
Activity
Actively maintainedrelease 10 days ago
Company
Notarize, Inc. · Domain since 2026site footer · domain registered
Runs as
SDK
Used for
  • require identity proof before a route serves an agent
  • verify a credential from a trusted issuer on retry
  • step up authentication for high-risk actions like wire changes
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Jun 25, 2026Product Hunt ↗
Your datawhat they publish, each line with its page · read Oct 23, 2026

These are x401's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

Alternatives in Developer toolsby use, among tools still maintained

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

Compare x401 with

Pick up to two.

All 10 alternatives to x401 →

All Developer tools 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 x401 for?

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

    Defines an HTTP handshake where a route demands signed identity proof and agents return a credential to retry. It is listed in the Atlas under Developer tools and made by Notarize, Inc.

  • Who is x401 for?

    Developers of services and AI agents that must prove identity over plain HTTP requests

  • Do people use x401?

    Emerging.

  • Is x401 still maintained?

    Actively maintained: release 10 days ago.

  • Who owns x401?

    x401 is run by Notarize, Inc., per its site footer (2026-10-23).

  • What are alternatives to x401?

    In Developer tools, by use: Experiential Labs, GitMir, Treg, Scrollport, MintyCode, Sparta.

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