Wyze

Wyze Labs, Inc. is a Kirkland, Washington consumer smart-home company founded in 2017 by former Amazon employees, known for value-priced connected hardware: indoor and outdoor security cameras, video doorbells, smart locks, contact and motion sensors, plugs, bulbs and light strips, robot vacuums, thermostats, sprinkler controllers, scales and wearables. Devices are operated through the Wyze app and backed by cloud services sold as subscriptions (Cam Plus, Cam Unlimited, Wyze Home Monitoring). Wyze does not publish a general-purpose public developer platform, but it does operate a first-party Developer API Console at developer-api-console.wyze.com that issues a personal API Key / Key ID pair so owners can authenticate against the Wyze cloud API (auth-prod.api.wyze.com and api.wyzecam.com) from Home Assistant, Homebridge and other third-party integrations. Its Shopify-hosted storefront additionally exposes agent-facing commerce surfaces: a published llms.txt/agents.md, a Universal Commerce Protocol (UCP) discovery document, and two live Model Context Protocol servers.

Wyze publishes 4 APIs on the APIs.io network. Tagged areas include Company, Smart Home, Internet of Things, Home Security, and Cameras.

Wyze’s developer surface includes documentation, getting-started guide, support, engineering blog, pricing, authentication, and 22 more developer resources.

37.8/100 thin ▬ flat Agent 27/100 agent aware Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
4 APIs 1 MCP Servers
CompanySmart HomeInternet of ThingsHome SecurityCamerasConsumer ElectronicsHome AutomationVideoSensorsCommerce

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 37.8/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 10.9 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 4.1 / 13
Governance 1.5 / 12
Discoverability 9.3 / 10
Agent readiness — 27/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/wyze: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Wyze Developer API

The first-party Wyze cloud API reached with a personal API Key and Key ID generated from the Wyze Developer API Console. Authentication posts credentials to auth-prod.api.wyze.c...

Wyze Storefront MCP Server

A live, anonymously reachable Model Context Protocol server on the Wyze storefront host that lets agents search the Wyze product catalog, read and update a cart, look up product...

Wyze Customer Account MCP Server

A live Model Context Protocol server on account.wyze.com exposing customer order-status lookup, store-credit balances and return requests. tools/list answers anonymously; the to...

Wyze UCP Commerce Endpoint

The Universal Commerce Protocol (UCP) merchant surface published by the Wyze storefront. The /.well-known/ucp discovery document declares supported UCP versions, the dev.ucp.sho...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

wyze-mcp.yml

MCP SERVER

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wyze Authentication

apiKey/http/oauth2/openIdConnect · 5 schemes

SECURITY

Wyze Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wyze Vulnerability Disclosure

Bugcrowd · contact published

SECURITY

Wyze Trust Center

ioXt Alliance certification, Google MASA (Mobile Application Security Assessment), UL / FCC / Energy Star

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Wyze Scopes

4 scopes · authorizationCode/refreshToken

4 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: wyze
name: Wyze
description: 'Wyze Labs, Inc. is a Kirkland, Washington consumer smart-home company founded in 2017 by former Amazon employees,
  known for value-priced connected hardware: indoor and outdoor security cameras, video doorbells, smart locks, contact and
  motion sensors, plugs, bulbs and light strips, robot vacuums, thermostats, sprinkler controllers, scales and wearables.
  Devices are operated through the Wyze app and backed by cloud services sold as subscriptions (Cam Plus, Cam Unlimited, Wyze
  Home Monitoring). Wyze does not publish a general-purpose public developer platform, but it does operate a first-party Developer
  API Console at developer-api-console.wyze.com that issues a personal API Key / Key ID pair so owners can authenticate against
  the Wyze cloud API (auth-prod.api.wyze.com and api.wyzecam.com) from Home Assistant, Homebridge and other third-party integrations.
  Its Shopify-hosted storefront additionally exposes agent-facing commerce surfaces: a published llms.txt/agents.md, a Universal
  Commerce Protocol (UCP) discovery document, and two live Model Context Protocol servers.'
url: https://raw.githubusercontent.com/api-evangelist/wyze/refs/heads/main/apis.yml
image: https://www.wyze.com/cdn/shop/files/Wyze_Ecosystem_Share.png?v=1781726389
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.20'
created: '2026-08-02'
modified: '2026-08-02'
tags:
- Company
- Smart Home
- Internet of Things
- Home Security
- Cameras
- Consumer Electronics
- Home Automation
- Video
- Sensors
- Commerce
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: wyze:developer-api
  name: Wyze Developer API
  description: The first-party Wyze cloud API reached with a personal API Key and Key ID generated from the Wyze Developer
    API Console. Authentication posts credentials to auth-prod.api.wyze.com to exchange the key pair for an access token (valid
    2 days) and refresh token (valid 30 days), which are then used against the api.wyzecam.com application endpoints that
    back the Wyze app. Wyze publishes the key-issuance and login/refresh flow in its support documentation but does not publish
    a full endpoint reference or a machine-readable OpenAPI description.
  humanURL: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key
  baseURL: https://api.wyzecam.com
  tags:
  - Smart Home
  - Internet of Things
  - Devices
  - Authentication
  properties:
  - type: Documentation
    url: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key
  - type: DeveloperPortal
    url: https://developer-api-console.wyze.com/
  - type: Authentication
    url: authentication/wyze-authentication.yml
