API - Credits and Billing

Each detection call draws from your TrailCamHub credit balance — the same balance you use across the app.

What a call costs

• Image: 1 credit

• Video: 10 credits

When credits are charged — on submit
Credits are deducted the moment a request is submitted, not when it succeeds. You're paying for the analysis to run, not for a particular result.

Because of that:

• A call still costs credits even when nothing is found — no animals detected, or no antlers on a checked deer. An empty result is still a result; the analysis ran.

• Since the charge is taken at submission, a request that's accepted but then can't be completed (for example a URL we can't reach, or a video with no readable frames) is also charged. Make sure your image and video URLs are public and valid before sending.

• Requests that are rejected before processing — a missing or invalid API key, a malformed body, or an empty balance — are not charged.

What happens at zero balance
If your balance can't cover a call, the request is rejected with HTTP 402 and isn't processed (and isn't charged). Top up to continue.

Checking your balance and buying credits
There's no API endpoint for your balance. Your current credits are shown in the TrailCamHub app, and that's also where you buy more — the same credit packs used across the platform. Plan your usage around the rates above (1 per image, 10 per video, charged up front), since you can't poll the balance programmatically.