CurrencyBeacon MCP integration for AI agents.
Connect AI agents to CurrencyBeacon through 5 structured actions, including get currencies, convert currency, and get historical rates. Review authentication…
- ACTION CONTRACTS
- 5
- 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 CurrencyBeacon integration exposes
The CurrencyBeacon Agent App exposes 5 provider-backed actions for finance and data work. Its current contract lets an authorized agent retrieve the supported currencies exposed by currencybeacon, convert an amount between two currencies using currencybeacon exchange rates, and retrieve historical exchange rates for a specific date from currencybeacon. 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 CurrencyBeacon account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real CurrencyBeacon capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_currenciesREADRetrieve the supported currencies exposed by CurrencyBeacon.
convert_currencyREVIEWConvert an amount between two currencies using CurrencyBeacon exchange rates.
INPUTS: from / to / amount / date
get_historical_ratesREADRetrieve historical exchange rates for a specific date from CurrencyBeacon.
INPUTS: base / date / symbols
get_latest_ratesREADRetrieve the latest exchange rates for a base currency from CurrencyBeacon.
INPUTS: base / symbols
get_timeseries_ratesREADRetrieve exchange rates across a date range from CurrencyBeacon.
INPUTS: base / startDate / endDate / symbols
INPUT CONTRACTS
Know what the action needs before it runs.
convert_currency
fromREQUIRED- Source currency code for the conversion.
toREQUIRED- Target currency code for the conversion.
amountREQUIRED- Positive amount to convert.
dateOPTIONAL- Optional historical date in YYYY-MM-DD format for historical conversion.
get_historical_rates
baseOPTIONAL- Base currency code for the historical exchange rates.
dateREQUIRED- Historical date in YYYY-MM-DD format.
symbolsOPTIONAL- List of target currency codes to include in the response.
get_latest_rates
baseOPTIONAL- Base currency code for the requested exchange rates.
symbolsOPTIONAL- List of target currency codes to include in the response.
get_timeseries_rates
baseOPTIONAL- Base currency code for the timeseries exchange rates.
startDateREQUIRED- Start date of the timeseries range in YYYY-MM-DD format.
endDateREQUIRED- End date of the timeseries range in YYYY-MM-DD format.
symbolsOPTIONAL- List of target currency codes to include in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Currencies
Retrieve the supported currencies exposed by CurrencyBeacon. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_currenciesVerify with Get Historical Rates
Retrieve historical exchange rates for a specific date from CurrencyBeacon. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_historical_ratesSAFETY BOUNDARY
Operate CurrencyBeacon with explicit limits
- Authorize CurrencyBeacon with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned CurrencyBeacon 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.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in CurrencyBeacon rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the CurrencyBeacon task completed successfully.
CONNECTION MODEL
API key
CurrencyBeacon API key sent with the api_key query parameter. Get it from https://currencybeacon.com/account/dashboard.
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
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 CurrencyBeacon.