Devices and capabilities Beta

One action model for every device, sorted by risk

Beta. The Device SDK is live for design partners: Dopl issues your project's keys while the developer portal is being built, and @dopl/sdk is available on request. Agents that act for one signed in Dopl user can use the hosted MCP server instead.

Every device has a kind (glasses, phone, desktop, watch, home_hub, home_device, vehicle or robot), a vendor, model and firmware, and the adapter that reaches it. Instead of vendor APIs, each device publishes capability descriptors, and your agent calls capabilities by ID.

Capabilities and risk tiers

FamilyCapabilitiesDefault tierWhat it does
statestate.read, telemetry.read, presence.readT0Read device state, telemetry and whether the user is present
presentpresent.notify, present.display, present.speak, present.hapticT1Notify, show display blocks, speak, or buzz
askask.choice, ask.confirm, ask.textT1Ask a question and get the answer back
inputinput.utterance, input.tap, input.gesture, input.buttonT1Receive what the user says or does on the device
capturecapture.photo, capture.audio, capture.video_stream, capture.screenT2Capture from cameras, microphones or the screen
actact.set, act.media, act.navigateT3Reversible changes such as lights, media or navigation
actact.lockT4Locks
act.motionact.motion.move, act.motion.gripper, act.motion.vehicleT4Robot and vehicle motion

A scope can name one capability or a whole family, such as present.* or act.motion.*. A family scope counts at the highest tier among its members, so act.* is a T4 scope because it includes act.lock. Permissions and safety has the rules for each tier.

Descriptors

A descriptor states a capability's limits on that exact device, how fast it answers (realtime, interactive or deferred), its risk tier and the adapter version that added it. This is the Even Realities G2's question capability:

{
  "capability": "ask.choice",
  "limits": {
    "question_bytes": 120,
    "option_bytes": 40,
    "min_options": 2,
    "max_options": 4,
    "hold_s": 200
  },
  "latency_class": "interactive",
  "risk_tier": "T1",
  "since_adapter": "even_g2@0.1.0"
}

The Connect page checks these descriptors before the user pairs, and Dopl checks them again on every call: a capability the device does not publish fails with capability_unsupported rather than reaching the device. Each device page lists its capability matrix.