A pretrained detector that finds every instance of cars in an image and returns each one with a bounding box — count the detections and you have your number. Use the API immediately, no training required, then adapt it to your own data when you need more.
Drop in a photo and get the count back. No signup, no setup.
Detection functions run behind your own endpoint — create a free account to set one up in the console, then invoke it with any HTTP client:
curl
curl -X POST "https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke" \
-H "Authorization: Bearer $NYCKEL_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data": "https://example.com/photo.jpg"}'
Python
import requests
# Get an access token: https://www.nyckel.com/docs/api/overview/authentication/
token = "YOUR_ACCESS_TOKEN"
response = requests.post(
"https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke",
headers={"Authorization": "Bearer " + token},
json={"data": "https://example.com/photo.jpg"},
)
result = response.json()
print(len(result[0]["boxes"])) # the count
Example response
[
{
"labelId": "label_...",
"boxes": [
{ "centerX": 0.42, "centerY": 0.31, "width": 0.18, "height": 0.12, "confidence": 0.93 },
{ "centerX": 0.71, "centerY": 0.55, "width": 0.22, "height": 0.15, "confidence": 0.88 }
]
}
]
One box per cars found — the number of boxes is your count, and each box tells you where in the photo that detection is.
The detector locates each instance of cars it finds in the photo and returns one detection per instance, each with a bounding box. Counting the detections gives you the number — that's what the widget on this page shows — and the boxes tell you where in the image each one is.
Honestly: we can't know in advance — it depends on your data stream and how closely it resembles what this detector has seen. The reliable way to find out is to measure it on your own data: start invoking the detector with real traffic, or upload and annotate a set of images in the console — make sure they look like your production photos, not idealized examples. Nyckel's evaluation metrics then show you exactly how it performs on that data before you rely on it.
No detector is perfect, so Nyckel is built around the correction loop: invokes can be captured for review, you confirm or correct detections in the console, and corrections become training data. Over time the model adapts to your data distribution — accuracy on your traffic improves with use rather than staying fixed.
Trying the detector on this page is free with no signup. Using the API requires a free account, and the free tier covers your first API calls each month — see nyckel.com/pricing for current limits and paid tiers.
Create a free Nyckel account — you'll get detection functions behind a live API endpoint, and a path to a custom model trained on your own data.