Bank Lookup Skill

What this skill does

Let your agent identify any US bank or credit union from a name, routing number, SWIFT code or website, including closed and merged ones. 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 Bank Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · banklookuptool call

{
  "name": "Wells Fargo"
}

result

count: 1
totalMatches: 3
banks: [ 1 item ]
routingCheck: null
ibanCheck: null

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 Bank Lookup and your app can look up bank 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, Bank Lookup shows up as the banklookup 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.

banklookup

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

Ask your agent

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

Bank Lookup Skill, answered

How to connect it over MCP or REST.

How do I add Bank Lookup to my app or agent?

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

How many credits does a Bank Lookup call cost?

Each call costs 10 credits. 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 Bank Lookup is available immediately.

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

VerveKit runs on APIVerve, our production data engine; Bank 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

Bank Lookup Skill, answered

Other ways to use Bank Lookup

Give your software a way to act on the world.

Scaling in production?