Zenput website screenshot

Zenput

Zenput (now Crunchtime Ops Execution) is an operations-execution platform for multi-unit restaurant and convenience-store operators, used across 60,000+ locations in 100+ countries to run task management, audits and food-safety compliance, temperature monitoring, food-prep labeling, and store-level operational workflows. Zenput exposes a RESTful HTTP API (documented at developer.zenput.com) for submissions/form data, locations, users and roles, teams, tasks, sensors, calendar events / operating hours, general attributes, and field-business-consultant (FBC) assignments. The API authenticates with a per-user X-API-TOKEN header, is versioned in the URL path (v1 and v3), and provides a large-batch submissions retrieval flow with token-based paging plus a staging environment for testing. Zenput was acquired by Crunchtime in 2022 and continues to operate its developer platform under the Zenput brand.

Zenput publishes 1 API on the APIs.io network. Tagged areas include Company, Restaurant Operations, Operations Execution, Food Safety, and Compliance.

Zenput’s developer surface includes documentation, API reference, getting-started guide, support, authentication, changelog, sandbox, and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub
18.6/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyRestaurant OperationsOperations ExecutionFood SafetyComplianceTask ManagementConvenience StoresField OperationsRestaurant Technology

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 18.6/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 8.6 / 20
Access Clarity 0.0 / 20
Operational Transparency 2.4 / 13
Contract Governance 0.0 / 12
Discoverability 7.6 / 10
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 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 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
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.
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 github.com/api-evangelist/zenput: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Zenput API

RESTful HTTP API for the Zenput operations-execution platform — retrieve activity/form submissions (including large-batch paged retrieval), manage locations, users, user roles, ...

Security Posture 2

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

Zenput Authentication

apiKey · 1 scheme

SECURITY

Zenput Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 Sandbox
Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 X-MCPServerCandidate
X-MCPServerCandidate

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Lifecycle
Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication

Operate 2

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog

Company 1

The organization behind the API

Website
Website

Other 1

Properties that don't map to a standard resource type

ParentCompany
ParentCompany

Source (apis.yml)

apis.yml Raw ↑ 
aid: zenput
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  - url: https://www.zenput.com
    status: 301
    note: declared website redirects to https://www.crunchtime.com/operations-execution — a different registrable domain (zenput.com
      -> crunchtime.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/zenput.png
name: Zenput
description: Zenput (now Crunchtime Ops Execution) is an operations-execution platform for multi-unit restaurant and convenience-store
  operators, used across 60,000+ locations in 100+ countries to run task management, audits and food-safety compliance, temperature
  monitoring, food-prep labeling, and store-level operational workflows. Zenput exposes a RESTful HTTP API (documented at
  developer.zenput.com) for submissions/form data, locations, users and roles, teams, tasks, sensors, calendar events / operating
  hours, general attributes, and field-business-consultant (FBC) assignments. The API authenticates with a per-user X-API-TOKEN
  header, is versioned in the URL path (v1 and v3), and provides a large-batch submissions retrieval flow with token-based
  paging plus a staging environment for testing. Zenput was acquired by Crunchtime in 2022 and continues to operate its developer
  platform under the Zenput brand.
url: https://raw.githubusercontent.com/api-evangelist/zenput/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- version-one-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 9
  pass: local-v1
tags:
- Company
- Restaurant Operations
- Operations Execution
- Food Safety
- Compliance
- Task Management
- Convenience Stores
- Field Operations
- Restaurant Technology
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Zenput API
  description: RESTful HTTP API for the Zenput operations-execution platform — retrieve activity/form submissions (including
    large-batch paged retrieval), manage locations, users, user roles, teams, tasks, sensors, calendar events / operating
    hours, general attributes, and FBC assignments. Authenticated with an X-API-TOKEN header and versioned in the URL path
    (v1/v3).
  humanURL: https://developer.zenput.com
  baseURL: https://www.zenput.com/api/v1/
  tags:
  - Operations Execution
  - Submissions
  - Locations
  - Restaurant Operations
  properties:
  - type: Documentation
    url: https://developer.zenput.com/docs/introduction
  - type: APIReference
    url: https://developer.zenput.com/reference
  - type: GettingStarted
    url: https://developer.zenput.com/docs/introduction
  - type: Authentication
    url: authentication/zenput-authentication.yml
  - type: LLMsTxt
    url: llms/zenput-llms.txt
common:
- type: ParentCompany
  url: https://apis.io/providers/crunchtime/
  name: Crunchtime
  x-relationship: acquired
  x-evidence: Zenput was acquired by Crunchtime in 2022 and continues to operate its developer platform under the Zenput brand.
- type: DomainSecurity
  url: security/zenput-domain-security.yml
- type: DeveloperPortal
  url: https://developer.zenput.com
- type: Website
  url: https://www.zenput.com
- type: Documentation
  url: https://developer.zenput.com/docs/introduction
- type: APIReference
  url: https://developer.zenput.com/reference
- type: GettingStarted
  url: https://developer.zenput.com/docs/introduction
- type: Support
  url: https://help.crunchtime.com
- type: GitHubOrganization
  url: https://github.com/zenput
- type: Authentication
  url: authentication/zenput-authentication.yml
- type: LLMsTxt
  url: llms/zenput-llms.txt
- type: WellKnown
  url: well-known/zenput-well-known.yml
- type: Conventions
  url: conventions/zenput-conventions.yml
- type: Lifecycle
  url: lifecycle/zenput-lifecycle.yml
- type: ChangeLog
  url: changelog/zenput-changelog.yml
- type: Sandbox
  url: sandbox/zenput-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/zenput-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'

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/zenput"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/zenput/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/zenput/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.