Unicode Lookup Skill

What this skill does

Let your agent inspect characters. Call it as an MCP tool to get any character's codepoint, UTF-16 encoding, category and 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 Unicode Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · unicodelookuptool call

{
  "character": "👋"
}

result

character: �
codepoint: U+D83D
decimal: 55357
hex: D83D
utf16: \uD83D
category: Control
name: null

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

Ways to use it

Turn IDs into detail

Enable Unicode Lookup and your app can look up unicode — expand an identifier into full structured detail — in a single call, no integration per source.

A tool your agent reaches for

Over MCP, your model calls unicodelookup to enrich data mid-workflow exactly when it's needed.

Enrich from your backend

Call Unicode Lookup over REST to look up unicode across a batch in a server-side 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.

unicodelookup

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

Ask your agent

“Enable Unicode Lookup and ask your agent to look up unicode.”
“Use the Unicode Lookup skill for me.”

Unicode Lookup Skill, answered

How to connect it over MCP or REST.

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

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

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

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

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

Turn IDs into detail

A tool your agent reaches for

Enrich from your backend

Unicode Lookup Skill, answered

Give your software a way to act on the world.

Scaling in production?