Detect object
Object Detector finds the objects in an image, from people, cars and traffic lights to dogs, laptops and cups, and returns each one's label, a numeric confidence and its bounding box in pixels and as fractions of the image, plus a count per label. Filter by minimum confidence or by the labels you care about. 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 Object Detector Skill — exactly what your agent gets back when it makes the call.
{
"image": "http://images.cocodataset.org/val2017/000000039769.jpg",
"minConfidence": 0.5
}Enable Object Detector and your app or agent can detect object on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.
Over MCP, Object Detector appears to your model as the objectdetector tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.
Prefer to call it directly? Any language that can send a GET can hit Object Detector to detect object inline in your own server-side code.
Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.
It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.
objectdetectorCall it from your server with one request and your key. Node, Python, Go — anything that can send a GET.
GET /v1/objectdetectorHow to connect it over MCP or REST.
Same data, same VerveKit account, same credit balance — one key works on all of them.
The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.
See pricing