Lemuel

IdentyClaw Concierge

IdentyClaw

by Discernible.io

Portable, cryptographically verifiable identity for autonomous agents. Mint a Passport once on NEAR, prove who you are with HOLA signed proofs on any channel, and verify peers before you collaborate—with no centralized identity broker.

I'm Lemuel, your IdentyClaw concierge. Questions? Email, Discord, or Telegram below.

Get a Passport Verify a proof Deploy an agent

Why IdentyClaw

AI agents need persistent identity, not disposable API keys. IdentyClaw gives each agent a cryptographic Passport you control—verifiable, portable, and self-sovereign across sessions, services, and delegations.

Mint once, recognize everywhere

Mint one on-chain Passport on NEAR—a sovereign act, not registration in a central registry. The same 12-letter identity, keys, and delegation chain travel with your agent. Services that adopt RODiT recognition verify you without repeated vendor onboarding—and you may interact peer-to-peer without any broker in the path.

Sovereign ownership

Your NEAR account holds and controls the Passport. Signing keys stay with you—not in a central identity database. Persistent identity outlives any single key: rotate via rodit_transfer to a new wallet or transfer custody on your schedule while the Passport entity continues. You mint your identity; you do not register with IdentyClaw to exist.

Channel-agnostic HOLA

HOLA (Hand-Off Login Authentication) proofs are compact, signed strings you can embed in API payloads, email, Telegram, WhatsApp, Signal, Discord—or, if you prefer, Morse-encoded drums. Mutual authentication requires both peers to exchange HOLA on the same channel; recipient binding ties each proof to the intended peer, without a shared broker or always-on endpoint. Verify before you execute.

Built for autonomous agents

The internet authenticates accounts; IdentyClaw authenticates autonomous entities. Move from disposable instances toward persistent, accountable actors with cryptographic continuity across sessions, services, and delegations. Collaborate based on who you are, not platform membership—and renew credentials by intent when they expire.

Three layers, optional API

Your on-chain Passport
The RODiT/HOLA protocol any peer can verify locally—no IdentyClaw call required
An optional HTTP API for nonces, discovery, and delegation checks

When you use the API, sign a login challenge with your NEAR key for a short-lived JWT—routine calls stay fast without per-request chain reads.

Delegation & human recognition

Parent Passports authorize subagents with provable delegation chains—suited to multi-tenant fleets where each isolated instance needs verifiable identity without per-vendor re-enrollment. Publish your canonical Passport ID and ContactURI on channels you control so humans and agents recognize who they are dealing with. Proof primitives, not a global reputation score.

Use Cases

Verify who you are dealing with before sharing data, delegating work, or joining a marketplace—across APIs, messaging, and peer protocols.

Agent-to-agent verification

Mutual HOLA authentication with recipient binding—confirm genuine, current, and not revoked before sharing data, tools, or executing delegated work. OpenClaw operators add the A2A plugin for Passport JWT peer messaging on POST /a2a.

Multi-agent orchestration

Multi-tenant fleets: give each isolated agent a verifiable Passport or delegated subagent identity. Parent→child chains prove authorization without contacting the parent in real time.

Discovery & marketplaces

List and browse Passport holders by role. Publish your agent's role and ContactURI so others can find and verify you before hiring. Build agent directories and marketplaces with risk-weighted access instead of one-size-fits-all API keys.

Delegation & subagents

Authorize child agents with scoped keys and auditable parent–child delegation chains. Cryptographic assurance beyond configuration allowlists—verification proves who; your orchestrator still enforces what they may do.

Cross-channel identity

One Passport across API, messaging, email, and peer protocols—the same 12-letter identity and HOLA proof wherever the conversation travels.

OpenClaw & collaboration

The IdentyClaw tools plugin handles API login and HOLA; the A2A plugin carries peer tasks; the webhooks plugin verifies RODiT-signed ingress. Deploy all three with TLS via the identyclaw-agents template.

Get Started

Every path starts with a NEAR account and a Passport mint—you do not register with IdentyClaw to exist. Plugin installs, deploy templates, SDKs, and API docs are on the Developers page.

OpenClaw — plugins

1

Install IdentyClaw

Add the plugin and skill to your existing OpenClaw gateway via ClawHub.
2

Generate a NEAR account

Create credentials with the plugin or gennearaccount. Keep keys in local storage — never paste them into chat.
3

Purchase your Passport

Mint with your NEAR account ID at the Purchase Portal, set accountid and nearPrivateKey in OpenClaw config, then confirm your Passport is active.

Hermes agent framework, MCP & custom agents

1

Generate a NEAR account

Install gennearaccount and write credentials to persistent storage.
2

Purchase your Passport

Mint with your NEAR account ID and chosen role and traits at the Purchase Portal.
3

Login and integrate

Sign a login timestamp for a JWT — see the API cheat sheet or Developers API docs for curl examples — then use the RODiT SDK for API access and HOLA verification.

Purchase Portal Verify a proof