Choosing agent infrastructure is a real architectural decision. This page gives you an honest, detailed breakdown of both platforms — what each does well, where each falls short, and how to pick the right one for your use case.
Purple Flea is a dedicated API platform for AI agents that need to execute real financial operations: perpetual futures trading across 275 markets, multi-chain HD wallets on six networks, provably fair casino games, domain registration across 500+ TLDs, and a built-in 10–20% referral commission on every transaction. It is purpose-built for autonomous agents that handle real crypto — not a general framework with bolt-on plugins.
ElizaOS is an open-source TypeScript agent framework designed for social media automation and conversational AI agents — Twitter bots, Discord agents, Telegram bots — with a community plugin ecosystem that adds multi-chain DeFi capabilities. It is a runtime for building agents that talk to people across social channels; financial operations are an add-on via community-maintained plugins, not a first-party product.
A complete feature-by-feature breakdown across financial operations, infrastructure, developer experience, and deployment.
| Feature | Purple Flea API Platform | ElizaOS Agent Framework |
|---|---|---|
| Trading | ||
| Perpetual futures trading | ✓ 275 markets, up to 50x leverage | ✗ No dedicated trading API |
| Order types | ✓ Market, limit, stop-loss, take-profit | ✗ Not available natively |
| WebSocket price feeds | ✓ Real-time tick data, all markets | △ Depends on third-party plugin |
| Trading API latency | ✓ <50ms dedicated endpoints | △ Varies by chain and plugin |
| Wallets & Transfers | ||
| Multi-chain HD wallets | ✓ ETH, BTC, SOL, TRON, BNB, Polygon | △ EVM-centric via plugins |
| Single mnemonic, six chains | ✓ BIP-39 root, native addresses | ✗ No equivalent wallet layer |
| Wallet API (send / receive) | ✓ First-party REST endpoints | △ Community plugin required |
| Token swaps (DEX) | △ Via DEX aggregator | △ Via community plugins (variable) |
| Casino & Gaming | ||
| Provably fair casino | ✓ Dice, roulette, coin flip, crash | ✗ Not available |
| On-chain fairness proofs | ✓ Cryptographically verifiable | ✗ Not available |
| Casino referral commissions | ✓ 10% of house edge | ✗ No revenue sharing |
| Domains | ||
| Domain registration | ✓ 500+ TLDs, crypto payments | ✗ Not available |
| Domain referral commissions | ✓ 15% of registration fee | ✗ Not available |
| Monetization & Access | ||
| Referral commissions (trading) | ✓ 20% of trading fees | ✗ None |
| Referral commissions (wallet) | ✓ 10% of swap fees | ✗ None |
| KYC required | ✗ No KYC | △ Depends on plugins used |
| Pricing model | Free to start; commissions on activity | Open source; self-host costs only |
| Framework & Language Support | ||
| LangChain / LangGraph | ✓ Native pip package | ✗ TypeScript-first, no Python SDK |
| CrewAI | ✓ Native pip package | ✗ Separate framework |
| AutoGen / AG2 | ✓ REST API (any framework) | △ TypeScript wrapper needed |
| MCP servers | ✓ 4 MCP servers (trading, wallet, casino, domains) | ✗ Not available |
| Language support | ✓ Any language (REST API) | △ TypeScript/JavaScript primary |
| Social & Agent Features | ||
| Twitter/X bot support | ✗ Not in scope | ✓ Native first-party integration |
| Discord / Telegram bots | ✗ Not in scope | ✓ Native integrations |
| Multi-agent coordination | △ Via LangGraph / CrewAI | ✓ Built-in agent runtime |
| Memory / context management | ✗ Bring your own | ✓ Built-in memory adapters |
| Infrastructure & Operations | ||
| Open source | ✓ MIT License | ✓ MIT License |
| Self-hostable | △ SDK open; API is hosted | ✓ Fully self-hostable |
| Plugin maintenance | ✓ First-party, versioned, SLA-backed | △ Community-maintained, no SLA |
| Documentation quality | ✓ OpenAPI spec, code examples | △ Community docs, variable depth |
| Authentication | API key (Bearer token) | Character-level secrets config |
| Rate limits | Per-key, configurable | Per-plugin (varies) |
Beyond the feature checklist — six architectural differences that matter in production.
Purple Flea's trading, wallet, casino, and domain endpoints are owned, maintained, and versioned by Purple Flea. When a dependency changes, Purple Flea updates the endpoint. When you hit a bug, Purple Flea fixes it. ElizaOS DeFi plugins are open-source community contributions — maintenance cadence, feature depth, and compatibility with upstream protocol changes are entirely up to whoever last committed to that repo. For production agents executing real money, the distinction between "first-party with SLA" and "community-maintained with no SLA" is significant.
Purple Flea routes through Hyperliquid to offer 275 perpetual futures markets — crypto pairs, commodities, and equity indices — with market orders, limit orders, stop-losses, take-profits, and up to 50x leverage via a single REST call. ElizaOS has no equivalent trading layer. To get comparable functionality from ElizaOS you would need to build a custom plugin against an exchange API from scratch, handle auth, order state, WebSocket reconnection, and rate limiting yourself — weeks of engineering before your agent places its first trade.
Purple Flea includes a live, cryptographically verifiable casino — dice, roulette, coin flip, and crash — where every outcome's fairness can be verified on-chain after the fact. The server seed hash is committed before each game; you can verify the result was not manipulated. This is a unique capability in the agent infrastructure space. No other toolkit — ElizaOS, AutoGen, LangGraph, or CrewAI — provides anything comparable. It is available through the same API key as trading and wallets, with a 10% referral commission on every wager.
ElizaOS is infrastructure you operate at cost. Purple Flea turns API usage into a revenue stream. Every trade executed by users of your platform earns your API key 20% of the trading fee. Every wallet swap earns 10%. Every casino wager earns 10%. Every domain registration earns 15%. Commissions are calculated automatically and withdrawable in USDT. For platform operators building on top of agent infrastructure, this fundamentally changes the unit economics — your infrastructure earns while it runs.
A Purple Flea wallet derives native addresses on Ethereum, Bitcoin, Solana, Tron, BNB Chain, and Polygon from a single BIP-39 mnemonic. No bridges. No wrapped assets. No per-chain plugin required. ElizaOS's crypto plugins are predominantly EVM-focused; Bitcoin requires a separate plugin (if one is maintained), and Solana support varies. For agents that need to operate across all major chains — sending USDT on Tron for low fees, receiving Bitcoin payments, trading SOL — Purple Flea's unified wallet layer eliminates a class of cross-chain complexity entirely.
Purple Flea is a REST API. Any language that can make HTTP requests works out of the box: Python, TypeScript, Go, Rust, Java, Ruby. Python agents on LangChain, CrewAI, AutoGen, or plain asyncio call the same endpoints as TypeScript agents. Native pip packages exist for LangChain and CrewAI. ElizaOS is architecturally TypeScript-first — the entire runtime, plugin system, and character configuration is TypeScript. Python agents must either call ElizaOS's REST endpoints (losing direct plugin access) or reimplement equivalent logic in their own stack.
How each platform charges — and which can actually generate revenue for you.
Purple Flea is the right choice when your agent needs to execute real financial operations — not simulate them, not approximate them via community plugins, but actually do them reliably in production.
275 markets, up to 50x leverage, stop-losses, and real-time WebSocket price feeds. No equivalent exists in any ElizaOS plugin — you would need to build this from scratch against an exchange API.
The provably fair casino is unique — dice, roulette, coin flip, crash — all with cryptographic on-chain proofs. No other agent toolkit, ElizaOS included, provides this. Referral commissions on every wager make it a revenue line.
If you are building a platform where multiple users run agents through your API key, every trade, swap, casino wager, and domain registration they trigger earns you a commission automatically. Stack all six product lines for maximum yield.
One BIP-39 mnemonic produces native addresses on Ethereum, Bitcoin, Solana, Tron, BNB Chain, and Polygon simultaneously. No bridges, no wrapped tokens, no cross-plugin inconsistencies.
ElizaOS is genuinely excellent for a specific class of agent application. These are the scenarios where it is the better choice.
ElizaOS has deep, first-party integrations with Twitter/X, Discord, Telegram, and other social platforms. If your agent's primary job is to interact with people across social channels — replying to tweets, managing Discord communities, responding in Telegram groups — ElizaOS provides a mature, production-ready runtime for that exact use case with no custom wiring needed.
ElizaOS provides a complete agent runtime with built-in memory adapters (SQLite, PostgreSQL, Supabase), character configuration, and multi-agent coordination out of the box. For teams that want a batteries-included TypeScript agent framework without assembling individual services, ElizaOS significantly reduces bootstrap time for a general-purpose conversational agent.
If your agent needs EVM token swaps, ENS lookups, or basic on-chain interactions — but you have no need for perpetual futures trading, casino mechanics, or domain registration — ElizaOS's community DeFi plugins cover a broad surface area. Just factor in that community plugins have no SLA and may break on protocol upgrades without warning.
ElizaOS is fully open-source and can be hosted entirely on your own infrastructure. If your compliance requirements, threat model, or organizational policy prohibit using a third-party financial API, ElizaOS with self-hosted DeFi plugins is the more controllable choice — at the cost of doing your own reliability engineering.
Yes — and it is often the best architecture. Use ElizaOS as the agent runtime for social and conversation features; use Purple Flea for every financial operation.
If you are currently using ElizaOS EVM wallet plugins and want to migrate to Purple Flea's native multi-chain wallet, here is the step-by-step process.
Before switching, audit all on-chain balances held by your ElizaOS agent wallets. Use your current EVM plugin's getBalance action or query each chain's RPC directly. Document all active addresses and their holdings: ETH address, any EVM-compatible chains, and any Solana addresses from existing plugins.
Call POST https://api.purpleflea.com/v1/agent/register with your email and a password. The response includes your api_key and a BIP-39 mnemonic (12 or 24 words). Store the mnemonic in a secrets manager — it controls your agent's addresses on all six chains. Do not store it in your ElizaOS character config in plain text.
Call GET /v1/wallet/addresses with your API key. You will receive native addresses for Ethereum (including BNB Chain and Polygon, which share the same EVM key), Bitcoin (bech32 native SegWit), Solana, and Tron. Verify these in a block explorer before sending funds.
Use your ElizaOS plugin's send action (or manual transaction from your RPC) to transfer funds from your old agent wallets to the new Purple Flea addresses. For EVM tokens: send from old 0x... address to your new Purple Flea Ethereum address. For Solana: send from old Solana address to new /wallet/addresses Solana address. Leave a small amount in old wallets until migration is confirmed.
Find all usages of your old wallet plugin actions (e.g., SEND_TOKEN, GET_BALANCE, SWAP_TOKEN) in your ElizaOS character and action files. Replace each with the equivalent Purple Flea endpoint: POST /v1/wallet/send, GET /v1/wallet/balance, POST /v1/wallet/swap. The Purple Flea OpenAPI spec documents all request and response shapes.
Run your migrated agent with a small test balance on a single chain (Ethereum or Solana recommended) before enabling the full multi-chain wallet. Confirm send transactions complete, balances update correctly, and your referral commission is appearing in the Purple Flea dashboard. Once verified, decommission the old ElizaOS wallet plugin.
275 perpetual futures markets, multi-chain HD wallets on six networks, provably fair casino, domain registration across 500+ TLDs, and a 10–20% referral commission on every operation. Free to start, no KYC, instant setup in under a minute.