@portpowered/reference-data 0.0.0-stage → 0.4.1

package/generated/public/docs/for-ai/capability-interfaces/air-quality-sensor/1.0.md

@@ -0,0 +1,17 @@
+# air-quality-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/air-quality-sensor`
+
+Air quality reports the air-quality index measured by a device. Use the reading to understand conditions in a room and decide when to run ventilation or another automation.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/air-quality-sensor/1.0.yaml)
+
+## Messages
+
+- [get-air-quality](/docs/references/capability-interfaces/air-quality-sensor/1.0/messages/get-air-quality.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [air-quality-index](/docs/references/capability-interfaces/air-quality-sensor/1.0/attributes/air-quality-index.yaml)

package/generated/public/docs/for-ai/capability-interfaces/alarm/1.0.md

@@ -0,0 +1,19 @@
+# alarm 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/alarm`
+
+Alarms ring, silence, or test a device's siren when supported. Read the alarm state to see whether the siren is active.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/alarm/1.0.yaml)
+
+## Messages
+
+- [ring-alarm](/docs/references/capability-interfaces/alarm/1.0/messages/ring-alarm.yaml) (in): Sound the endpoint alarm. Requires an endpoint with an alarm actuator.
+- [silence-alarm](/docs/references/capability-interfaces/alarm/1.0/messages/silence-alarm.yaml) (in): Use this exact payload schema.
+- [test-alarm](/docs/references/capability-interfaces/alarm/1.0/messages/test-alarm.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [alarm-state](/docs/references/capability-interfaces/alarm/1.0/attributes/alarm-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/application-launcher/1.0.md

@@ -0,0 +1,19 @@
+# application-launcher 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/application-launcher`
+
+Application launchers start and stop applications on a connected device. Check the available applications and the current selection before choosing what to launch.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/application-launcher/1.0.yaml)
+
+## Messages
+
+- [launch-application](/docs/references/capability-interfaces/application-launcher/1.0/messages/launch-application.yaml) (in): Use this exact payload schema.
+- [stop-application](/docs/references/capability-interfaces/application-launcher/1.0/messages/stop-application.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [application-list](/docs/references/capability-interfaces/application-launcher/1.0/attributes/application-list.yaml)
+- [current-application](/docs/references/capability-interfaces/application-launcher/1.0/attributes/current-application.yaml)

package/generated/public/docs/for-ai/capability-interfaces/authorization/1.0.md

@@ -0,0 +1,18 @@
+# authorization 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/authorization`
+
+Authorization connects an integration to an account and keeps its credentials up to date. Use token refresh and authorization reports to follow the connection as it changes.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/authorization/1.0.yaml)
+
+## Messages
+
+- [authorization-established](/docs/references/capability-interfaces/authorization/1.0/messages/authorization-established.yaml) (out): The authorization established message is sent to a plugin to indicate that the plugin has been installed and authorized for a principal
+- [authorization-update-report](/docs/references/capability-interfaces/authorization/1.0/messages/authorization-update-report.yaml) (out): Use this exact payload schema.
+- [refresh-tokens](/docs/references/capability-interfaces/authorization/1.0/messages/refresh-tokens.yaml) (in): Use this exact payload schema.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/barrier-control/1.0.md

@@ -0,0 +1,20 @@
+# barrier-control 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/barrier-control`
+
+Barrier control opens, closes, or positions a connected barrier. Read its position and state to check a garage door or gate before sending the next command.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/barrier-control/1.0.yaml)
+
+## Messages
+
+- [close](/docs/references/capability-interfaces/barrier-control/1.0/messages/close.yaml) (in): Use this exact payload schema.
+- [go-to-position](/docs/references/capability-interfaces/barrier-control/1.0/messages/go-to-position.yaml) (in): Use this exact payload schema.
+- [open](/docs/references/capability-interfaces/barrier-control/1.0/messages/open.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [barrier-position](/docs/references/capability-interfaces/barrier-control/1.0/attributes/barrier-position.yaml)
+- [barrier-state](/docs/references/capability-interfaces/barrier-control/1.0/attributes/barrier-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/battery/1.0.md

@@ -0,0 +1,16 @@
+# battery 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/battery`
+
+Battery reports a connected device's charge level and battery health. Use it to show when a device needs charging or a replacement battery.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/battery/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [battery](/docs/references/capability-interfaces/battery/1.0/attributes/battery.yaml)

package/generated/public/docs/for-ai/capability-interfaces/brightness/1.0.md

@@ -0,0 +1,17 @@
+# brightness 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/brightness`
+
+Brightness sets how bright a connected device should be and reports its current level. Use it to dim a light for the evening or restore a brighter setting for work.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/brightness/1.0.yaml)
+
+## Messages
+
+- [set-brightness](/docs/references/capability-interfaces/brightness/1.0/messages/set-brightness.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [brightness](/docs/references/capability-interfaces/brightness/1.0/attributes/brightness.yaml)

package/generated/public/docs/for-ai/capability-interfaces/calendar-provider/1.0.md

@@ -0,0 +1,17 @@
+# calendar-provider 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/calendar-provider`
+
+Calendar providers list events from a connected calendar. Use the returned events to give an assistant schedule context or build an automation around an upcoming appointment.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/calendar-provider/1.0.yaml)
+
+## Messages
+
+- [list-events](/docs/references/capability-interfaces/calendar-provider/1.0/messages/list-events.yaml) (in): Request to list events from a calendar provider
+- [list-events-response](/docs/references/capability-interfaces/calendar-provider/1.0/messages/list-events-response.yaml) (out): Response containing a list of events from a calendar provider
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/camera/1.0.md

@@ -0,0 +1,21 @@
+# camera 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/camera`
+
+Cameras provide streaming, event images, and camera controls. Start a stream, adjust pan and tilt when supported, or configure motion detection for the view you need.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/camera/1.0.yaml)
+
+## Messages
+
+- [get-event-image](/docs/references/capability-interfaces/camera/1.0/messages/get-event-image.yaml) (in): Use this exact payload schema.
+- [ptz-control](/docs/references/capability-interfaces/camera/1.0/messages/ptz-control.yaml) (in): Use this exact payload schema.
+- [set-motion-detection](/docs/references/capability-interfaces/camera/1.0/messages/set-motion-detection.yaml) (in): Use this exact payload schema.
+- [start-streaming](/docs/references/capability-interfaces/camera/1.0/messages/start-streaming.yaml) (in): Use this exact payload schema.
+- [stop-streaming](/docs/references/capability-interfaces/camera/1.0/messages/stop-streaming.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [motion-detection-enabled](/docs/references/capability-interfaces/camera/1.0/attributes/motion-detection-enabled.yaml)

package/generated/public/docs/for-ai/capability-interfaces/carbon-dioxide-concentration-sensor/1.0.md

@@ -0,0 +1,18 @@
+# carbon-dioxide-concentration-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/carbon-dioxide-concentration-sensor`
+
+Carbon dioxide measurements report the concentration observed by a sensor, including its minimum and maximum readings. Use them to track changes in indoor conditions over time.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/carbon-dioxide-concentration-sensor/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [max-measured-value](/docs/references/capability-interfaces/carbon-dioxide-concentration-sensor/1.0/attributes/max-measured-value.yaml)
+- [measured-value](/docs/references/capability-interfaces/carbon-dioxide-concentration-sensor/1.0/attributes/measured-value.yaml)
+- [min-measured-value](/docs/references/capability-interfaces/carbon-dioxide-concentration-sensor/1.0/attributes/min-measured-value.yaml)

package/generated/public/docs/for-ai/capability-interfaces/carbon-monoxide-concentration-sensor/1.0.md

@@ -0,0 +1,18 @@
+# carbon-monoxide-concentration-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/carbon-monoxide-concentration-sensor`
+
+Carbon monoxide measurements report the concentration observed by a sensor, including its minimum and maximum readings. Use the reported values as input to monitoring and notification flows.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/carbon-monoxide-concentration-sensor/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [max-measured-value](/docs/references/capability-interfaces/carbon-monoxide-concentration-sensor/1.0/attributes/max-measured-value.yaml)
+- [measured-value](/docs/references/capability-interfaces/carbon-monoxide-concentration-sensor/1.0/attributes/measured-value.yaml)
+- [min-measured-value](/docs/references/capability-interfaces/carbon-monoxide-concentration-sensor/1.0/attributes/min-measured-value.yaml)

package/generated/public/docs/for-ai/capability-interfaces/channel/1.0.md

@@ -0,0 +1,18 @@
+# channel 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/channel`
+
+Channel controls select a channel or skip between channels on a connected device. Read the current channel to keep the interface in step with what is playing.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/channel/1.0.yaml)
+
+## Messages
+
+- [change-channel](/docs/references/capability-interfaces/channel/1.0/messages/change-channel.yaml) (in): Use this exact payload schema.
+- [skip-channels](/docs/references/capability-interfaces/channel/1.0/messages/skip-channels.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [channel](/docs/references/capability-interfaces/channel/1.0/attributes/channel.yaml)

package/generated/public/docs/for-ai/capability-interfaces/cleaning-mode/1.0.md

@@ -0,0 +1,19 @@
+# cleaning-mode 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/cleaning-mode`
+
+Cleaning types, suction levels and water flows the robot supports, refreshed on every discovery. set-cleaning-mode values outside these lists are rejected before dispatch.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/cleaning-mode/1.0.yaml)
+
+## Messages
+
+- [set-cleaning-mode](/docs/references/capability-interfaces/cleaning-mode/1.0/messages/set-cleaning-mode.yaml) (in): Set whether the robot vacuums, mops or does both, optionally with a suction level and water flow. Omitted levels keep the current non-off value. Values outside the configured supported lists are rejected with 422 before dispatch.
+
+## State attributes
+
+- [cleaning-mode](/docs/references/capability-interfaces/cleaning-mode/1.0/attributes/cleaning-mode.yaml)
+- [suction-level](/docs/references/capability-interfaces/cleaning-mode/1.0/attributes/suction-level.yaml)
+- [water-flow](/docs/references/capability-interfaces/cleaning-mode/1.0/attributes/water-flow.yaml)

package/generated/public/docs/for-ai/capability-interfaces/color/1.0.md

@@ -0,0 +1,17 @@
+# color 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/color`
+
+Color sets and reports the color of a connected device. Use it to coordinate lighting for a scene or let an assistant choose a new color.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/color/1.0.yaml)
+
+## Messages
+
+- [set-color](/docs/references/capability-interfaces/color/1.0/messages/set-color.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [color](/docs/references/capability-interfaces/color/1.0/attributes/color.yaml)

package/generated/public/docs/for-ai/capability-interfaces/color-temperature/1.0.md

@@ -0,0 +1,19 @@
+# color-temperature 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/color-temperature`
+
+Color temperature adjusts a light between warmer and cooler tones. Set a temperature directly or increase and decrease it, then read the reported value in kelvin.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/color-temperature/1.0.yaml)
+
+## Messages
+
+- [decrease-color-temperature](/docs/references/capability-interfaces/color-temperature/1.0/messages/decrease-color-temperature.yaml) (in): Use this exact payload schema.
+- [increase-color-temperature](/docs/references/capability-interfaces/color-temperature/1.0/messages/increase-color-temperature.yaml) (in): Use this exact payload schema.
+- [set-color-temperature](/docs/references/capability-interfaces/color-temperature/1.0/messages/set-color-temperature.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [color-temperature-in-kelvin](/docs/references/capability-interfaces/color-temperature/1.0/attributes/color-temperature-in-kelvin.yaml)

package/generated/public/docs/for-ai/capability-interfaces/connectivity/1.0.md

@@ -0,0 +1,18 @@
+# connectivity 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/connectivity`
+
+Connectivity tells you whether a connected device is reachable. Use its reported state to explain an unavailable device or decide when to retry an action.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/connectivity/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [network-throughput](/docs/references/capability-interfaces/connectivity/1.0/attributes/network-throughput.yaml)
+- [radio-diagnostics](/docs/references/capability-interfaces/connectivity/1.0/attributes/radio-diagnostics.yaml)
+- [reachability](/docs/references/capability-interfaces/connectivity/1.0/attributes/reachability.yaml)

package/generated/public/docs/for-ai/capability-interfaces/contact-sensor/1.0.md

@@ -0,0 +1,16 @@
+# contact-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/contact-sensor`
+
+Contact sensors tell you whether a door, window, or gate is open or closed. Use their reported state to check an entryway or trigger an automation when something is left open.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/contact-sensor/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [detection-state](/docs/references/capability-interfaces/contact-sensor/1.0/attributes/detection-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/contacts-provider/1.0.md

@@ -0,0 +1,17 @@
+# contacts-provider 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/contacts-provider`
+
+Contacts providers list contacts from a connected account. Use the returned records to give an assistant the contact information available to your integration.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/contacts-provider/1.0.yaml)
+
+## Messages
+
+- [list-contacts](/docs/references/capability-interfaces/contacts-provider/1.0/messages/list-contacts.yaml) (in): Request to list contacts from a contacts provider
+- [list-contacts-response](/docs/references/capability-interfaces/contacts-provider/1.0/messages/list-contacts-response.yaml) (out): Response containing a list of contacts from a contacts provider
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/content-launcher/1.0.md

@@ -0,0 +1,17 @@
+# content-launcher 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/content-launcher`
+
+Content launchers open content or a URL on a connected device. Use them to send a selected item to a screen or start the content a customer asked for.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/content-launcher/1.0.yaml)
+
+## Messages
+
+- [launch-content](/docs/references/capability-interfaces/content-launcher/1.0/messages/launch-content.yaml) (in): Use this exact payload schema.
+- [launch-url](/docs/references/capability-interfaces/content-launcher/1.0/messages/launch-url.yaml) (in): Use this exact payload schema.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/control-route-groups-provider/1.0.md

