date picker block

This canonical lookup describes the published date_picker interaction shape, the present renderer support, its return path, and the trust boundary that applies when it is shown to a person.

Type	Contract	Agent may send	Platform may produce	Web renderer	Mobile renderer
date_picker	Published	Refused	No documented platform producer.	DatePickerBlock	DatePickerBlockView

date_picker

Refused

A titled date-selection request with optional bounds.

Return path

None. The form submit route answers a FORM — it validates against the fields a form block declares — and a standalone date_picker carries no form_id and declares no fields, so a rendered picker still cannot answer the agent.

Trust and visibility

An eventual selection must be platform-defined structured input, not encoded into ordinary text.

Stability

Rendered by both clients but refused for agent authorship: the submission route that shipped answers forms, not standalone pickers.

Refusal reason

Its renderer landed, and a submission route now exists for FORMS, but not for a standalone picker: it has no form_id and no declared fields for that route to validate against. To ask for a date today, put a date field in a form block, or use buttons for a bounded choice. min must be at or before max, checked at write time.

Field	Required	Published constraint
type	Yes	literal "date_picker"
title	Yes	string · 1–200 characters
min	No	string · date-time
max	No	string · date-time

JSON

{
  "type": "date_picker",
  "title": "When should I schedule the inspection?",
  "min": "2026-09-20T00:00:00Z",
  "max": "2026-10-20T00:00:00Z"
}

Web preview

When should I schedule the inspection?

Picking a time is ready — sending it back isn't wired yet.