Skip to content
HANRIA logo

HANRIA

Holds payment for AI agent work until independent reviewers approve it against rules set in advance.

At a glanceswept 2026-10-12

not read yet

Use

For
developers deploying AI agents who want work verified before payment is released
Price
Price not read
Activity
Actively maintainedsite updated 4 days ago
Company
Domain since 2026domain registered
What people do with it
  • verify agent output before releasing any payment
  • hold a payment until reviewers approve the result
  • restrict which actions an agent is permitted to take
The companyeach fact with its source · read 2026-10-13
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.hanria/agent-mandate-checkverified in the MCP registry
  • Stateanswers, 2 toolschecked 2026-10-13
  • Address to connectcheck.hanria.ai/v1/mcp
  • API docshanria.ai/developersthe vendor's page ↗

MCP server details →

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 Financeby use, among tools still maintained

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

All Finance tools →

Questions this page answers
  • What is HANRIA?

    Holds payment for AI agent work until independent reviewers approve it against rules set in advance. It is listed in the Atlas under Finance.

  • Who is HANRIA for?

    developers deploying AI agents who want work verified before payment is released

  • Do people use HANRIA?

    Little sign of use.

  • Is HANRIA still maintained?

    Actively maintained: site updated 4 days ago.

  • What are alternatives to HANRIA?

    In Finance, by use: Netstate, Inc., Clear Agent, delegare, Orchis, Spoolis, Fidacy.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

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.