@@ -0,0 +1,17 @@
+# control-route-groups-provider 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/control-route-groups-provider`
+
+Control route groups organize several routes into a group. Create a group with its member routes or delete a group your integration no longer needs.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/control-route-groups-provider/1.0.yaml)
+
+## Messages
+
+- [create-group](/docs/references/capability-interfaces/control-route-groups-provider/1.0/messages/create-group.yaml) (in): Request to delete a group based on its group ID. 
+- [delete-group](/docs/references/capability-interfaces/control-route-groups-provider/1.0/messages/delete-group.yaml) (in): Request to delete a group based on its group ID. 
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/control-routes-provider/1.0.md

@@ -0,0 +1,22 @@
+# control-routes-provider 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/control-routes-provider`
+
+Control route providers carry dispatch results and attribute reports between an integration and Port OS. Use them to report acknowledgements, errors, deferred responses, and batches of messages.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/control-routes-provider/1.0.yaml)
+
+## Messages
+
+- [acknowledged](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/acknowledged.yaml) (in): Response to acknowledge a message was dispatched, it confirms that a message was dispatched, but not necessarily that it did anything.  Consider this to happen on any infrared based device (TV remotes), where no ack is feasible.
+- [attribute-report](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/attribute-report.yaml) (in): Response to report attributes of a control route
+- [batch-message-dispatch](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/batch-message-dispatch.yaml) (in): Request to dispatch a batch of messages to a control route sent from port OS to the control routes provider
+- [deferred-response](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/deferred-response.yaml) (in): Response to acknowledge a message was dispatched, it confirms that a message was dispatched, and that a confirmation of the result will be sent later on.  We generate this message when the device is expected to respond some time later on, and we need to wait for the result.  For the default behavior, we expect to wait up to a minute to handle low powered devices.
+- [error-dispatch](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/error-dispatch.yaml) (in): Response to acknowledge a message was dispatched, it confirms that a message was dispatched, and that the result was not successful.
+- [report-attributes](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/report-attributes.yaml) (in): Request to report attributes of a control route sent from port OS to the control routes provider
+- [successful-dispatch](/docs/references/capability-interfaces/control-routes-provider/1.0/messages/successful-dispatch.yaml) (in): Response to acknowledge a message was successfully dispatched, it confirms that a message was dispatched, and that the result was successful.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/cooktop/1.0.md

