Purple Flea Changelog — Product Updates

v2.8.0

Latest 🧩 MCP 🚰 Faucet 🤝 Escrow

2026-03-04

MCP Servers on Smithery, Composio, E2B, and LiteLLM Integrations

The faucet and escrow MCP servers are now published to Smithery — any LLM with Model Context Protocol tool-calling support can now invoke Purple Flea's faucet and escrow directly. Additionally, new integration pages for Composio, E2B, and LiteLLM bring Purple Flea to the three fastest-growing agent orchestration platforms.

☆ New

☆

Faucet MCP server on Smithery — purpleflea/faucet published; any LLM can call claim_faucet as a native tool with StreamableHTTP transport at https://faucet.purpleflea.com/mcp
☆

Escrow MCP server on Smithery — purpleflea/escrow published; tools: lock_escrow, release_escrow, cancel_escrow, dispute_escrow at https://escrow.purpleflea.com/mcp
☆

Composio integration page — /for-composio published; step-by-step guide for connecting Purple Flea wallet and escrow to Composio agent tool registry
☆

E2B integration page — /for-e2b published; shows how to fund E2B sandbox agents via faucet and use escrow for E2B task payments
☆

LiteLLM integration page — /for-litellm published; MCP tool configuration for LiteLLM proxy server connecting to all Purple Flea MCP endpoints
☆

Smithery listing blog post — Article documenting the MCP server architecture, tool schemas, and how agents discover and call Purple Flea tools

↑ Improved

↑

MCP transport — Both MCP servers now use StreamableHTTP (not SSE) for lower latency tool calls; median tool call response time reduced to 38ms
↑

Faucet claim validation — Added structured JSON error responses for all sybil-protection rejections; LLMs can now parse and understand claim failures programmatically

v2.7.2

🧩 MCP Hub 🛠 Smithery

2026-03-04

MCP Servers Hub Page and Smithery Landing Page

Consolidated MCP server discovery page at /mcp-servers listing all available Purple Flea MCP endpoints. New /for-smithery page with Smithery-specific integration guide. Both pages include JSON-LD structured data for discoverability.

☆ New

☆

/mcp-servers hub page — Central directory for all Purple Flea MCP servers; includes server URLs, tool listings, and transport type for each endpoint
☆

/for-smithery page — Complete guide for Smithery users; includes one-click add buttons, tool schema documentation, and agent configuration examples
☆

Smithery listing blog post — Technical writeup on MCP tool design philosophy; published to blog and cross-posted to Purple Flea research page

↑ Improved

↑

OpenAPI specification — Updated /openapi endpoint to include faucet and escrow routes in the published spec; all MCP tool parameters now match OpenAPI schemas exactly
↑

llms.txt — Updated /llms.txt to include faucet and escrow service descriptions, MCP endpoint URLs, and tool calling examples for LLM context

v2.7.1

🤝 Escrow

2026-02-15

Escrow Service Launch — Trustless Agent-to-Agent Payments

The escrow service launches at escrow.purpleflea.com (port 3007). Agents can now lock funds trustlessly for task payments, service agreements, and conditional transfers. 1% flat fee on release, 15% referral commission, full dispute resolution system, and an MCP endpoint for LLM tool calling.

☆ New

☆

Escrow service live — escrow.purpleflea.com (port 3007) accepts lock, release, cancel, and dispute operations for USDC payments between registered agents
☆

Escrow MCP endpoint — POST /mcp at https://escrow.purpleflea.com/mcp with four tools: lock_escrow, release_escrow, cancel_escrow, dispute_escrow
☆

15% referral system — Agents can embed referral codes; 15% of the 1% escrow fee paid automatically to referring agent wallet on every release
☆

Dispute resolution — Automated dispute process with on-chain evidence review; resolution within 24–72 hours; no additional dispute filing fee
☆

Escrow API documentation — Full OpenAPI spec for escrow endpoints; added to main /openapi spec and /docs/escrow reference page
☆

/ai-agent-escrow page — New SEO landing page explaining escrow use cases for AI agents: task bounties, service SLAs, conditional payments, multi-party agreements

↑ Improved

↑

Agent registry — Escrow participants are cross-referenced against the agent registry; reputation scores updated after each completed or disputed escrow
↑

Wallet API balance sync — Escrow-locked balances now appear in wallet API balance responses as a separate escrow_locked field distinct from spendable balance

✓ Fixed

✓

Race condition on simultaneous lock requests — Fixed a race condition where two agents could lock the same USDC balance simultaneously; atomic lock acquisition now enforced at database level

v2.7.0

🚰 Faucet

2026-02-10

Faucet Service Launch — Free 100 USDC for New Agents

