Plans / Partner API
Routines and alerts for your customers’ cameras.
For camera brands, dealers and installers, internet providers and property software. Send events and frames; get back plain observations, routine results with a coverage line, and alerts your customers can read.
The API isn’t open yet, and nothing is billed.
Garage
Example photo
PeekabooHome
Garage door: open at 10:00 PM
Checked at 10:00 PM on the Garage camera. Peekaboo looks again every 30 minutes until 1:00 AM.
At the next look
Garage door: closed at 10:30 PM
Seen closed at 10:30 PM on the Garage camera.
What the API returns.
Three things, all as structured data with plain English text alongside. The API reference has every endpoint, and fields may still change.
-
Observations
One per analyzed frame: people, vehicles and packages counted; animals and carriers seen; door and gate states; a short description using roles and objects; light level; and whether the frame was usable.
-
Routine results
For each routine window: met, missed, couldn’t confirm, or seen when it shouldn’t be, with first and last seen times and the coverage line that explains it.
-
Alerts
What was sent and who it named, from
GET /alertsor as signed webhooks when each one is made. Morning briefs go out from the app; they aren’t in the API.
An observation, field by field.
| Field | What it holds | Example |
|---|---|---|
usable | Whether the frame could be read at all | true |
lighting | day, dusk, night_color, night_ir, dark, glare or unknown | “day” |
people | How many people are in frame, or null if it can’t tell | 1 |
vehicles | How many vehicles are in frame | 0 |
packages | Packages visible | 1 |
animals | Animals visible | [] |
carriers | Carrier names or vehicle markings seen, never identities | [] |
states | The states your routines ask about | garage_door: closed |
description | One plain sentence | “A courier in a brown uniform left a package by the door.” |
Planned prices.
Planned, per event, no minimums. You’d pay for frames Peekaboo reads, not for every motion your cameras log.
- First 2,000 analyzed events each month
- Free
- An analyzed event is one frame that Peekaboo reads. An event sent as a label alone is recorded without reading a frame, and wouldn’t be charged.
- Each analyzed event after that
- $0.004
- For scale: a camera with 10 analyzed events a day is about 300 a month, or $1.20 once you’re past the free 2,000.
- An app under your own name
- Ask us
- We haven’t built an app under your name. If you’d want one, tell us in the form below.
Planned prices. The API isn’t open yet and nothing is billed. To talk about volumes, use the form below.
The same rules apply.
Partner traffic runs through the same product rules as Peekaboo itself. They aren’t options.
-
No identity.
No face recognition, names, face matching, watchlists or outside databases.
-
No audio.
Frames and event times only.
-
No verdicts.
No “intruder”, “suspicious” or “weapon”; a wording check removes them before anything is returned.
-
Honest uncertainty.
Unusable frames return “can’t tell”. A missed result needs pictures of the spot that were actually read, none more than 30 minutes apart and one in the last 15 minutes before the deadline. With fewer, it’s “couldn’t confirm”.
-
Heads-ups, not alarms.
Results are heads-ups for people, not alarm signals or dispatch triggers.
-
Retention.
Frames are kept 7 or 30 days, then deleted. Details.
Who we’d like to hear from.
Use the form below. A person will reply.
-
Camera brands
You want expectations, look-checks and routine results in your own app.
-
Dealers and installers
You look after cameras for many homes or small businesses.
-
Internet providers
You bundle cameras with service.
-
Property and rental software
Your software already knows the schedule: bookings, openings, visits.
Example photo
Talk to us about the Partner API.
The API isn’t open yet. Tell us what you’d build and a person will reply.