@@ -0,0 +1,16 @@
+# cooktop 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/cooktop`
+
+Cooktops report their operational state. Use that state to show what the appliance is doing or supply context to an automation.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/cooktop/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [operational-state](/docs/references/capability-interfaces/cooktop/1.0/attributes/operational-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/dishwasher/1.0.md

@@ -0,0 +1,16 @@
+# dishwasher 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/dishwasher`
+
+Dishwashers report their operational state. Use it to keep an appliance dashboard up to date or react when a reported state changes.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/dishwasher/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [operational-state](/docs/references/capability-interfaces/dishwasher/1.0/attributes/operational-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/doorbell/1.0.md

@@ -0,0 +1,16 @@
+# doorbell 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/doorbell`
+
+Doorbells emit a chime event. Use that event to start a notification or another flow when someone rings the bell.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/doorbell/1.0.yaml)
+
+## Messages
+
+- [chime](/docs/references/capability-interfaces/doorbell/1.0/messages/chime.yaml) (out): A distinct doorbell press. A chime does not imply a door was opened.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/electrical-conductivity-sensor/1.0.md

@@ -0,0 +1,16 @@
+# electrical-conductivity-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/electrical-conductivity-sensor`
+
+Electrical conductivity measurements report a sensor reading. Use the value and its declared units when displaying or comparing measurements.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/electrical-conductivity-sensor/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [measured-value](/docs/references/capability-interfaces/electrical-conductivity-sensor/1.0/attributes/measured-value.yaml)

package/generated/public/docs/for-ai/capability-interfaces/embedding-generation/1.0.md

@@ -0,0 +1,17 @@
+# embedding-generation 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/embedding-generation`
+
+Embedding generation turns an input into an embedding and returns its URI. Use the result in integrations that work with vector representations of content.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/embedding-generation/1.0.yaml)
+
+## Messages
+
+- [embedding-uri](/docs/references/capability-interfaces/embedding-generation/1.0/messages/embedding-uri.yaml) (out): Use this exact payload schema.
+- [generate-embedding](/docs/references/capability-interfaces/embedding-generation/1.0/messages/generate-embedding.yaml) (in): Use this exact payload schema.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/endpoint-registry/1.0.md