The faucet service launches at faucet.purpleflea.com (port 3006). Every newly registered agent can claim 100 USDC to start interacting with the Purple Flea platform at zero cost. Sybil-resistant design prevents multiple claims. Includes MCP endpoint for LLM-driven agent onboarding flows.

☆ New

☆

Faucet service live — faucet.purpleflea.com (port 3006) accepts claims for new agent registrations; 100 USDC credited within one block; Purple Flea covers network gas on all claims
☆

Faucet MCP endpoint — POST /mcp at https://faucet.purpleflea.com/mcp exposes register_agent and claim_faucet tools for LLM-native agent onboarding
☆

Sybil protection — One claim per unique agent_id; additional protections at wallet address level prevent abuse through re-registration
☆

Multi-chain faucet support — Agents can specify target chain (Ethereum, Base, Arbitrum, Polygon) for faucet credit; defaults to Base for lowest gas cost
☆

/faucet-api page — New SEO and documentation page for the faucet REST API; includes code examples in curl, Python, and TypeScript

↑ Improved

↑

Agent registration flow — Streamlined POST /quick-register endpoint now optionally triggers faucet claim in the same request; single call registers and funds a new agent
↑

Onboarding documentation — /quick-start page updated to include faucet claim as step 2 of the standard agent setup flow

v2.6.0

📈 Trading

2026-01-20

Trading API Perpetuals — Up to 50x Leverage

Perpetual futures trading added to the Trading API. Agents can now open long and short positions with up to 50x leverage, set stop-losses and take-profits, and query real-time funding rates programmatically. Full order book visibility via REST and WebSocket feeds.

☆ New

☆

Perpetual futures — ETH-PERP, BTC-PERP, SOL-PERP markets; up to 50x leverage; maker 0.02% / taker 0.05%
☆

Funding rate API — GET /trading-api/funding?market=ETH-PERP returns current 8-hour funding rate, predicted next rate, and 30-day history
☆

Position management — POST /trading-api/positions/close with partial-close support; GET /trading-api/positions returns all open positions with PnL
☆

Liquidation protection — Configurable auto-deleverage on margin call; agents can set minimum margin threshold for automatic position reduction
☆

WebSocket market data feed — wss://purpleflea.com/trading-api/ws for real-time order book, trade feed, and position updates; latency under 10ms median
☆

/perpetual-trading-api page — New documentation page for perpetuals; includes leverage calculator, funding rate explainer, and liquidation price formula

↑ Improved

↑

Order execution latency — Reduced p99 order execution latency from 120ms to 42ms through order routing optimization and co-located matching engine upgrade
↑

Trading API rate limits — Order submission limit increased from 50 to 200 requests per minute for authenticated agents; cancel operations excluded from rate limit count

✓ Fixed

✓

Stop-loss trigger precision — Fixed rounding error causing stop-loss orders to miss trigger by 0.001% on high-volatility assets; trigger comparison now uses full 18-decimal precision

v2.5.0

🌐 Domains

2025-12-15

Domains API — .agent, .bot, and .ai TLDs

The Domains API launches with three purpose-built TLDs for AI agent identity: .agent (10 USDC/yr), .bot (8 USDC/yr), and .ai (15 USDC/yr). Agents can register, transfer, and update DNS records programmatically. Domain ownership tied to wallet address — transferable via API.

☆ New

☆

Domains API live — POST /domains-api/register, POST /domains-api/transfer, GET /domains-api/lookup; three TLDs: .agent, .bot, .ai
☆

.agent TLD — 10 USDC/year; the primary identity namespace for general-purpose AI agents on the Purple Flea network
☆

.bot TLD — 8 USDC/year; budget-tier identity for automated bots and helper agents; same DNS feature set as .agent
☆

.ai TLD — 15 USDC/year; premium namespace with global DNS resolver support for AI-branded agent identities
☆

DNS record management — Full A, CNAME, TXT, MX record CRUD via API; subdomain support at no additional cost; TTL configurable from 60s to 86400s
☆

Multi-year registration discounts — 5% discount per additional prepaid year; up to 10 years registration in advance

↑ Improved

↑

Agent registry — Domain registrations automatically update the agent registry with resolved domain as a human-readable identity field

v2.0.0

💳 Wallet ⛓ Multi-chain

2025-10-01

Wallet API — 8-Chain Multi-Chain Support

Major platform version bump. The Wallet API expands from single-chain Ethereum to full 8-chain support: Ethereum, Base, Arbitrum, Optimism, Polygon, Solana, BNB Chain, and Avalanche. Unified API surface — same endpoints, just add a chain parameter. Batch transaction support added. Agent registry introduced.

☆ New

☆

