How POLYROB compares
POLYROB is a goal-achieving, self-evolving, crypto-native agent — and a base you can ship products on. It's MIT-licensed and self-hosted: the full engine, free forever, yours to fork and run — not a limited open core wrapped around a paid cloud. The table below compares capabilities and architecture — the axes we can state about ourselves first-party.
| Capability | POLYROB | Hermes | OpenClaw |
|---|---|---|---|
| License | MIT | MIT | MIT |
| Goal-achieving autonomy | ✓ durable goal board + cron | ⚠ cron only | ✗ |
| Self-evolving skills | ✓ writes + curates | ✓ learning loop | ✓ workspace |
| Cross-session memory | ✓ H-MEM hierarchical | ✓ FTS5 | ✓ FTS5 |
| Agent wallet | ✓ policy-capped + audited | ✗ | ✗ |
| On-chain payments (x402) | ✓ USDC on Base | ✗ | ✗ |
| On-chain identity + reputation (ERC-8004) | ✓ 3 registries | ✗ | ✗ |
| Security model | ✓ 3-tier access + capability gates | ⚠ pairing | ✓ sandbox |
| Prompt-injection defense | ✓ untrusted-output wrapping | ⚠ partial | ⚠ partial |
| Multi-tenant + billing | ✓ isolation + metering + credits | ✗ single-user | ✗ single-user |
| Standard agent APIs | ✓ REST + OpenAI-compat + A2A | ✗ | ✗ |
| Use any of 6+ providers | ✓ | ✓ | ✓ |
| MCP support | ✓ full client | ✓ | ✓ |
| Browser automation | ✓ Playwright | ✓ | ✓ |
| Chat surfaces (one contract) | ✓ CLI / Telegram / WhatsApp / email | ✓ | ✓ |
✓ supported ⚠ partial/limited ✗ not supported
When to choose POLYROB
You want goals chased, not chatted
Durable goals + autonomy loops that run unattended, survive restarts, and deliver — and an agent that evolves its own skills as it goes.
You want a crypto-native agent
A built-in wallet and x402 pay-per-request in USDC on Base — the agent pays for what it uses and can charge for its own work.
You're building an agent product
Multi-tenant isolation, metering + credits, and standard APIs (REST / OpenAI-compat / A2A) are in the core — ship a paid agent without a backend. MIT, self-hosted.