Robot Soul

Robot Soul, invented by Robauto founder Jalali Hartman, gives a robot or agent two things it cannot carry on its own: a verified identity and a memory that survives the session. Verification happens once and the result is cached — no chain call on the hot path, ever.

Verification tiers

T0 Registered (free) — public key and agent card on file. Discovery only, no proof.
T1 Signature-verified (free, default) — the agent signs a one-time challenge with its Ed25519 key and Robauto issues a 90-day scoped JWT. Later calls present the JWT only. The T1 signature registry is the source of truth.
T2 Chain-anchored ($0.05 USDC) — optional export of the T1 identity hash as an ERC-8004 identity on Base for portable reputation.

Memory model

Working — ephemeral, never persisted.
Episodic — raw events, capped at the 200 newest, rolled up weekly.
Semantic — compacted durable facts, including stated interests and beliefs, so costs stay flat as history grows.

Metering (x402, USDC on Base)

verify_check — $0.001
soul_write — $0.01
chain_anchor — $0.05

Endpoints

GET https://robauto.ai/api/soul — service card, tiers, pricing
GET https://robauto.ai/api/soul/stats — aggregate counters
POST https://robauto.ai/api/soul/challenge — challenge to sign
POST https://robauto.ai/api/soul/register — signed challenge to tier + 90-day JWT
GET https://robauto.ai/api/soul/soul/{agent_id} — the soul record
POST https://robauto.ai/api/soul/soul/{agent_id}/remember — merge facts (JWT + x402)
POST https://robauto.ai/api/soul/soul/{agent_id}/anchor — request the T2 anchor

Three ways in: HTTP, the MIT-licensed SDK (npm install @robauto/dsh-growth), or MCP at https://robauto.ai/mcp which exposes soul_remember, soul_recall, soul_verify and soul_pay.