What authentication does the CurrencyLayer API use?

The CurrencyLayer API authenticates with an API access key passed as the access_key query parameter, per its OpenAPI spec. Through Jentic the key is stored once by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.

Is there a CurrencyLayer MCP server?

You don't need an MCP server to give your agent the CurrencyLayer API. Jentic connects it directly from the API Directory: import it, store your access key once, and your agent calls the rate and conversion operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

Can I limit what my agent is allowed to do with the CurrencyLayer API?

Yes. Every operation is a read, so the agent can never modify data, and you choose which operations it may call. You might allow live rates and conversion while blocking the time-series and change endpoints, with every call logged.

How many currencies does the CurrencyLayer API cover?

According to its specification the API provides rates for 168 world currencies. You can list the supported currencies through the list operation and request live, historical, or time-series rates for any of them.

What are the rate limits for the CurrencyLayer API?

The OpenAPI spec does not specify rate limits. Check the CurrencyLayer documentation at https://currencylayer.com/documentation for current plan limits before running high-volume rate lookups.

How do I convert an amount between currencies through Jentic?

Search Jentic by intent, for example 'convert an amount between two currencies', and Jentic returns the convert operation with its input schema. Your agent supplies the amount and the currency pair and reads back the converted value. To run it on your own infrastructure, install Jentic One from its GitHub repo.