Reference guides for the finance apps an AI agent can work with: every endpoint, the permission each one needs, and how to give agents safe, governed access.
The Adyen API is how an app or AI agent takes a payment, captures or refunds it, removes a shopper's saved card, sends a payout, or configures a merchant account.
The Airwallex API is how an app or AI agent works with an Airwallex account: accepting a payment, refunding it, paying out to a beneficiary, or reading the balance across currencies.
The BILL API is how an app or AI agent works with a BILL organization: drafting a bill, adding a vendor, paying a bill, or sending an invoice to a customer.
The Brex API is how an app or AI agent works with a company's Brex account: reading settled card and cash transactions, checking account balances, issuing and locking cards, sending transfers to vendors, and managing expenses and receipts.
The Chargebee API is how an app or AI agent works with a Chargebee site: creating a subscription, charging an invoice, adding a customer, building the product catalog, or issuing a credit note.
The Checkout.com API is how an app or AI agent works with a Checkout.com account: requesting a payment, capturing or refunding it, tokenizing a card, raising a payout, or handling a dispute.
The Expensify API is how an app or AI agent works with an Expensify account: exporting report and card data, creating expenses and reports, reading and updating policies, and marking reports reimbursed.
The FreshBooks API is how an app or AI agent works with a FreshBooks account: creating and sending an invoice, recording a payment, adding a client, logging an expense, or tracking time on a project.
The GoCardless API is how an app or AI agent collects bank payments: creating a customer, setting up a mandate to take Direct Debit, charging a payment, or running recurring billing through subscriptions.
The Mercury API is how an app or AI agent works with a Mercury banking account: reading account balances and transaction history, managing recipients, sending money to a saved recipient, and issuing or freezing cards.
The Mollie API is how an app or AI agent works with a Mollie account: taking a payment, refunding a charge, creating a customer, or running recurring billing through mandates and subscriptions.
The NetSuite API is how an app or AI agent works with a NetSuite account: reading and writing records like customers and items, creating transactions such as invoices and sales orders, and running queries across any record.
The Paddle API is how an app or AI agent runs billing in a Paddle account: creating products and prices, charging a customer through a transaction, managing recurring subscriptions, and refunding a charge as an adjustment.
The PayPal API is how an app or AI agent works with a PayPal business account: creating a checkout order, capturing or refunding a payment, billing a subscriber, sending an invoice, or paying out to many recipients at once.
The Plaid API is how an app or AI agent connects to a person's bank to read transactions, pull account and routing numbers, check balances, fetch identity, or read investments, liabilities, and income.
The QuickBooks API is how an app or AI agent works with a QuickBooks company's books: creating an invoice, recording a payment, adding a customer or vendor, and querying bills and accounts.
The Ramp API is how an app or AI agent works with a Ramp account: listing card transactions, issuing a virtual card, setting a spend limit, or reading reimbursements and bills.
The Razorpay API is how an app or AI agent works with a Razorpay account: creating an order, capturing a payment, refunding a customer, running recurring subscriptions, or sending a bank payout through RazorpayX.
The Recurly API is how an app or AI agent runs subscription billing on a site: creating an account, starting or canceling a subscription, collecting or refunding an invoice, and applying a coupon.
The Sage API is how an app or AI agent works with a Sage Business Cloud Accounting business: listing contacts, raising a sales invoice, recording a payment against a bill, or posting a journal to the ledger.
The Spendesk API is how an app or AI agent works with a company's spend data: reading settlements and payables, pulling the receipts attached to an expense, and listing suppliers, members, and cost centers.
The Square API is how an app or AI agent works with a Square seller account: taking a payment, refunding a charge, creating an order, updating a customer, or changing the catalog and stock.
The Stripe API is how an app or AI agent works with a Stripe account: taking a payment, refunding a charge, creating a customer, or running recurring billing through subscriptions and invoices.
The Wave API is how an app or AI agent works with a Wave business: creating an invoice, recording a customer, posting an accounting transaction, or reading the chart of accounts.
The Wise API is how an app or AI agent moves money internationally: pricing a transfer with a quote, adding a recipient, creating and funding a transfer, and reading the currency balances in a multi-currency account.
The Xero API is how an app or AI agent works with a Xero organisation: raising an invoice, recording a payment, adding a contact, reconciling a bank transaction, or pulling a Profit and Loss report.
The Zoho Books API is how an app or AI agent works with a Zoho Books organization: creating and emailing invoices, adding customers and vendors, recording bills and expenses, and applying customer payments.
A finance API is how an app or AI agent works with payments, banking, accounting, and spend. The platforms here, including Stripe, QuickBooks, Xero, and Plaid, hold money movement and financial records, and their APIs let an agent read a transaction, create an invoice, reconcile an account, or take a payment.
These APIs can move money and expose financial detail, so the permission attached to an access key is the central control: reading a transaction is narrow, while issuing a refund or paying a bill is not. Access runs on an access key, and most platforms separate read access from the permission to move funds and offer restricted keys. A governed layer lets an agent that reconciles invoices read accounting records without holding a key that can also send a payment.
Bollard AI sits between a team's AI agents and the apps it runs on. Grant each agent exactly the access it needs, read or write, app by app, and every call is checked and logged.