Integrations

Last updated: August 2026

BTCMatic pushes signed, traced events out and lets external systems wake rules — never decide for them. Execution decisions are made only by the BTCMatic engine, and live order rules can only ever be enabled from the app.

n8n & TradingView

Signed outbound webhooks (HMAC-SHA256, frozen t=,v1= format), the verified n8n community node n8n-nodes-btcmatic, and the inbound webhook trigger: a TradingView alert or an n8n HTTP node POSTs a flat JSON body to your hook URL and any rule with the Incoming webhook trigger evaluates it. Read the n8n & TradingView guide →

Agent API (402 / L402 over Lightning)

Read-only Bitcoin context for autonomous agents, paid per call in sats (about 21 sats) with no account: open security incidents, fee percentile over 90 days, price-change windows, mempool size, and "how often did this condition occur". MCP server: btcmatic-mcp-server. Read the agent API guide →

API keys

Pro and Power plans mint API keys (btcm_…) for the management surface — rules, fire history, backtests, hooks, dry-run automation. A key cannot create a live order rule, touch billing, exchange keys or channels. OpenAPI: https://api.btcmatic.com/docs.

Machine entry points

• Discovery document for agents: GET https://api.btcmatic.com/agent
• MCP server source: github.com/btcmatic-com/btcmatic-mcp-server
• n8n node on npm: n8n-nodes-btcmatic
• This site for LLMs: /llms.txt · /agents.md