World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
Smart Meta-Facilitator for x402 payments on Base: route, verify, and settle payments.
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 Nexflow Smf 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
SettingsDeveloperEdit Config
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Nexflow Smf 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Nexflow Smf,或回答中出现 Nexflow Smf 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Nexflow Smf
Nexflow Smf 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Nexflow Smf 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Nexflow Smf 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user nexflow-smf --env NEXFLOW_API_KEY=your-value --env NEXFLOW_BASE_URL=your-value -- npx -y @nexflow-smf/smf按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Nexflow Smf 在列表中并显示已连接
用 Nexflow Smf 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Nexflow Smf,或回答中出现 Nexflow Smf 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Nexflow Smf 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Nexflow Smf 的设置中,NEXFLOW_API_KEY, NEXFLOW_BASE_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Nexflow Smf 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Nexflow Smf,或回答中出现 Nexflow Smf 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Nexflow Smf 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Nexflow Smf 的设置中,NEXFLOW_API_KEY, NEXFLOW_BASE_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Nexflow Smf 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Nexflow Smf,或回答中出现 Nexflow Smf 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user nexflow-smf --env NEXFLOW_API_KEY=your-value --env NEXFLOW_BASE_URL=your-value -- npx -y @nexflow-smf/smfClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"nexflow-smf": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}NEXFLOW_API_KEY 机密 必填 envNEXFLOW_BASE_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月12日
注册名称已通过 GitHub 账户 NexFlow-SMF 验证,该账户拥有此仓库
代码最后更新于8个月前,已超过 6 个月
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:NEXFLOW_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于8个月前,最新版本(1.0.0)于10个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:World Monitor, Claude Flow, Windmill
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The x402-native metered billing and routing brain for AI agents and SaaS APIs on Base.
NexFlow SMF routes, verifies, and settles x402 micropayments on Base. It acts as an intelligent intermediary between payers and facilitators, selecting the optimal route based on cost, latency, and reliability. This repository contains the on-chain settlement contracts, TypeScript SDK, agent manifest specification, and integration examples.
Discover AI agent services with x402 payment routing through NexFlow SMF. Submit your service to the catalog.
| Component | Description |
|---|---|
contracts/ | Solidity contracts for atomic batch settlement with Merkle proof verification |
sdk/ | Zero-dependency TypeScript SDK (@nexflow-smf/smf) for routing, verification, and settlement |
examples/ | Ready-to-run examples demonstrating common integration patterns |
examples/workflows/ | JSON workflow definitions for the NexFlow SMF workflow host |
examples/client/ | Minimal TypeScript clients showing the 402 → pay → retry pattern |
Canonical list of NexFlow SMF skills. Each skill has a SKILL.md (for Cursor/agents) and lives in nexflow-smf-skills/. Machine-readable manifest: skills-manifest.json · API: GET https://api.nexflowapp.app/.well-known/skills (redirects to manifest).
| Skill | Description |
|---|---|
| List Facilitators | Discover active x402 facilitators by network/asset before quoting or paying. |
| Route Matrix | Compare priced routes (fees, latency) across facilitators for USDC on Base. |
| Route Quote | Get a single priced quote for a chosen facilitator before committing. |
| Settlement Receipt | Fetch a settlement receipt for a completed x402 payment for logs or audits. |
| Healthcheck | Ping NexFlow SMF for status and latency before routing payments. |
| Simulate Charge | See x402 pricing headers without performing a real payment. |
| Budget Plan | Turn a USDC budget into an approximate number of SMF API calls. |
Discover NexFlow services as AgentCards, ready for AI agents and x402-aware clients:
https://nexflow-agentcards.pages.dev/
Drop a Lambda@Edge function in front of CloudFront. Every request to a protected path must include a valid x402-payment header — otherwise the client gets a 402 Payment Required with payment instructions. No backend changes needed.
How it works:
/x402/verify with the payment proof (not billed). If valid, attaches a settlementIntentId and forwards to origin. If invalid, returns 402.settlementIntentId. If origin status < 400, calls /x402/settle to confirm delivery (this is the billable event). Returns the response unchanged.Get started in 15 minutes:
[AWS CloudFront + Lambda@Edge Quickstart →](./examples/aws-cloudfront-lambdaedge/README.md)
For server-side integrations where you control the request lifecycle — route payments, verify intents, and trigger batch settlement from your own code.
npm install @nexflow-smf/smf
import { NexFlowSMFClient } from '@nexflow-smf/smf';
const smf = new NexFlowSMFClient({ baseUrl: 'https://api.nexflowapp.app', apiKey: process.env.NEXFLOW_API_KEY!, });
// Route a payment const route = await smf.route({ amount_wei: '1000000', token_address: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', chain_id: 'eip155:8453', payment_id: 'order-123', });
// Verify a payment intent const result = await smf.verify({ payment_intent: 'x402:1:base:0xabc...', recipient_address: '0xYourAddress...', });
[Full SDK documentation →](./sdk/README.md)
| Path | Description |
|---|---|
examples/aws-cloudfront-lambdaedge/ | 15-minute AWS quickstart — Lambda@Edge x402 pay-per-request gating |
examples/basic-settlement.ts | End-to-end SDK example: route, verify, settle |
sdk/ | Zero-dependency TypeScript SDK (@nexflow-smf/smf) |
contracts/ | Solidity contracts for atomic batch settlement with Merkle proofs |
docs/ | API reference, facilitator contract, production checklist |
AGENT_MANIFEST_V1.md | Agent Manifest spec for machine-to-machine discovery |
nexflow-smf-skills/ | Cursor-style agent skills (route-matrix, quote, receipt, facilitators, health, simulate, budget) |
PRICING.md | Pricing model with example scenarios |
| Service | Description | Status |
|---|---|---|
| Smart Meta-Facilitator | Intelligent payment routing, verification, and batch settlement | Live |
| CloudFront Edge Gating | Lambda@Edge adapter for pay-per-request access via CloudFront | Live |
| Agent Manifest & Discovery | Machine-readable capability manifest for AI agent integration | Live |
| Pulse Scheduler | Metered job scheduling with x402 billing (cron, webhooks, tasks) | Live |
| Action Catalog | Pre-built metered actions (Shopify, Salesforce, data enrichment) | Live |
| Contract | Address | Explorer |
|---|---|---|
| AtomicBatchSettlement | 0x43A04228152115fDd5663B2Aa559Ebd84D17A49D | BaseScan |
| USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 | BaseScan |
NexFlow SMF allows agents to define, publish, and monetize hosted workflows — multi-step compositions of core SMF operations that other agents can invoke via the 402/MPP payment gateway.
Workflows can compose any of these paid SMF operations:
| Operation | Description |
|---|---|
create_session | Create a metered session with a budget |
budget_check | Check planned charges against budgets |
budget_diagnostics | Analyze sessions for overrun risk |
process_charges | Deduct charges from a session or caller |
verify_payment | Validate a payment descriptor |
settle_batch | Settle a batch of transactions |
revenue_share | Record revenue-share accounting for a period |
route_quote | Get a payment routing quote |
usage_timeseries | Time-series spend data for a caller/session |
configure_alerts | Set budget/usage alert thresholds |
monitor_sessions | List sessions with budget & spend status |
monitor_alerts | Return triggered budget/usage alerts |
pricing_estimate | Estimate cost of a set of operations |
examples/workflows/safety_capped_session_runner.json
A 5-step workflow that:
examples/workflows/usage_health_check.json
A 3-step diagnostic workflow that:
examples/workflows/revenue_share_settlement.json
A 5-step workflow demonstrating the full payment lifecycle:
The workflow creator earns their standard rev-share (set via creatorShareBps) on every invocation. Rev-share credits accumulate per wallet and are batched for payout when they reach $5+.
Input example:
{
"sessionBudget": { "amount": 2000000, "currency": "USDC" }, "charges": [ { "callerId": "agent_a", "amount": 500000, "description": "API usage week 12" }, { "callerId": "agent_b", "amount": 300000, "description": "Compute usage week 12" } ], "settlementPeriod": "2026-03-01/2026-03-31" }
# Register the Safety-Capped Session Runner
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ --data-binary "@examples/workflows/safety_capped_session_runner.json"
Response:
{
"workflowId": "wf_abc123_1", "name": "Safety-Capped Session Runner", "invokeUrl": "/nexflow/workflows/wf_abc123_1/invoke", "status": "active", "steps": 5, "pricing": { "billingMode": "per_call", "markupBps": 300 } }
# First call — no payment proof → 402 Payment Required
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows/wf_abc123_1/invoke" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ --data '{ "requestedBudget": { "amount": 500000, "currency": "USDC" }, "plannedCost": { "amount": 50000, "currency": "USDC" } }'
The first call returns HTTP 402 with a payment challenge:
{
"object": "payment_challenge", "operation": "workflow_invoke", "workflow_id": "wf_abc123_1", "required_amount": 17350, "currency": "usdc", "price_breakdown": { "totalPrice": 17350, "baseCost": 7000, "markup": 210, "platformFee": 149 }, "instructions": "Pay via MPP using the challenge above, then retry with X-PAYMENT-PROOF header." }
After the agent pays (via Tempo MPP or x402), it retries with the proof:
# Second call — with valid proof → 200 OK
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows/wf_abc123_1/invoke" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ -H "X-PAYMENT-PROOF: " \ --data '{ "requestedBudget": { "amount": 500000, "currency": "USDC" }, "plannedCost": { "amount": 50000, "currency": "USDC" } }'
See examples/client/invokeUsageHealthCheck.ts for a runnable demo of the full 402 → proof → retry flow.
export NEXFLOW_SMF_BASE_URL=http://localhost:3001
export WORKFLOW_ID=wf_abc123_1 npx tsx examples/client/invokeUsageHealthCheck.ts
| Variable | Required | Description |
|---|---|---|
NEXFLOW_API_KEY | Yes | Your NexFlow API key (nf_live_xxx or nf_test_xxx) |
NEXFLOW_BASE_URL | No | Override API URL (default: https://api.nexflowapp.app) |
NEXFLOW_SMF_BASE_URL | No | NexFlow SMF bridge URL for workflow invocations (default: http://localhost:3001) |
WORKFLOW_ID | No | Workflow ID for the client example scripts |
Sign up or log in at [nexflowapp.app](https://n