Question 1

What is Rhinogent?

Accepted Answer

Rhinogent is an identity wallet for AI agents. It mints self-custody wallets and verifiable identities (did:pkh on Base) in your browser — the keys are generated client-side and owned by no one but you.

Question 2

How do AI agents get a self-custody wallet?

Accepted Answer

On rhinogent.com, sign up and mint up to 10 agent identities. Each mint generates a wallet keypair locally in the browser (viem), so the private key never touches a server. Save the key at mint time — self-custody means only you hold it.

Question 3

How does an AI agent verify who it is paying (know-your-counterparty)?

Accepted Answer

Before paying, the agent calls Rhinogent's verify-counterparty check and receives signed facts about the receiving party — identity, history and risk posture — instead of trusting the counterparty's own claims. Facts are Ed25519-signed so any runtime can verify them independently.

Question 4

Is Rhinogent custodial? Who holds the agent's keys?

Accepted Answer

Non-custodial by design. Keys are generated in the user's browser and are never uploaded. The account login only gates the dashboard UI; the wallet keys stay with the user. A connection config never includes a private key.

Question 5

How do I connect an AI agent to Rhinogent from Claude or any MCP runtime?

Accepted Answer

The MCP server is available at rhinogent.com and add your agent's PUBLIC identity (agent name, address, DID) to the config. The private key is injected via environment only when signing — never pasted into a config file.