ceven

BTCPay Server

Syncs Bitcoin payment requests and store events into your operational tools, automates order fulfillment for crypto payments, and manages store configurations across your self hosted nodes.

Try BTCPay Server in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native BTCPay Server integration

    • Describe the outcome and Ceven picks the right BTCPay Server calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your BTCPay Server data, across all 16 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke BTCPay Server access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in BTCPay Server, when, and on whose behalf.
    • The agent pauses and asks when BTCPay Server is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach BTCPay Server.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every BTCPay Server action to support review and sign off.

Supported tools

Every action Ceven's agents can run on BTCPay Server, and when to use it.

Create payment request
Use this when a workflow needs to generate a new Bitcoin invoice for a customer after you have confirmed the store id.
Create store
Use this to provision a new store instance before you begin processing transactions for a new brand or product line.
Create user
Use this to register a new BTCPay Server user programmatically as an administrator.
Register webhook
Use this when you need the agent to receive instant notifications for store events like payment settled.
Delete API key
Revoke a specific api key to immediately prevent its use. Call this after identifying the key to revoke.
Delete payment request
Use this to archive or remove an existing payment request for a store that is no longer valid.
Delete store payout
Use this to cancel a payout that is no longer needed or was created in error.
Get API key
Pull the current api key details after authentication to verify access levels.
List API keys
Pull all api keys associated with the authenticated user for security auditing.
Get payment requests
List all payment requests for a specific store. Use this after confirming the store id.
Get server info
Pull server version, tor address, supported payment methods, and synchronization states.
Get store
Pull the full configuration and settings for a specific store instance.
Get user
Fetch profile data for a given user id or email address.
Get store webhook
Verify the configuration or status of a specific webhook for a given store after creation.
List store webhooks
Pull all webhooks registered for a store for management or auditing purposes.
List apps
Pull basic metadata for every app currently installed in a specific store.
Create BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
Get BTCPay Server Info
Tool to retrieve information about the btcpay server instance. use when needing server version, tor address, supported payment methods, and synchronization states.
Get BTCPay Server User
Tool to retrieve information about a specific user. use when you need to fetch profile data for a given user id or email.
Update BTCPay Server User
Tool to update current user information. use when you need to modify your authenticated user profile on btcpay server.

21 actions · scroll to see them all

Frequently asked questions

Ceven connects to your BTCPay Server instance via the Green API using an API key you generate in your store settings. Because BTCPay Server is self hosted, you must ensure your server firewall allows incoming requests from Ceven IP addresses. You will create an API key with the specific permissions required for the workflows you intend to run, such as payment request creation or store management. Once the key is entered into Ceven, the agent tests the connection by calling the server info endpoint to verify the version and synchronization state of your node before enabling the rest of the toolset.
Yes. Ceven uses the register webhook action to tell your BTCPay Server where to send event notifications. When a customer pays a Bitcoin invoice and the transaction reaches the required number of confirmations on the blockchain, your server sends a webhook to Ceven. The agent then parses that event and triggers the next step in your workflow, such as updating a database or sending a digital download. This removes the need for you to manually refresh your dashboard to see if a payment has landed, creating a seamless experience for your customers.
If your self hosted server goes offline, Ceven will be unable to call the API or receive webhooks. Unlike hosted services, the reliability of the integration depends entirely on your server uptime. However, Ceven implements a retry logic for outbound API calls. If a request fails due to a connection timeout, the agent will attempt to reconnect several times before flagging an error in your workflow logs. We recommend using a monitoring tool to alert you if your node drops, as Ceven cannot wake up a dead server or process payments while the node is unreachable.
One critical quirk of BTCPay Server is that it does not impose a global rate limit like a centralized SaaS, but your own hardware and network configuration do. If you run a very high volume of payment requests on a low power VPS, you may experience timeouts or 502 errors during API calls. Additionally, the Green API requires specific permissions for each key. If you find that a Ceven action is failing with a 403 Forbidden error, it is almost always because the API key you provided lacks the specific permission for that action, such as the permission to create stores or manage users.
Yes. Ceven allows you to define multiple connection profiles for BTCPay Server. You can map different workflows to different server instances based on the environment or the region. For example, you can have one workflow that manages a production server for customer payments and another that manages a testnet server for development. The agent can even move data between them if you build a workflow to do so, allowing you to audit transactions across different nodes from a single centralized dashboard without switching browser tabs or logging into multiple servers.
No. Ceven never asks for and never stores your private keys or seed phrases. BTCPay Server is designed so that the merchant retains full control of the funds. Ceven only interacts with the BTCPay Server API to read payment statuses, create invoices, and manage store settings. Your private keys remain safely stored on your own server or your hardware wallet. Ceven only sees the public data provided by the API, such as payment request IDs and confirmation counts, ensuring that your funds remain under your sole control at all times.
The agent uses the get server info tool to determine which payment methods your specific instance supports. Whether you are using on chain Bitcoin, the Lightning Network, or other supported coins via the BTCPay ecosystem, Ceven adapts the payment request creation to match your server configuration. If you enable Lightning payments on your store, the agent can create invoices that support both on chain and Lightning payments, and the webhook will notify Ceven regardless of which path the customer chose to complete the transaction, ensuring consistent fulfillment across all payment types.

Alternatives to BTCPay Server

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Coinbase Commerce logoCoinbase CommerceBitPay logoBitPayOpenNode logoOpenNode

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect BTCPay Server and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free