Bluetooth Company Lookup Skill

What this skill does

Let your agent identify Bluetooth device makers. Call it as an MCP tool to resolve a SIG company identifier to its manufacturer 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 Bluetooth Company Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · bluetoothlookuptool call

{
  "companyid": 76
}

result

companyId: 76
companyIdHex: 0x004C
found: true
company: Apple, Inc.

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

Ways to use it

Host & IP lookups, no plumbing

Enable Bluetooth Company Lookup and your app can look up bluetooth company without standing up your own resolver or stitching together network APIs.

A tool agents call to check hosts

Over MCP, bluetoothlookup is the tool your model reaches for to verify connectivity facts instead of assuming them.

One request, any language

Call Bluetooth Company Lookup over REST from any backend to look up bluetooth company inline, using the key you already have.

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.

bluetoothlookup

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

Ask your agent

“Enable Bluetooth Company Lookup and ask your agent to look up bluetooth company.”
“Look up everything you can about this host.”

Bluetooth Company Lookup Skill, answered

How to connect it over MCP or REST.

How do I add Bluetooth Company Lookup to my app or agent?

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

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

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

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

Host & IP lookups, no plumbing

A tool agents call to check hosts

One request, any language

Bluetooth Company Lookup Skill, answered

Give your software a way to act on the world.

Scaling in production?