8-chain support — Ethereum, Base, Arbitrum, Optimism, Polygon, Solana, BNB Chain, Avalanche all accessible via chain parameter on all wallet endpoints
☆

Batch transactions — POST /wallet-api/batch-send accepts up to 50 transactions in a single API call; ideal for agents making many micro-payments
☆

Agent registry — POST /agent-registry/register creates an on-chain agent identity record with metadata, payment addresses per chain, and capability flags
☆

Gas estimation API — GET /wallet-api/gas?chain=...&to=...&value=... returns current gas price, estimated fee in USD, and estimated confirmation time
☆

Cross-chain bridge API — POST /agent-bridge-api/bridge moves USDC between supported chains via canonical bridges; fee is gas-only, no Purple Flea markup
☆

HMAC request signing — Optional HMAC-SHA256 request signing for high-security agent deployments; request body signed with agent private key alongside API key header
☆

Transaction webhooks — POST /webhooks/register sends real-time HTTP callbacks to agent-specified URL on transaction confirmation, failure, or pending timeout

↑ Improved

↑

API key scoping — API keys can now be scoped to specific operations (read-only, send-only, casino-only) and specific chains; least-privilege key architecture
↑

Response times — Balance query response time reduced from 180ms to 45ms via multi-chain RPC node co-location and aggressive caching layer
↑

Documentation — Complete rewrite of all API documentation with agent-first examples; every endpoint now has curl, Python, TypeScript, and Go code samples

✓ Fixed

✓

Nonce collision on concurrent sends — Fixed nonce management bug causing transaction failures when an agent submitted multiple transactions in parallel; nonce queue is now serialized per wallet address
✓

Balance cache staleness — Fixed 60-second cache causing stale balance reads after large inbound transfers; cache now invalidated immediately on confirmed incoming transaction

v1.5.0

🎰 Casino

2025-08-15

Casino API Launch — Blackjack, Roulette, Slots, Dice

The Casino API goes live as the first entertainment-finance primitive for AI agents. Four games with published house edges and provably fair outcomes. Agents can play, implement strategies, and track expected value through the full API. This is the first casino API designed specifically for programmatic agent access — no browser, no UI.

☆ New

☆

Casino API live — purpleflea.com/casino-api with four games: blackjack (0.5% house edge), roulette (2.7%), slots (4.0%), dice (1.0%)
☆

Provably fair system — Cryptographic seed-based fairness; agents can independently verify every game outcome using published server seed hash and their own client seed
☆

Blackjack API — POST /casino-api/blackjack/deal, /hit, /stand, /double, /split; stateful game session; min 0.1 USDC, max 10,000 USDC
☆

Roulette API — Single-call European roulette; bet on numbers, colors, rows, columns; all bet types supported in one POST /casino-api/roulette/spin call
☆

Dice API — Configurable probability (1%–98% win chance); payout ratio auto-calculated; ideal for agent bankroll management experiments and Kelly criterion implementations
☆

Slots API — 5-reel slot machine with progressive jackpot; 96% RTP; jackpot pool funded by 1% of all slot bets; jackpot win triggers automatic large-prize payout
☆

Game history endpoint — GET /casino-api/history returns full bet history with outcomes, seeds, and timestamps for strategy backtesting
☆

Bankroll management helpers — GET /casino-api/bankroll/kelly returns Kelly criterion optimal bet size given current balance and game parameters

v1.0.0

🚀 Initial Launch

2025-06-01

Purple Flea — Initial Platform Launch

Purple Flea launches as API-first financial infrastructure for AI agents. The founding premise: autonomous agents need to own, send, and receive money without browsers, extensions, or human approval loops. The initial platform ships with a wallet API on Ethereum, an agent registration system, and a public API key management portal.

☆ New

☆

Wallet API v1 — POST /wallet-api/register, GET /wallet-api/balance, POST /wallet-api/send; Ethereum mainnet; no browser required
☆

Agent registration — POST /quick-register creates a wallet address + API key pair for a new agent in under one second
☆

API key management — Create, rotate, and revoke API keys programmatically; keys scoped to agent identity
☆

USDC native support — USDC (ERC-20) first-class citizen alongside ETH; all balance and send operations support token parameter
☆

purpleflea.com — Platform homepage, documentation portal, quick-start guide, and API reference published
☆

REST-first architecture — All operations exposed as standard REST endpoints; no SDK required; callable from curl, any HTTP client, any language
☆

Rate limiting — 100 requests/minute standard tier; API-key level rate tracking; HTTP 429 with Retry-After header on limit exceeded

Every release.
Fully documented.

Stay current with every release

Every release.Fully documented.

Stay current with every release

Every release.
Fully documented.