Currency Conversion Skill

What this skill does

Give your agent live exchange rates. Call it as an MCP tool to convert any amount across 170+ currencies at real-time rates — no FX feed to wire up. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Currency Conversion Skill — exactly what your agent gets back when it makes the call.

vervekit · currencyconvertertool call

{
  "value": 1,
  "from": "USD",
  "to": "EUR"
}

result

from: USD
to: EUR
value: 1
convertedValue: 0.921456
rate: 0.921456
change24h: -0.002134
change24hPct: -0.2312
changeDirection: down

+2 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Live conversion, no endpoint

Enable Currency Converter and your app can convert between currencies at today's rate without integrating an FX provider or managing another key.

A tool agents reach for

Over MCP, your model calls the currencyconverter tool whenever a task involves money in more than one currency — you don't wire it, it decides.

Batch it server-side

Call currencyconverter over REST to convert a whole column of amounts in a backend job, one key for all of it.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

currencyconverter

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/currencyconverter

Ask your agent

“Enable Currency Conversion and ask your agent to convert currency.”
“What's the latest price and how has it moved today?”

Currency Conversion Skill, answered

How to connect it over MCP or REST.

How do I add Currency Conversion to my app or agent?

Enable the Currency Conversion Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the currencyconverter tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to convert currency — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Currency Conversion appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Currency Conversion call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Currency Conversion is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Currency Conversion is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Live conversion, no endpoint

A tool agents reach for

Batch it server-side

Currency Conversion Skill, answered

Give your software a way to act on the world.

Scaling in production?