BTCPay Server
for LuumenAI
BTCPay Server is a free, open-source, self-hosted Bitcoin payment processor that enables merchants to accept Bitcoin payments without intermediaries.
Operate BTCPay Server from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.
The BTCPay Server toolbox
16 tools: 8 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current API KeyRetrieve information about the current API key.
- ReadGet Payment RequestsList all payment requests for a specific store.
- ReadGet BTCPay Server InfoRetrieve information about the BTCPay Server instance.
- ReadGet StoreRetrieves complete configuration and settings for a specific BTCPay Server store by its ID.
- ReadGet BTCPay Server UserRetrieve information about a BTCPay Server user by ID or email.
- ReadGet Store WebhookRetrieves detailed configuration of a specific webhook registered for a BTCPay store, including its callback URL, subscribed events, enabled status, and automatic redelivery settings.
- ReadList Store WebhooksLists all webhooks registered for a BTCPay Server store.
- ReadList AppsRetrieve all apps (Point of Sale, Crowdfund, etc.) associated with a specific BTCPay Server store.
- WriteCreate Payment RequestCreates a new payment request in a BTCPay Server store. Approval by default
- WriteCreate StoreCreate a new store in BTCPay Server. Approval by default
- WriteCreate BTCPay Server UserCreate a new BTCPay Server user. Approval by default
- WriteRegister a WebhookRegisters a new webhook for a BTCPay store to receive real-time notifications when store events occur (e.g., invoice created, payment received, invoice settled). Approval by default
- WriteDelete API KeyRevoke a specific API key to immediately prevent its use for authentication. Approval by default
- WriteDelete Payment RequestDeletes (archives) a specific payment request from a BTCPay Server store. Approval by default
- WriteCancel Store PayoutCancels (deletes) a specific payout from a BTCPay Server store. Approval by default
- WriteUpdate BTCPay Server UserUpdate the profile of the currently authenticated BTCPay Server user. Approval by default
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create payment request, create store, create btcpay server user, register a webhook, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to BTCPay Server — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SAP BTPGateways, jobs, and subaccounts operated from one governed chat.
SalesforceRecords and integration jobs checked without a second console.
SAP S/4HANAJobs, queues, and records in SAP S/4HANA without a second console.
SAP SuccessFactorsJobs, queues, and records in SAP SuccessFactors without a second console.Put BTCPay Server to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.