Clockwise

Clockwise was an AI-powered calendar optimization platform that helped individuals, teams, and organizations protect focus time, reduce meeting overload, and coordinate scheduling intelligently. The platform provided REST APIs for managing focus time blocks, meeting preferences, smart scheduling links, and team calendar coordination. Clockwise was acquired by Salesforce and shut down on March 27, 2026.

Clockwise is listed with 1 API on the APIs.io network: REST API. Tagged areas include Calendar, Artificial Intelligence, Scheduling, Focus Time, and Productivity.

The Clockwise catalog on APIs.io includes 1 JSON-LD context.

Clockwise’s developer surface includes documentation, engineering blog, pricing, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

0.0/100 minimal ▬ flat Agent 0/100 human only Front door AI 3/6 light Heartbeat 48/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 API

Calendar Artificial Intelligence SchedulingFocus TimeProductivityTeam CoordinationMeeting Optimization

Kin Score

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

Composite quality — 0.0/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 0.0 / 9

Regulatory Posture 1.5 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 18 / 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 7 / 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/clockwise/"><img src="https://apis.io/badge/clockwise/card.svg" alt="Clockwise 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):

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
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 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
Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 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/clockwise/apis.yml: open an issue on github.com/api-evangelist/clockwise 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
Workplace Collaboration App Marketplaces	builds-on	51.7	-	-
Zoom App Marketplace and Partner Ecosystem (builders and partners on Zoom)	builds-on	51.7	-	-
Browser Extension Stores (company-published Firefox add-ons; Chrome Web Store unreadable)	builds-on	51.7	-	-

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.

SCIM 2.0

prose — states compatibility; nothing published to check it against

5 core of 24 operations graded · api-commons/identity

OpenAPI

measured — observed by APIs.io (published)

APIs 1

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

Clockwise REST API

REST API for the Clockwise AI calendar optimization platform, providing programmatic access to focus time management, meeting preferences, scheduling links, and team calendar co...

Clockwise API pricing

Not yet checked against Clockwise's own pricing page. Compiled by API Evangelist; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free	Free
Teams	$6.75
Business	$11.5
Enterprise	Free

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Clockwise Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Clockwise Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Clockwise Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Clockwise Context

20 classes · 0 properties

JSON-LD

Security Posture 1

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

Clockwise Domain Security

TLSv1.3 · 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

GitHubOrg

GitHubOrg

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

ParentCompany

ParentCompany

Source (apis.yml)

name: Clockwise
description: Clockwise was an AI-powered calendar optimization platform that helped individuals, teams, and organizations
  protect focus time, reduce meeting overload, and coordinate scheduling intelligently. The platform provided REST APIs for
  managing focus time blocks, meeting preferences, smart scheduling links, and team calendar coordination. Clockwise was acquired
  by Salesforce and shut down on March 27, 2026.
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: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/clockwise.png
url: https://raw.githubusercontent.com/api-evangelist/clockwise/refs/heads/main/apis.yml
type: Index
tags:
- Calendar
- Artificial Intelligence
- Scheduling
- Focus Time
- Productivity
- Team Coordination
- Meeting Optimization
tags_raw:
- Calendar
- AI
- Scheduling
- Focus Time
- Productivity
- Team Coordination
- Meeting Optimization
created: '2026-06-13'
modified: '2026-08-21'
specificationVersion: '0.23'
aid: clockwise
apis:
- name: Clockwise REST API
  description: REST API for the Clockwise AI calendar optimization platform, providing programmatic access to focus time management,
    meeting preferences, scheduling links, and team calendar coordination features.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.getclockwise.com/developers
  baseURL: https://api.getclockwise.com
  tags:
  - Calendar
  - Focus Time
  - Scheduling
  - Meetings
  properties:
  - type: Documentation
    url: https://support.getclockwise.com/hc/en-us
  - type: OpenAPI
    url: https://api.getclockwise.com/openapi.yml
  contact:
  - FN: Clockwise Support
    email: support@getclockwise.com
common:
- type: ParentCompany
  url: https://apis.io/providers/salesforce/
  name: Salesforce
  x-relationship: acquihire
  x-generated-by: salesforce-family:2026-08-21
- type: DomainSecurity
  url: security/clockwise-domain-security.yml
- type: Website
  url: https://www.getclockwise.com
- type: Documentation
  url: https://support.getclockwise.com/hc/en-us
- type: GitHubOrg
  url: https://github.com/clockwisehq
- type: LinkedIn
  url: https://www.linkedin.com/company/clockwise-inc.
- type: Blog
  url: https://www.getclockwise.com/blog
- type: Pricing
  url: https://www.getclockwise.com/pricing
- type: StatusPage
  url: https://status.getclockwise.com/
- type: X
  url: https://x.com/getclockwise
- type: Plans
  url: plans/clockwise-plans-pricing.yml
- type: RateLimits
  url: rate-limits/clockwise-rate-limits.yml
- type: FinOps
  url: finops/clockwise-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-parent: salesforce
x-relationship: acquihire
x-status: discontinued
x-status-source: https://www.theregister.com/off-prem/2026/03/20/salesforce-acquihires-team-behind-clockwise-for-agentforce/5226782

Clockwise API — frequently asked questions

Does Clockwise have an API?

Yes. APIs.io lists 1 API from Clockwise, including Clockwise REST API.

Is there an OpenAPI specification for the Clockwise API?

Yes. APIs.io indexes 1 OpenAPI specification for Clockwise, each linked for download from this page.

How much does the Clockwise API cost?

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

Is the Clockwise API ready for AI agents?

Clockwise has a Kin Score of 0.0 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/clockwise"

All providers

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

Every operation they expose

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

How their score was established

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