Docs Join alpha
Model

Screen-time

The gate between the kid's request and the parent's call. Approve, deny, or steer them elsewhere.

Screen-time is the gate between the kid's request for more device time and the parent's approval. The kid asks; your agent reviews; the answer comes back as approve, deny, or steer-them-somewhere-else. It's the most-asked parent-side flow, governed at the protocol layer.

Where you'll see this

In the wild: Triage screen-time (Build)

Shape

A worked example

Triage pending requests.

Shell
screentime.list_requests({ status: "pending" })
# Returns: [{ requestId, childId, durationMinutes, reason, ... }]
# For each request your agent reviews:
screentime.review_request({
requestId: "<requestId>",
action: "approve",
durationMinutes: 30
})
# action: "approve" | "deny". Denials confirm with parent first.

When to use it

Run a quick screen-time review whenever a kid requests, or surface it on a fixed cadence (morning + evening sweeps). The right answer often isn't yes-or-no: it's "yes if you finish the homework task," "yes for 15 minutes, then call me," or "let's switch from YouTube to the puzzle game I set up." Your agent can route to a more interesting alternative.

Common errors

Related tools

Roadmap for this noun

Triage screen-time Reward

Was this page helpful?