@@ -0,0 +1,16 @@
+# endpoint-registry 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/endpoint-registry`
+
+Configuration for Port OS endpoint registry lifecycle notifications
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/endpoint-registry/1.0.yaml)
+
+## Messages
+
+- [endpoint-updated](/docs/references/capability-interfaces/endpoint-registry/1.0/messages/endpoint-updated.yaml) (out): Port OS emitted a durable endpoint metadata or enablement change. Delivery is best effort.
+
+## State attributes
+

package/generated/public/docs/for-ai/capability-interfaces/equalizer/1.0.md

@@ -0,0 +1,20 @@
+# equalizer 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/equalizer`
+
+Equalizers adjust audio bands and select an equalizer mode. Read the current bands and mode to keep an audio control in step with the device.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/equalizer/1.0.yaml)
+
+## Messages
+
+- [adjust-bands](/docs/references/capability-interfaces/equalizer/1.0/messages/adjust-bands.yaml) (in): Use this exact payload schema.
+- [set-bands](/docs/references/capability-interfaces/equalizer/1.0/messages/set-bands.yaml) (in): Use this exact payload schema.
+- [set-mode](/docs/references/capability-interfaces/equalizer/1.0/messages/set-mode.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [bands](/docs/references/capability-interfaces/equalizer/1.0/attributes/bands.yaml)
+- [mode](/docs/references/capability-interfaces/equalizer/1.0/attributes/mode.yaml)

package/generated/public/docs/for-ai/capability-interfaces/event-detection-sensor/1.0.md

@@ -0,0 +1,17 @@
+# event-detection-sensor 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/event-detection-sensor`
+
+Event detection sensors report human presence and emit person-detected events. Use them to give an automation context about activity in a monitored area.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/event-detection-sensor/1.0.yaml)
+
+## Messages
+
+- [person-detected](/docs/references/capability-interfaces/event-detection-sensor/1.0/messages/person-detected.yaml) (out): A distinct person detection occurrence, independent of cached presence state.
+
+## State attributes
+
+- [human-presence-detection-state](/docs/references/capability-interfaces/event-detection-sensor/1.0/attributes/human-presence-detection-state.yaml)