- aid: wyze:storefront-mcp
  name: Wyze Storefront MCP Server
  description: A live, anonymously reachable Model Context Protocol server on the Wyze storefront host that lets agents search
    the Wyze product catalog, read and update a cart, look up product detail, and query store policies and FAQs. The tool
    list and per-tool JSON input schemas were returned by an unauthenticated MCP tools/list call and are captured verbatim
    in mcp/.
  humanURL: https://www.wyze.com/llms.txt
  baseURL: https://www.wyze.com/api/mcp
  tags:
  - Model Context Protocol
  - Commerce
  - Agents
  properties:
  - type: MCPServer
    url: mcp/wyze-mcp.yml
  - type: LLMsTxt
    url: llms/wyze-llms.txt
- aid: wyze:customer-account-mcp
  name: Wyze Customer Account MCP Server
  description: A live Model Context Protocol server on account.wyze.com exposing customer order-status lookup, store-credit
    balances and return requests. tools/list answers anonymously; the tools themselves operate on a logged-in customer session.
    The tool list and input schemas are captured verbatim in mcp/.
  humanURL: https://www.wyze.com/llms.txt
  baseURL: https://account.wyze.com/customer/api/mcp
  tags:
  - Model Context Protocol
  - Commerce
  - Orders
  properties:
  - type: MCPServer
    url: mcp/wyze-mcp.yml
- aid: wyze:ucp
  name: Wyze UCP Commerce Endpoint
  description: The Universal Commerce Protocol (UCP) merchant surface published by the Wyze storefront. The /.well-known/ucp
    discovery document declares supported UCP versions, the dev.ucp.shopping MCP service endpoint, cart/checkout/fulfillment/discount/
    catalog capabilities and the Google Pay, Shopify Card and Shop Pay payment handlers. The UCP MCP endpoint itself rejects
    anonymous tools/list with a required agent-profile error, so its tool schemas are gated; the tool names are the ones published
    in llms.txt.
  humanURL: https://www.wyze.com/llms.txt
  baseURL: https://www.wyze.com/api/ucp/mcp
  tags:
  - Commerce
  - Agents
  - Universal Commerce Protocol
  properties:
  - type: WellKnown
    url: well-known/wyze-ucp.json
common:
- type: DomainSecurity
  url: security/wyze-domain-security.yml
- type: Website
  url: https://www.wyze.com
- type: DeveloperPortal
  url: https://developer-api-console.wyze.com/
- type: Documentation
  url: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key
- type: GettingStarted
  url: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key
- type: Login
  url: https://developer-api-console.wyze.com/#/apikey/view
- type: Support
  url: https://support.wyze.com/hc/en-us
- type: Community
  url: https://forums.wyze.com/
- type: Blog
  url: https://www.wyze.com/blogs/news
- type: GitHubOrganization
  url: https://github.com/wyzelabs-inc
- type: Pricing
  url: https://www.wyze.com/pages/service-plans
- type: TermsOfService
  url: https://www.wyze.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://www.wyze.com/policies/privacy-policy
- type: StatusPage
  url: https://support.wyze.com/hc/en-us/articles/360015979872-Service-Status-Known-Issues
- type: Security
  url: https://www.wyze.com/pages/wyzes-vulnerability-disclosure
- type: TrustCenter
  url: security/wyze-trust-center.yml
- type: Compliance
  url: https://www.wyze.com/pages/security-trust
- type: LLMsTxt
  url: llms/wyze-llms.txt
- type: MCPServer
  url: mcp/wyze-mcp.yml
- type: WellKnown
  url: well-known/wyze-well-known.yml
- type: Packages
  url: packages/wyze-packages.yml
- type: Authentication
  url: authentication/wyze-authentication.yml
- type: OAuthScopes
  url: scopes/wyze-scopes.yml
- type: Conventions
  url: conventions/wyze-conventions.yml
- type: Lifecycle
  url: lifecycle/wyze-lifecycle.yml
- type: Conformance
  url: conformance/wyze-conformance.yml
- type: ErrorCatalog
  url: errors/wyze-problem-types.yml
- type: VulnerabilityDisclosure
  url: security/wyze-vulnerability-disclosure.yml
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 19
  pass: local-v1