Documentation Index
Fetch the complete documentation index at: https://docs.kynasmith.dev/llms.txt
Use this file to discover all available pages before exploring further.
Accepted frames
Kynasmith bills on accepted frames — the pose frames that are successfully received and processed during a detection session. This page explains how billing works and how you can predict costs.What is an accepted frame?
An accepted frame is a pose frame that Kynasmith successfully receives and processes during a detection session. Each accepted frame counts toward your monthly quota. Frames are not billed if the session has already ended, if the frame is a duplicate, or if it was dropped due to connection issues.Do low-confidence frames count?
Yes. Frames with low landmark confidence are still processed and billed. Low-quality detections are valid signals for movement detection. If no pose is detected in a video frame, no pose frame is sent to Kynasmith, so nothing is billed for that video frame.How to predict billing
You can estimate billing impact before submitting frames:- Check
accepted_frames_totalon completed sessions — The session result includes the total count of accepted frames, which matches what was billed. - Use short sample videos in
replaymode during development to calibrate frame counts before running on full-length content. - Use the usage API to check cumulative usage across sessions:
GET /api/usage— Organization-level totalsGET /api/usage/projects/{project_id}— Project-level breakdown
Reducing frame consumption
- Lower your frame rate — If your use case does not require 30fps analysis, configure your SDK or integration to send frames at a lower rate.
- Use
replaymode with trimmed videos during development and testing. - Finalize sessions promptly when you have all the data you need, so no additional frames are processed.
- Cancel sessions that are no longer needed rather than letting them idle.