ZenMaid

ZenMaid is scheduling and business-management software for maid and house cleaning services - booking, calendar/dispatch, automated SMS and email communication, GPS-verified clock-in/out on a cleaner mobile app, online payments and invoicing, payroll, and reporting. ZenMaid has no public, self-service developer portal, no published REST/GraphQL API reference, and no OpenAPI specification of its own. Its only documented programmatic surface is a Zapier integration (triggers - New Customer Created, Appointment Booked, Appointment Cancelled, Appointment Updated, Contact Created/Updated, One-Time Service Created/Updated, Recurring Service Created/Updated/Cancelled, Invoice Created, Invoice Paid; actions - Create Appointment, Create Booking, Create Cleaner, Create Customer) built and maintained by ZenMaid against a private, undocumented backend API. No API keys, base URL, endpoint reference, payload schema, or SDK are published for third-party developers; the public GitHub organization (github.com/zenmaid) has no public repositories. This entry is documented as a stub because there is no public API to catalog.

ZenMaid is profiled on the APIs.io network. Tagged areas include Maid Service, Cleaning Business Software, Field Service Management, Scheduling, and Zapier.

ZenMaid’s developer surface includes documentation, engineering blog, and 6 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

8.7/100 minimal ▬ flat Agent 0/100 human only Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidOpenFree trialNo public API

0 APIs

Maid ServiceCleaning Business SoftwareField Service Management Scheduling Zapier

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 8.7/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 1.3 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 0.9 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 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/zenmaid/"><img src="https://apis.io/badge/zenmaid/card.svg" alt="ZenMaid 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
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

13 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
Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 16.7 — up to +16.7 composite points

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.

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/zenmaid/apis.yml: open an issue on github.com/api-evangelist/zenmaid 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 →

ZenMaid API pricing

Not yet checked against ZenMaid's own pricing page. Compiled by API Evangelist on 2026-07-04 from get.zenmaid.com/pricing; confirm before you rely on a figure.

Plan	Price
Starter paid	—
Pro paid	—
Pro Max paid	—

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Zenmaid Plans Pricing

3 plans

PLANS

Security Posture 1

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

Zenmaid Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

HelpCenter

HelpCenter

Commercial 1

Pricing, plans, and the legal terms of use

Plans

Plans

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Source (apis.yml)

aid: zenmaid
url: https://raw.githubusercontent.com/api-evangelist/zenmaid/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
x-api-posture-note: This entry is documented as a stub because there is no public API to catalog.
name: ZenMaid
kind: company
description: ZenMaid is scheduling and business-management software for maid and house cleaning services - booking, calendar/dispatch,
  automated SMS and email communication, GPS-verified clock-in/out on a cleaner mobile app, online payments and invoicing,
  payroll, and reporting. ZenMaid has no public, self-service developer portal, no published REST/GraphQL API reference, and
  no OpenAPI specification of its own. Its only documented programmatic surface is a Zapier integration (triggers - New Customer
  Created, Appointment Booked, Appointment Cancelled, Appointment Updated, Contact Created/Updated, One-Time Service Created/Updated,
  Recurring Service Created/Updated/Cancelled, Invoice Created, Invoice Paid; actions - Create Appointment, Create Booking,
  Create Cleaner, Create Customer) built and maintained by ZenMaid against a private, undocumented backend API. No API keys,
  base URL, endpoint reference, payload schema, or SDK are published for third-party developers; the public GitHub organization
  (github.com/zenmaid) has no public repositories. This entry is documented as a stub because there is no public API to catalog.
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: paid
  onboarding: open
  trial: true
  try_now: false
  public: false
  gated: private
  gated_source:
  - tag:No Public API
  label: Paid (free trial) · Open access
  confidence: low
  try_now_blocked_by: 'gated: private'
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zenmaid.png
tags:
- Maid Service
- Cleaning Business Software
- Field Service Management
- Scheduling
- Zapier
tags_raw:
- Maid Service
- Cleaning Business Software
- Field Service
- Scheduling
- Zapier
created: '2026-07-04'
modified: '2026-07-04'
specificationVersion: '0.23'
apis: []
common:
- type: DomainSecurity
  url: security/zenmaid-domain-security.yml
- type: Website
  url: https://www.zenmaid.com
- type: LinkedIn
  url: https://www.linkedin.com/company/zenmaid
- type: GitHubOrganization
  url: https://github.com/zenmaid
- type: Integrations
  url: https://get.zenmaid.com/zapier
- type: Documentation
  url: https://answers.zenmaid.com/en/collections/39144-integrations
- type: HelpCenter
  url: https://answers.zenmaid.com
- type: Plans
  url: plans/zenmaid-plans-pricing.yml
- type: Blog
  url: https://www.zenmaid.com/feed/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-tags-removed:
- No Public API

ZenMaid API — frequently asked questions

How much does the ZenMaid API cost?

APIs.io lists 3 pricing plans for ZenMaid, with each plan's price, limits and inclusions under Pricing on this page.

Is the ZenMaid API ready for AI agents?

ZenMaid has a Kin Score of 8.7 out of 100 (minimal) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.

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/zenmaid"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/zenmaid/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.