SWIFT Code Lookup Skill

What this skill does

Let your agent resolve SWIFT/BIC codes. Call it as an MCP tool to return the bank, branch, city and country for any code or bank name. 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 SWIFT Code Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · swiftlookuptool call

{
  "swift": "CHASUS33ARP"
}

result

count: 1
banks: [ 1 item ]

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

Sign in to try

Ways to use it

Live data, no endpoint wiring

Enable SWIFT Code Lookup and your app can look up swift code through one connection — no client library for a finance API, no keys to rotate per provider. The skill answers over MCP or REST using the key you already have.

A tool your agent reaches for

Over MCP, SWIFT Code Lookup shows up as the swiftlookup tool your model calls whenever a task needs live numbers — it decides when, you don't write the glue.

Ship it in an afternoon

Flip the skill on and call it from your backend the same day; there's nothing to deploy and nothing to maintain as the underlying data changes.

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.

swiftlookup

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/swiftlookup

Ask your agent

“Enable SWIFT Code Lookup and ask your agent to look up swift code.”
“What's the latest price and how has it moved today?”

SWIFT Code Lookup Skill, answered

How to connect it over MCP or REST.

How do I add SWIFT Code Lookup to my app or agent?

Enable the SWIFT Code Lookup Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the swiftlookup 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 look up swift code — 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 SWIFT Code Lookup appears as a standard tool with nothing skill-specific to integrate.

How many credits does a SWIFT Code Lookup 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 SWIFT Code Lookup is available immediately.

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

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

More Finance skills

Browse all skills

Live data, no endpoint wiring

A tool your agent reaches for

Ship it in an afternoon

SWIFT Code Lookup Skill, answered

Give your software a way to act on the world.

Scaling in production?