Cinderwright is a universal payment routing and discovery hub for the AI agent economy, with its core positioning being "the search engine of the agent economy." It connects agents with various paid services through an MCP server and the x402 Discovery Hub, and solves the interoperability problem between different payment protocols.
Main capabilities:
- Service discovery: indexes more than 1,450 (the latest figure is 2,835) agent services, and supports searching for the best match using natural language tasks.
- Cross-protocol payment routing: supports both x402 (USDC on Base) and L402 (Lightning) protocols. An agent only needs to hold a USDC balance to call any Lightning-gated (L402) service. The system automatically detects the protocol, routes the payment, and returns the data, without the agent needing to be aware of the underlying settlement protocol.
- Payment flow: the agent deposits USDC into a proxy account → sends a plain English task to /proxy/do → Cinderwright searches for and matches a service → detects the payment protocol from the 402 response header → routes payment according to the protocol (USDC for x402, Lightning invoice for L402) → returns the data and deducts the equivalent amount of USDC from the balance.
- Bidirectional bridge: mainnet bidirectional bridging was confirmed on June 9, 2026. Lightning → USDC proxy: after paying a Lightning invoice, agent credit is received within 30 seconds; USDC → Lightning: agents holding USDC automatically pay for L402 services.
- MCP server: provides 17 tools for Claude Desktop, including proxy_do, proxy_setup, proxy_balance, and service discovery, among others.
How to use:
- Free demo: visit api.ideafactorylab.org, no account required.
- CLI: run npx cinderwright "Bitcoin price".
- MCP server: the npm package is npx cinderwright-mcp-server, and it needs to be added to claude_desktop_config.json.
- New accounts receive $0.10 in free credit.
Use cases:
- AI agents need to call paid APIs or services, but do not want to manage multiplecryptocurrency wallets.
- Agent applications that need automatic payments across the x402 and L402 protocols.
- Developers who want to quickly search for and integrate various services in the agent economy.
Limitations:
- The materials do not provide the specific charging model, pricing details, a complete list of supported services, the scope of platform compatibility, performance metrics, or usage restrictions.
- Some data (such as the number of indexed services) differs across locations (1,450+ and 2,835); the official latest figure should prevail.
- The cross-protocol payment feature depends on mainnet operating status, and specific availability should be checked against the official status page.
