DTC Lookup Skill

What this skill does

DTC Lookup explains OBD-II diagnostic trouble codes such as P0301 or U0100. It returns the code's system and standard title, which warning light it turns on, and on paid plans the full description, likely causes ranked by likelihood, symptoms, repair difficulty, estimated cost and labor hours, and related codes. Carmaker-specific codes are covered for 32 makes. 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 DTC Lookup Skill — exactly what your agent gets back when it makes the call.

vervekit · dtclookuptool call

{
  "code": "P0301"
}

result

code: P0301
found: true
system: Powertrain
subsystem: Ignition
codeType: generic
title: Cylinder 1 Misfire Detected
description: Misfires concentrated on cylinder 1. A c…
warningLight: Check Engine Light

+14 more fields

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

Ways to use it

One toggle, a new capability

Enable DTC Lookup and your app or agent can look up dtc on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, DTC Lookup appears to your model as the dtclookup tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit DTC Lookup to look up dtc inline in your own server-side code.

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.

dtclookup

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

Ask your agent

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

DTC Lookup Skill, answered

How to connect it over MCP or REST.

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

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

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

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

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

One toggle, a new capability

A tool agents call themselves

REST from any backend

DTC Lookup Skill, answered

Other ways to use DTC Lookup

Give your software a way to act on the world.

Scaling in production?