Fern MCP integration for AI agents.
Connect AI agents to Fern through 7 structured actions, including get customer, get exchange rate, and get payment account. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Fern integration exposes
The Fern Agent App exposes 7 provider-backed actions for finance work. Its current contract lets an authorized agent retrieve one fern customer by id, retrieve fern exchange rate and fee details for source and destination currencies, and retrieve one fern payment account by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Fern account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Fern capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve one Fern customer by ID.
INPUTS: customerId / includeVerification / includePaymentMethods
get_exchange_rateREADRetrieve Fern exchange rate and fee details for source and destination currencies.
INPUTS: sourceCurrency / sourcePaymentMethod / sourceAmount / destinationPaymentMethod / destinationCurrency
get_payment_accountREADRetrieve one Fern payment account by ID.
INPUTS: paymentAccountId
get_transactionREADRetrieve one Fern transaction by ID.
INPUTS: transactionId
list_customersREADList Fern customers with optional organization filtering and cursor pagination.
INPUTS: pageToken / pageSize / organizationId
list_payment_accountsREADList Fern payment accounts for a customer with cursor pagination.
INPUTS: customerId / pageToken / pageSize
list_transactionsREADList Fern transactions with optional customer, payment account, and organization filters.
INPUTS: pageToken / pageSize / customerId / paymentAccountId / organizationId
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
customerIdREQUIRED- Unique identifier of the customer.
includeVerificationOPTIONAL- Whether to include verification details.
includePaymentMethodsOPTIONAL- Whether to include available payment methods in the response.
get_exchange_rate
sourceCurrencyREQUIRED- Currency label or contract address for the source currency.
sourcePaymentMethodREQUIRED- Payment method for the source exchange rate.
sourceAmountOPTIONAL- Amount to be sent. When provided, Fern returns fees and destination amount.
destinationPaymentMethodREQUIRED- Payment method for the destination exchange rate.
destinationCurrencyREQUIRED- Currency label or contract address for the destination currency.
get_payment_account
paymentAccountIdOPTIONAL- Unique identifier of the payment account.
get_transaction
transactionIdOPTIONAL- Unique identifier of the transaction.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve one Fern customer by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerVerify with Get Exchange Rate
Retrieve Fern exchange rate and fee details for source and destination currencies. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_exchange_rateSAFETY BOUNDARY
Operate Fern with explicit limits
- Authorize Fern with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Fern data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `customers:read`, `exchange_rates:read`, `payment_accounts:read`, and `transactions:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Fern task completed successfully.
CONNECTION MODEL
API key
Fern API key sent as a Bearer token. Create or manage API keys in the Fern developer dashboard: https://dashboard.fernhq.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Fern.