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 9 more developer resources.

🌐 Visit website 📡 Source on GitHub
25.0/100 emerging ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs 1 MCP Servers
CompanyRestaurant OperationsOperations ExecutionFood SafetyComplianceTask ManagementConvenience StoresField OperationsRestaurant Technology

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 25.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 25/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 4 / 4
Consent & Bot Identity 0 / 3
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/zenput: 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 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, ...

MCP Servers 1

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

zenput-mcp.yml

MCP SERVER

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
 MCPServer
MCPServer

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

Source (apis.yml)

apis.yml Raw ↑ 
aid: zenput
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
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: 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: MCPServer
  url: mcp/zenput-mcp.yml