Cinderwright Api

io.github.cinderwright-aiPublished by GitHub account cinderwright-aiv1.1.1Updated Nov 3, 2026

Cross-protocol agent payments hub. x402, MPP, L402/Lightning. 1551 services indexed.

VerifiedSTDIODesktop onlyWeb Search & ScrapingFinanceAI & ML

Overview

AI-generated overview

Local MCP server that routes an assistant's paid API tasks through a cross-protocol payment hub for x402 (USDC) and L402 (Lightning) services.

What you can do
  • Send a plain-English task to a proxy endpoint that searches indexed services, picks a match, detects the payment protocol and returns the data
  • Set up a proxy account, check the USDC balance and manage per-call budget caps and a kill switch
  • Discover indexed services and inspect on-chain settlement data for a given endpoint
  • Test services and Lightning node status, and submit new services to the index
When to use it
Useful when an assistant needs to call paid, payment-gated APIs (x402 or Lightning L402) without managing wallets or signing transactions itself, and you are willing to fund a prepaid USDC balance with the provider.
Requirements
Runs locally via npx (Node.js). Needs a proxy account created through the provider's setup flow, a funded USDC balance on Base, and an API key supplied in the CW_KEY environment variable. Network access to the provider's API is required.
Before you install
Calls spend real money from a prepaid USDC balance, so set per-call caps and a kill switch. The API key in CW_KEY is a billing credential. Setup involves a Base wallet address, and the provider signs payments and settles on your behalf, so tasks and payment details go to a third party.

Installation

In SourceWeft

  1. Open Cinderwright Api in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

What shipped this week

June 9, 2026: Both bridge directions confirmed on mainnet.

  • Lightning --> USDC proxy: pay a Lightning invoice, get agent credit within 30 seconds
  • USDC --> Lightning: agent with USDC pays L402 services automatically
  • Free demo: api.ideafactorylab.org -- no account needed
  • CLI: npx cinderwright "Bitcoin price"
  • 2,835 services indexed. $0.10 free credit on new accounts.

Cinderwright — Universal Payment Router for AI Agents

x402 + L402 (Lightning) interoperable. First confirmed cross-protocol agent payment June 2026.

An AI agent with a USDC balance can now call any Lightning-gated (L402) service. We detect the protocol, route the payment, and return the data. The agent never knows which protocol settled.

bash
# One endpoint. Any protocol. 2,811 services.curl -X POST https://api.ideafactorylab.org/proxy/do \  -H "X-CW-Key: sk_cw_your_key" \  -d '{"task": "get weather in Tokyo"}'

What's Live

ProtocolServicesStatus
x402 (USDC on Base)1,503Live
L402 (Bitcoin Lightning)1,185Live
MPP (Stripe/Tempo)92Coming soon

Lightning status: https://api.ideafactorylab.org/lightning-status

How It Works

  1. Agent deposits USDC to their proxy account
  2. Agent sends a plain-English task to /proxy/do
  3. Cinderwright searches 2,811 services, finds the best match
  4. Detects the payment protocol from the 402 response headers
  5. Routes payment accordingly: USDC for x402, Lightning invoice for L402
  6. Returns the data, charges USDC equivalent from agent's balance

The agent never manages wallets, signs transactions, or knows which protocol ran.

Quick Start

bash
# Get a proxy accountcurl -X POST https://api.ideafactorylab.org/proxy/setup \  -d '{"wallet": "0xYourBaseWallet"}'
# Deposit USDC on Base to the returned address
# Call any servicecurl -X POST https://api.ideafactorylab.org/proxy/do \  -H "X-CW-Key: sk_cw_your_key" \  -d '{"task": "Bitcoin price now", "max_cost_usd": 0.10}'

MCP Server for Claude Desktop

bash
npx cinderwright-mcp-server

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "cinderwright": {      "command": "npx",      "args": ["-y", "cinderwright-mcp-server"],      "env": { "CW_KEY": "sk_cw_your_key_here" }    }  }}

17 tools including proxy_do, proxy_setup, proxy_balance, and service discovery.

Free Developer Tools

ToolWhat it does
/testLive service tester
/debug16-check diagnostic engine with host pollution + scheme detection
/sandboxTest EIP-3009 signing without spending USDC
/budgetPer-call caps and kill switch
/setupWallet setup wizard
/lightning-statusLightning node status and outbound capacity
/onchainOn-chain settlement data via TomSmart mapper.db

Discovery

bash
# Free searchcurl "https://api.ideafactorylab.org/discover?q=weather"curl "https://api.ideafactorylab.org/discover?q=bitcoin+price&protocol=l402"
# On-chain settlement data for any servicecurl "https://api.ideafactorylab.org/onchain?endpoint=https://your-service.com/api"
# Submit your servicecurl -X POST https://api.ideafactorylab.org/submit \  -d '{"url": "https://your-service.com"}'

Architecture

The universal payment router sits between agents and services:

Agent (USDC balance)    |    vPOST /proxy/do {"task": "..."}    |    vCinderwright Router    |-- detect protocol from 402 response headers    |-- x402: sign USDC payment via EIP-3009    |-- L402: pay Lightning invoice via LND REST    |-- MPP: (coming soon)    |    vService returns data    |    vAgent receives data + charged USDC equivalent

Links

Source: README.md at commit 2424342

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts