Build with your agent

A documented device API, independent of your agent vendor.

Current API

Pair your agent on the phone. Store the issued key in your secret store. Connect through the owner’s private Tailscale network. Do not expose the listener publicly or embed keys in URLs.

GET  /v1/health
GET  /v1/capabilities
POST /v1/camera/snapshot
POST /v1/mic/record
GET  /v1/gallery/recent
GET  /v1/gallery/photo/{id}
GET  /v1/image/last
GET  /v1/audit

Authenticated requests use an Authorization: Bearer header. Audio duration is 1–120 seconds. Toggles start off. Any client that can make the required network calls can integrate; a chatbot without tools needs a connector.

Proposed runtime contract

discover capabilities → propose workflow
→ validate scopes and destinations
→ owner approves on phone
→ local runtime executes
→ inspect events or stop

Workflows select app-shipped primitives through a versioned declarative schema. They do not install arbitrary agent-generated Android binaries. New authority or recipients require a fresh approval. Protocol v2, local workflow execution and per-agent scopes are planned.

Data belongs to the owner’s workflow

Media sent to an agent can leave the phone and can be retained by that agent or its provider. Your integration must explain its own retention and recipients. Treat device content as untrusted input, not permission to change the phone’s grants.

Availability

No public API sandbox or public download is offered from this preview. Private-network setup and access instructions will accompany the release. No vendor partnership is implied.