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 is listed with 4 APIs on the APIs.io network. Tagged areas include Company, Smart Home, IoT, Home Security, and Camera.

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

🌐 Visit website 📡 Profile data on GitHub

41.0/100 developing ▬ flat Agent 14/100 agent aware Front door AI 4/6 moderate Heartbeat 79/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

4 APIs 1 MCP Servers

Company Smart Home IoT Home Security Camera Consumer Electronics Home Automation Video Sensors Commerce

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 41.0/100 · developing

Contract Quality 0.0 / 21

Developer Ergonomics 8.5 / 17

Access Clarity 10.7 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 6.8 / 9

Regulatory Posture 6.8 / 15

Agent readiness — 14/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/wyze/"><img src="https://apis.io/badge/wyze/card.svg" alt="Wyze on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Developer Ergonomics scores 50.0 — up to +10.0 composite points Ask about this →
Contract Governance scores 18.2 — up to +9.8 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/wyze/apis.yml: open an issue on github.com/api-evangelist/wyze to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
IoT and Smart Home	undeclared	-	-	-
ONVIF Video Analytics (video surveillance, edge cameras, computer vision)	undeclared	-	-	-
ENERGY STAR Certified Products (appliances, electronics, data-center equipment, EV chargers, smart thermostats)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (shopify)

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 Server

Remote MCP server at www.wyze.com.

MCP SERVER

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Wyze

11 quoted statements, read from Wyze's own page on 2026-11-10.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Wyze

30 quoted statements, read from Wyze's own page on 2026-11-10.

PRIVACY

Compliance 1

Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.

Wyze

4 quoted statements, read from Wyze's own page on 2026-11-10.

COMPLIANCE

Eligibility 1

Who may sign up and where, quoted from its own terms.

Wyze

6 quoted statements, read from Wyze's own page on 2026-11-10.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Wyze

1 quoted statement, read from Wyze's own page on 2026-11-10.

AI PREFS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Wyze

2 quoted statements, read from Wyze's own page on 2026-11-10.

LICENSE

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

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

AIPreferences

AIPreferences

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Lifecycle

Lifecycle

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 7

Authentication, authorization, and security posture

DomainSecurity

Security

TrustCenter

Compliance

Authentication

OAuthScopes

VulnerabilityDisclosure

VulnerabilityDisclosure

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Support

Support

Community

Community

StatusPage

StatusPage

Commercial 5

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 5

Properties that don't map to a standard resource type

Hosts

Vendors

DataProcessing

Attestations

Eligibility

Source (apis.yml)

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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: gated
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
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.23'
created: '2026-08-02'
modified: '2026-08-02'
tags:
- Company
- Smart Home
- IoT
- Home Security
- Camera
- Consumer Electronics
- Home Automation
- Video
- Sensors
- Commerce
tags_raw:
- 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
common:
- type: Hosts
  url: hosts/wyze-hosts.yml
- type: Vendors
  url: vendors/wyze-vendors.yml
- 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: 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: VulnerabilityDisclosure
  url: security/wyze-vulnerability-disclosure.yml
- type: UsageTerms
  url: terms/wyze-terms-of-service.yml
- type: DataProcessing
  url: privacy/wyze-privacy-policy.yml
- type: Attestations
  url: compliance/wyze-compliance.yml
- type: Eligibility
  url: eligibility/wyze-eligibility.yml
- type: AIPreferences
  url: ai-preferences/wyze-ai-preferences.yml
- type: DataLicense
  url: data-license/wyze-data-license.yml
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
  - IoT
  - Devices
  - Authentication
  tags_raw:
  - 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:
  - MCP
  - Commerce
  - Agents
  tags_raw:
  - Model Context Protocol
  - Commerce
  - Agents
  properties:
  - type: MCPServer
    url: mcp/wyze-mcp.yml
  - type: LLMsTxt
    url: llms/wyze-llms.txt
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: storefront-mcp
- 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:
  - MCP
  - Commerce
  - Order
  tags_raw:
  - Model Context Protocol
  - Commerce
  - Orders
  properties:
  - type: MCPServer
    url: mcp/wyze-mcp.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: customer-account-mcp
- 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
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
x-enrichment:
  date: '2026-10-20'
  status: nochange
  artifacts_added: 0
  pass: local-v5
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: Wyze's cloud API (api.wyzecam.com) is usable only with a personal API Key issued to device owners at developer-api-console.wyze.com,
    and Wyze publishes no OpenAPI or public reference for it.
  evidence:
  - url: https://www.wyze.com
    status: 200
  checked: '2026-10-20'

Wyze API — frequently asked questions

Does Wyze have an API?

Yes. APIs.io lists 4 APIs from Wyze, including Wyze Developer API, Wyze Storefront MCP Server and Wyze Customer Account MCP Server, and 1 more.

How do I authenticate with the Wyze API?

Wyze documents its authentication (apiKey/http/oauth2/openIdConnect · 5 schemes). The details are profiled on APIs.io as Wyze Authentication.

Does Wyze have an MCP server?

Yes. APIs.io lists 1 MCP server for Wyze: Remote MCP server at www.wyze.com.

Is the Wyze API ready for AI agents?

Wyze has a Kin Score of 41.0 out of 100 (developing) and an Agent Readiness score of 13.8 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/wyze"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/wyze/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/wyze/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.