Skip to main content

elizaOS Developer Tools

Free, private, client-side utilities for elizaOS agent builders — from the plugin-formatho native plugin to browser-side config checkers. Everything runs on your machine. No tracking, ever.

The native plugin: 9 pure-function actions

Install once and your elizaOS agent gains everyday dev utilities as native actions — no Docker, no API keys, no config. Every action is a synchronous pure function.

# add to any elizaOS project
elizaos plugins add plugin-formatho
keccak256
keccak256: hello world
0x47173285a8d7341e5e972fc677286384f802f8ef42a5ec5f03bbfa254cb01fad
function selector
selector: transfer(address,uint256)
0xa9059cbb
EIP-55 checksum
checksum: 0x5aaeb6053f3e94c9b9a09f33669435e7ef1beaed
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed
JSON validate & format
json: {"a":1}
pretty-printed or the exact parse error
base64 + URL-safe
base64: hello eliza
aGVsbG8gZWxpemE= (and url-safe variant)
unix timestamp ↔ ISO
timestamp: 1760000000
2025-10-09T08:53:20.000Z
URL encode & decode
url: https://formatho.com/?q=a b
percent-encoded or decoded form
HTML entities
entities: Café & Co
Café & Co — encode or decode
JWT decode
jwt: eyJhbGciOi...
header + payload, decoded locally — never validated online

Browser tools for agent configs

coming soon
Character-file validator

Validate your elizaOS character config against the real schema: missing required fields, type errors, empty style/bio, bad messageExamples.

coming soon
.env hygiene checker

Client-side scan of agent .env files: duplicate keys, empty values, quote issues, and known elizaOS variable names. Nothing is ever uploaded.

coming soon
Plugin manifest linter

Lint your plugin package.json against the elizaOS registry conventions: name scope, version, and description rules.

Want all 26 tools + audit logs?

The full Formatho runtime gives your elizaOS agent 26 tools — web3, security, data formats, compliance — behind a self-hosted MCP server with per-client keys, policies, and audit logs. Works with elizaOS agents today via @elizaos/plugin-mcp:

# self-hosted, works with elizaOS agents
docker run -p 3000:3000 formatho/formatho-runtime
Explore the runtime

Why private?

Agent configs, JWTs, and .env contents are the keys to your infrastructure. Pasting them into a random web tool means sending secrets over the network. Formatho tools never do that.

  • Zero network — no fetch, no APIs, no telemetry
  • Zero filesystem — nothing is read or written
  • Zero secrets — no env vars, no keys, no config
  • Pure functions: values in, values out — auditable in one sitting