satring-mcp
Discover and compare L402 and x402 paid API services from satring.com. Search, filter, and rank services by price, rating, or composite score across the best curated Lightning and USDC API directory.
README
___ __ _| |_ _ __(_)_ __ __ _
/ __|/ _` | __| '__| | '_ \ / _` |
\__ \ (_| | |_| | | | | | | (_| |
|___/\__,_|\__|_| |_|_| |_|\__, |
|___/ ⚡ L402 + x402
<img src="app/static/img/satring-logo-trans-bg.png" alt="satring" width="20"> satring.com — the best curated L402 + x402 API directory. Find, rate, and connect to paid APIs via Lightning (L402) or USDC on Base (x402).
Satring helps AI agents and developers discover paid API services that accept payments via the L402 protocol (Bitcoin Lightning) or the x402 protocol (USDC on Base). Browse the curated directory, submit your service, and let agents find you.
Why
AI agents can now pay for APIs autonomously using Lightning. But there's no good way to discover what's available. Satring is the best curated directory for L402 and x402 paid APIs.
Features
- Browse, search, and filter paid APIs by category, status, and protocol
- Dual-protocol payments: L402 (Bitcoin Lightning) and x402 (USDC on Base) supported side by side
- Submit services with payment gate (anti-spam), payable via either protocol
- Ratings and reputation system (also payment-gated)
- Edit your listing with secure edit tokens
- Recover lost edit tokens via domain verification (
.well-known/satring-verify) - Shared edit tokens across same-domain services; one token manages all your listings
- JSON API for programmatic access and agent queries
- Premium endpoints (bulk export, analytics, reputation) gated via L402 or x402
- Per-service health analytics: uptime percentage, average latency, probe history
- Health probing with automatic protocol detection (L402, x402, or both)
- Service status tracking (live / confirmed / dead)
Quick Start
git clone https://github.com/toadlyBroodle/satring.git
cd satring
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env # configure wallet keys, or leave defaults for test mode
uvicorn app.main:app --reload
Open http://localhost:8000
In test mode (AUTH_ROOT_KEY=test-mode), all payment gates are bypassed.
API
Full interactive docs at satring.com/docs.
Free endpoints
# List services (paginated, filterable by category, status, and protocol)
curl "https://satring.com/api/v1/services?category=search&status=live&protocol=L402&page=1&page_size=20"
# Search (also filterable by status and protocol)
curl "https://satring.com/api/v1/search?q=satring&protocol=X402"
# Service details
curl https://satring.com/api/v1/services/my-service
# List ratings
curl https://satring.com/api/v1/services/my-service/ratings
Payment-gated endpoints
These require payment via L402 or x402. Without auth headers, the server returns 402 with challenges for both protocols.
Option A: L402 (Lightning)
# Submit a service via L402
curl -X POST https://satring.com/api/v1/services \
-H "Authorization: L402 <macaroon>:<preimage>" \
-H "Content-Type: application/json" \
-d '{
"name": "My API",
"url": "https://api.example.com",
"pricing_sats": 10,
"pricing_model": "per-request",
"protocol": "L402",
"category_ids": [1, 2]
}'
Option B: x402 (USDC on Base)
# Submit a service via x402
curl -X POST https://satring.com/api/v1/services \
-H "PAYMENT-SIGNATURE: <base64-encoded-payment-json>" \
-H "Content-Type: application/json" \
-d '{
"name": "My API",
"url": "https://api.example.com",
"pricing_usd": "0.50",
"pricing_model": "per-request",
"protocol": "x402",
"x402_network": "eip155:8453",
"x402_asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"x402_pay_to": "0xYourWalletAddress",
"category_ids": [1, 2]
}'
Other gated operations
# Link to existing service on same domain (L402 or x402 auth)
curl -X POST https://satring.com/api/v1/services \
-H "Authorization: L402 <macaroon>:<preimage>" \
-H "Content-Type: application/json" \
-d '{
"name": "My Other API",
"url": "https://api.example.com/v2",
"existing_edit_token": "your-token-from-first-service"
}'
# Edit a service
curl -X PATCH https://satring.com/api/v1/services/my-api \
-H "X-Edit-Token: your-edit-token" \
-H "Content-Type: application/json" \
-d '{"description": "Updated description"}'
# Bulk export (use -i to see payment challenges in headers)
curl -i https://satring.com/api/v1/services/bulk
# Directory analytics (totals, health overview, pricing stats by protocol, growth, leaderboards, route usage)
curl -i https://satring.com/api/v1/analytics
# Per-service health analytics (uptime %, avg latency, probe history)
curl -i https://satring.com/api/v1/services/my-service/analytics
# Service reputation (rating distribution, monthly trends, peer comparison, review activity)
curl -i https://satring.com/api/v1/services/my-service/reputation
Token recovery
If you lose your edit token, or want to edit a pre-seeded endpoint, prove domain ownership to get a new one:
# 1. Generate a challenge
curl -X POST https://satring.com/api/v1/services/my-service/recover/generate
# 2. Place the challenge code at your-domain.com/.well-known/satring-verify
# 3. Verify — new token is applied to ALL services on the same domain
curl -X POST https://satring.com/api/v1/services/my-service/recover/verify
Configuration
Environment variables (see .env):
| Variable | Default | Description |
|---|---|---|
DATABASE_URL |
sqlite+aiosqlite:///./db/sr.db |
Database connection string |
PAYMENT_URL |
— | Wallet instance URL |
PAYMENT_KEY |
— | Wallet invoice/read key |
AUTH_ROOT_KEY |
test-mode |
Set to wallet key for production; test-mode bypasses payments |
AUTH_SUBMIT_PRICE_SATS |
1000 |
Cost to submit a service |
AUTH_REVIEW_PRICE_SATS |
10 |
Cost to submit a review |
AUTH_BULK_PRICE_SATS |
5000 |
Cost for bulk export |
AUTH_ANALYTICS_PRICE_SATS |
500 |
Cost for directory analytics |
AUTH_SERVICE_ANALYTICS_PRICE_SATS |
50 |
Cost for per-service health analytics |
AUTH_REPUTATION_PRICE_SATS |
100 |
Cost for reputation lookup |
AUTH_PRICE_SATS |
100 |
Default price for premium endpoints |
X402_FACILITATOR_URL |
https://facilitator.xpay.sh |
x402 facilitator endpoint |
X402_PAY_TO |
— | USDC wallet address (empty = x402 disabled) |
X402_NETWORK |
eip155:8453 |
Chain ID (default: Base mainnet) |
X402_ASSET |
0x8335...2913 |
USDC contract address on Base |
AUTH_SUBMIT_PRICE_USD |
0.50 |
x402 cost to submit a service |
AUTH_REVIEW_PRICE_USD |
0.01 |
x402 cost to submit a review |
AUTH_BULK_PRICE_USD |
2.50 |
x402 cost for bulk export |
AUTH_ANALYTICS_PRICE_USD |
0.25 |
x402 cost for directory analytics |
AUTH_SERVICE_ANALYTICS_PRICE_USD |
0.025 |
x402 cost for per-service health analytics |
AUTH_REPUTATION_PRICE_USD |
0.05 |
x402 cost for reputation lookup |
MCP Server
The satring-mcp package lets AI agents discover and compare services from the directory programmatically via the Model Context Protocol.
pipx install satring-mcp
# or
pip install satring-mcp
Then add to your Claude Desktop claude_desktop_config.json or Claude Code .claude/settings.json:
{
"mcpServers": {
"satring": {
"command": "satring-mcp"
}
}
}
Tools: discover_services, list_services, get_service, get_ratings, list_categories, compare_services, find_best_service. See mcp/README.md for full docs.
Tech Stack
- FastAPI + Jinja2 + HTMX: server-rendered with progressive enhancement
- SQLAlchemy (async) + SQLite: simple, no external DB needed
- L402 / Macaroons: Lightning-native authentication via pymacaroons
- x402 / USDC on Base: stablecoin payments via xpay.sh facilitator
- Tailwind CSS (browser CDN): terminal-themed green-on-black UI
Contributing
All contributions welcome!
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。