Gives DeerFlow agents the one thing the harness can't do on its own: decide who is safe to pay and how to settle.
AsterPay is the trust, discovery, and EUR-settlement layer for AI agent commerce:
- TRUST (KYA) — score any wallet 0-100 before paying it (sanctions, ERC-8004 identity).
- DISCOVERY (MPE) — resolve a European business to its verified IBAN/BIC.
- SETTLEMENT — estimate a USDC/EURC -> EUR cashout (rate, fee, SEPA Instant).
All core lookups are free, read-only, and need no wallet or API key.
AsterPay hosts a public, read-only remote MCP server. DeerFlow loads MCP servers from a dedicated extensions_config.json in the project root (copied from extensions_config.example.json). Add the asterpay entry and the four tools (check_agent_trust, merchant_resolve, settlement_estimate, market_rates) become available to every agent — no auth, no install.
{
"mcpServers": {
"asterpay": {
"enabled": true,
"type": "http",
"url": "https://mcp-api.asterpay.io/mcp",
"description": "AsterPay — KYA trust score, merchant payout resolution, USDC->EUR settlement estimate (read-only)"
}
}
}Then restart DeerFlow to register the tools. A ready-to-merge file is included at extensions_config.asterpay.json.
Schema (verified against DeerFlow
backend/docs/MCP_SERVER.mdandtest_mcp_client_config.py):typeis one ofstdio/sse/http(transportis accepted as an alias);http/sseservers requireurl. AsterPay's remote endpoint is a stateful Streamable HTTP MCP server and needs nooauthblock — it is public and read-only.
The skill teaches the agent when to reach for AsterPay (the pre-payment trust gate, merchant discovery, settlement quoting) and ships a zero-secret fallback script for sandboxes without the MCP server.
npx skills add https://github.com/AsterPay/deerflow-skill --skill asterpayOr copy it into a DeerFlow custom-skills directory manually:
cp -r asterpay /mnt/skills/custom/asterpay
# or point DEER_FLOW_SKILLS_PATH at a directory that contains itThen activate it for a single turn with a slash command:
/asterpay is wallet 0x742d35Cc6634C0532925a3b844Bc454e4438f44e safe to pay 500 USDC?
DeerFlow loads asterpay/SKILL.md as hidden current-turn context while keeping the base prompt limited to the skill metadata (progressive loading).
If the MCP server isn't configured, the agent runs the bundled helper in the sandbox (Node 18+, no dependencies, no wallet, no secrets):
node asterpay/scripts/asterpay.mjs trust 0x742d35Cc6634C0532925a3b844Bc454e4438f44e
node asterpay/scripts/asterpay.mjs estimate 100 USDC
node asterpay/scripts/asterpay.mjs resolve --business-id-type demo
node asterpay/scripts/asterpay.mjs ratesEach command prints a one-line decision summary followed by the full JSON. trust exits non-zero on upstream failure and surfaces a REFUSE/WARN/OK decision so the agent can gate transactions on it.
| Env var | Default | Purpose |
|---|---|---|
ASTERPAY_API_URL |
https://x402.asterpay.io |
API host override |
The skill's tools never move money. Actual settlement uses the x402 protocol (HTTP 402 -> signed EIP-3009 USDC transfer -> facilitator settles -> EUR via SEPA Instant) and requires a funded wallet supplied out-of-band by the operator. The skill ships no key handling by design and instructs the agent to require explicit user confirmation. See https://asterpay.io/docs for the paid path.
deerflow-skill/
├── README.md
├── extensions_config.asterpay.json # ready-to-merge MCP server entry (Option A)
└── asterpay/
├── SKILL.md # the skill (progressive-load triggers + workflow)
└── scripts/
└── asterpay.mjs # zero-secret free-lookup fallback
- AsterPay: https://asterpay.io
- API: https://x402.asterpay.io
- Remote MCP: https://mcp-api.asterpay.io/mcp
- DeerFlow: https://github.com/bytedance/deer-flow
Licensed Apache-2.0.