package/generated/public/docs/for-ai/capability-interfaces/extractor-hood/1.0.md

@@ -0,0 +1,16 @@
+# extractor-hood 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/extractor-hood`
+
+Extractor hoods report their fan speed. Use that state to show the current ventilation setting alongside other kitchen appliances.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/extractor-hood/1.0.yaml)
+
+## Messages
+
+
+## State attributes
+
+- [fan-speed](/docs/references/capability-interfaces/extractor-hood/1.0/attributes/fan-speed.yaml)

package/generated/public/docs/for-ai/capability-interfaces/fan-control/1.0.md

@@ -0,0 +1,19 @@
+# fan-control 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/fan-control`
+
+Fan control selects a fan mode and speed. Read the reported settings to check how a fan is running before changing them.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/fan-control/1.0.yaml)
+
+## Messages
+
+- [set-mode](/docs/references/capability-interfaces/fan-control/1.0/messages/set-mode.yaml) (in): Use this exact payload schema.
+- [set-speed](/docs/references/capability-interfaces/fan-control/1.0/messages/set-speed.yaml) (in): Use this exact payload schema.
+
+## State attributes
+
+- [fan-mode](/docs/references/capability-interfaces/fan-control/1.0/attributes/fan-mode.yaml)
+- [fan-speed](/docs/references/capability-interfaces/fan-control/1.0/attributes/fan-speed.yaml)

