currencyapi MCP integration for AI agents.
Connect AI agents to currencyapi through 5 structured actions, including get api status, convert currency, and get historical rates. Review authentication, i…
- 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 currencyapi integration exposes
The currencyapi Agent App exposes 5 provider-backed actions for finance and data work. Its current contract lets an authorized agent retrieve current currencyapi account quota usage, convert a monetary amount into one or more currencies with currencyapi, and retrieve historical exchange rates for a specific date from currencyapi. 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 currencyapi account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real currencyapi capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_statusREADRetrieve current currencyapi account quota usage.
convert_currencyREVIEWConvert a monetary amount into one or more currencies with currencyapi.
INPUTS: value / date / base_currency / currencies / type
get_historical_ratesREADRetrieve historical exchange rates for a specific date from currencyapi.
INPUTS: date / base_currency / currencies / type
get_latest_ratesREADRetrieve the latest exchange rates from currencyapi.
INPUTS: base_currency / currencies / type
get_supported_currenciesREADRetrieve supported currency metadata from currencyapi.
INPUTS: currencies / type
INPUT CONTRACTS
Know what the action needs before it runs.
convert_currency
valueREQUIRED- Numeric amount to convert from the base currency.
dateOPTIONAL- Date in YYYY-MM-DD format.
base_currencyOPTIONAL- Currency code using uppercase ASCII letters or digits.
currenciesOPTIONAL- List of currency codes to include in the response.
typeOPTIONAL- Currency type filter. Supported values are fiat, metal, or crypto.
get_historical_rates
dateREQUIRED- Date in YYYY-MM-DD format.
base_currencyOPTIONAL- Currency code using uppercase ASCII letters or digits.
currenciesOPTIONAL- List of currency codes to include in the response.
typeOPTIONAL- Currency type filter. Supported values are fiat, metal, or crypto.
get_latest_rates
base_currencyOPTIONAL- Currency code using uppercase ASCII letters or digits.
currenciesOPTIONAL- List of currency codes to include in the response.
typeOPTIONAL- Currency type filter. Supported values are fiat, metal, or crypto.
get_supported_currencies
currenciesOPTIONAL- List of currency codes to include in the response.
typeOPTIONAL- Currency type filter. Supported values are fiat, metal, or crypto.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Status
Retrieve current currencyapi account quota usage. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_statusVerify with Get Historical Rates
Retrieve historical exchange rates for a specific date from currencyapi. 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 currencyapi with explicit limits
- Authorize currencyapi with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned currencyapi 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 currencyapi rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the currencyapi task completed successfully.
CONNECTION MODEL
API key
currencyapi API key sent with the apikey header. Get it from https://app.currencyapi.com/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 currencyapi.