A pretrained race track spectators count classifier that sorts an image into one of 9 categories — the number of spectators at the race track. Use the race track spectators count API immediately, no training required, then adapt it to your own data when you need more.
Drop in a photo and get the prediction back. No signup, no setup.
A sample of the 9 labels this pretrained classifier chooses between.
Need a label that isn't here? Clone the classifier into your Nyckel console and edit the label set to fit your data.
Once you've added this classifier to your console, you get your own copy of it behind your own endpoint. 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"},
)
print(response.json())Example response
{
"labelName": "1-5",
"labelId": "label_...",
"confidence": 0.92
}Trained on a Nyckel-curated dataset covering 9 race track spectators count categories, served on Nyckel's own infrastructure — your image stays on Nyckel.
Send an image URL or file to the invoke endpoint; the response is a label with a confidence score.
Clone it, then correct predictions and add your own samples in the console — Nyckel retrains automatically, turning this into a custom model tuned to your data.
This function can assist race track management in monitoring real-time spectator counts during events. By analyzing the number of spectators, organizers can ensure they remain within capacity limits and enhance safety protocols.
By determining the number of fans attending events, marketing teams can analyze demographics and tailor promotional campaigns. Accurate data on spectator counts allows businesses to identify peak attendance trends and target specific audiences more effectively.
Security teams can use spectator count data to deploy resources more efficiently at race tracks. By knowing the expected number of attendees, they can adjust staffing levels and improve crowd management strategies to ensure safety.
Companies that sponsor events can benefit from accurate spectator counts to assess the ROI on their sponsorship. This data helps sponsors understand their audience reach and engagement levels, potentially influencing future sponsorship agreements.
Race track operators can analyze spectator attendance to optimize layout and facilities. This insight helps managers improve concessions, rest areas, and viewing spots based on where the largest crowds gather, enhancing the overall spectator experience.
By monitoring the fluctuating number of spectators, race track operators can dynamically adjust ticket prices for future events. This approach can help maximize revenue based on demand, encouraging higher attendance on less popular race days.
This feature can be harnessed to build historical databases of spectator attendance across different events and seasons. Analyzing this data can help track trends and patterns, informing future planning and investment decisions for race track events.
A zero-shot classifier uses a large foundation model's general knowledge to pick between your labels — no task-specific training, so new or edited labels work immediately. A Nyckel-trained classifier has been trained on labeled examples and runs on Nyckel's own infrastructure, which typically makes it faster, cheaper per call, and more accurate on data that resembles its training set. The "Under the hood" section on this page shows which kind this classifier is, and any classifier can be adapted into a trained one by adding your own examples.
Honestly: we can't know in advance — it depends on your data stream and how closely it resembles what this classifier has seen. The reliable way to find out is to measure it on your own data: start invoking the classifier with real traffic, or upload and annotate a set of images in the console — make sure they look like your production data, not idealized examples. Nyckel's evaluation metrics then show you exactly how it performs on that data before you rely on it.
No classifier is perfect, so Nyckel is built around the correction loop: invokes can be captured for review, you confirm or correct predictions 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.
No. This race track spectators count classifier works out of the box — clone it into your console and you'll have your own API endpoint in under a minute. Training data only enters the picture when you want to adapt it: your corrected predictions and uploaded samples improve the model, and you can also edit the label set to match your needs.
Trying the classifier on this page is free with no signup. Cloning it 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.
Add this pretrained classifier to your Nyckel console — you'll get a live API endpoint in under a minute, and a path to a custom model when you need one.