package/generated/public/docs/for-ai/capability-interfaces/filesystem-provider/1.0.md

@@ -0,0 +1,25 @@
+# filesystem-provider 1.0
+
+Namespace: `port1/systems/zero/capability-interfaces/filesystem-provider`
+
+Filesystem providers list folders and photo albums and expose file download, upload, and deletion. Check the provider's supported commands before requesting an operation.
+
+Read scopes: endpoint:read. Inbound control scope: message:send. Resource permission is also required.
+
+[Complete YAML](/docs/references/capability-interfaces/filesystem-provider/1.0.yaml)
+
+## Messages
+
+- [delete-file](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/delete-file.yaml) (in): Delete file.
+- [delete-file-response](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/delete-file-response.yaml) (out): The provider confirmed deletion of the requested file.
+- [download-file](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/download-file.yaml) (in): Download file.
+- [download-file-response](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/download-file-response.yaml) (out): Download file response.
+- [list-albums](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/list-albums.yaml) (in): Request to list photo albums from a filesystem provider
+- [list-albums-response](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/list-albums-response.yaml) (out): Response containing a list of photo albums from a filesystem provider
+- [list-folder](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/list-folder.yaml) (in): Request to list files and folders from a filesystem provider
+- [list-folder-response](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/list-folder-response.yaml) (out): Response containing a list of files and folders from a filesystem provider
+- [upload-file](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/upload-file.yaml) (in): Upload file.
+- [upload-file-response](/docs/references/capability-interfaces/filesystem-provider/1.0/messages/upload-file-response.yaml) (out): Upload file response.
+
+## State attributes
+