NAICS Lookup Skill

Look up naics

Reference Data2 credits/callMCP · RESTNew
See how to connect

Let your agent classify a business into a NAICS code from a description, or explain any code with its SBA size standard. 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.

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

vervekit · naicslookuptool call
{
  "code": "541511"
}
result
count
1
results
[ 1 item ]
notFound
[ 0 items ]
Run it with your own input. Live calls happen in your dashboard, on your key.
Sign in to try

Trusted facts in one call

Enable NAICS Lookup and your app can look up naics from a live source instead of shipping a lookup table you have to keep current.

A tool agents call for ground truth

Over MCP, your model calls naicslookup to fetch a reference value at the moment it needs it, rather than recalling it imperfectly.

REST from any stack

Call NAICS Lookup directly to look up naics inline, one key across every skill.

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.

naicslookup
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/naicslookup
  • “Enable NAICS Lookup and ask your agent to look up naics.”
  • “Use the NAICS Lookup skill for me.”

NAICS Lookup Skill, answered

How to connect it over MCP or REST.

How do I add NAICS Lookup to my app or agent?
Enable the NAICS Lookup Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the naicslookup 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 naics — 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 NAICS Lookup appears as a standard tool with nothing skill-specific to integrate.
How many credits does a NAICS Lookup call cost?
Each call costs 2 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 NAICS Lookup is available immediately.
Where does the data come from, and what shows on my bill?
VerveKit runs on APIVerve, our production data engine; NAICS Lookup is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Other ways to use NAICS Lookup

Same data, same VerveKit account, same credit balance — one key works on all of them.

Give your software a way to act on the world.

Scaling in production?

The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.

See pricing