cutt
cutt (cutt.com) is a Chinese technology company surfaced from the published portfolio of Qiming Venture Partners and added to the API Evangelist network as an enrichment lead. As of the 2026-07-20 enrichment pass the company has no reachable public web presence: the cutt.com apex does not complete an HTTPS connection, www.cutt.com returns HTTP 404 for the site root and every probed path, and no developer, documentation, or API subdomain (api./developer./docs./ dev./open.) resolves. One surviving subdomain, zhiyue.cutt.com, issues a 301 redirect to api.zhiyueapp.cn — a live JSON API host fronted by an APISIX 3.4.1 gateway that returns an empty 200 body and publishes no documentation. The zhiyueapp.cn domain is registered to 北京简网生活圈科技有限公司 (Beijing Jianwang Life Circle Technology Co., Ltd.), which appears to be the operating entity behind the cutt.com property. The cutt.com domain itself was created in 2003 and remains registered through Alibaba Cloud Computing Ltd. (HiChina) with an April 2027 expiry, so the registration is maintained even though the public site is not being served. No OpenAPI, AsyncAPI, SDK, portal, changelog, status page, or /.well-known/ discovery document could be found on any reachable host. This profile therefore records probed infrastructure evidence only; it carries no fabricated API surface and should be revisited if the company restores a public developer presence.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles cutt the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — cutt scores 5.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from cutt's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cutt/"
title="cutt on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cutt.svg"
alt="cutt Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/cutt/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cutt/"
title="cutt on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/cutt/card.svg"
alt="cutt Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile cutt
Each block below is one kind of artifact we hold for cutt. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for cutt — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cutt · machine-readable index on apis.io
This is an independent, third-party profile of cutt, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.