Object Counting Agent

Anything visually distinct enough to tell apart in a photo: tyres, pallets, cartons, packages, tools, parts, bottles, crates, plants. It counts a defined object type rather than everything in frame, so you get “34 cartons” rather than a total of every shape the camera saw.

It depends on how much is in the frame. A single item comes back in a few hundred milliseconds. A full rack or pallet with many items to separate takes up to about ten seconds, against roughly three minutes to count the same rack by hand and longer again if it needs a recount. The consistency matters more than the speed: the same photo counted twice returns the same number.

Every count returns a confidence score alongside the number, so low-confidence results can be routed for a human check instead of being trusted silently. Accuracy depends on your images, since lighting, angle and occlusion all matter, which is why the confidence score is part of the output rather than hidden behind it.

Either. Teams capture on web or mobile as part of a workflow, and counts can also run against images from fixed cameras. The CCTV and IP camera integration guide covers feeding existing camera infrastructure through the API.

No. Counting runs on what you submit, with no training project first. If you need specific items identified rather than counted, that is product recognition, and much of that works as it is too, with a catalogue needed only where the answer has to be your exact SKU.

Counting answers “how many of this thing are here”. Product recognition answers “which exact item is this”, identifying a specific SKU or variety. Stocktaking usually wants counting; checkout and inventory accuracy usually want recognition. Many operations use both.

Yes, and normally by configuring what you already run rather than building against anything. A count can land on the record it belongs to – in Salesforce, for instance – or be pushed to whoever needs to act on it through Slack, Zapier or Power Automate. Nobody has to remember to go and look somewhere.

Stocktakes and cycle counts set up as recurring workflows, proof of delivery verification, yard and asset counts, and counting parts or tools before and after a job. The pattern is the same each time: the count is assigned to a team, captured in the app where the work happens, and kept as a record instead of a number written on a clipboard and typed in later.