coohua
Coohua (酷划在线) is a Beijing-based Chinese mobile advertising company founded in 2014 and backed by Qiming Venture Partners. It pioneered the incentive- and lock-screen-advertising model in China, rewarding users with cash for unlocking their screens, reading content, and engaging with ads. Its flagship products include Coohua Lockscreen (酷划锁屏) and the Tao News (淘新闻) reading-rewards app, serving advertisers across internet, finance, automotive, and e-commerce verticals. At its peak Coohua captured a majority share of China's lock-screen advertising market and returned billions of yuan in cash rewards to users annually. No public API, developer portal, SDK, or machine-readable specification could be found during enrichment; advertising business is transacted through a sales contact (sale@coohua.com) on the 广告合作 page rather than through any self-serve or programmatic surface. The company does maintain a GitHub organization (github.com/coohua-dev) publishing CocoaPods spec repositories for the iOS modules behind its two apps, but every podspec resolves its source to an unreachable internal gitlab.coohua.com host, so none of it is consumable by a third party. This profile is retained as a company/provider record surfaced from the Qiming portfolio.
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 coohua the way a machine reads it — 3 machine-readable artifacts, 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 — coohua scores 9.4/100 (minimal), with a separate agent-readiness read of 3/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.
Why this profile is thin
Coohua ships consumer reward apps and sells lock-screen ad inventory by email (sale@coohua.com on its 广告合作 page); its own coohua.cn domain is dead — the apex has no A record and www/api/open/developer/docs are a DNS wildcard to 39.106.94.60 that answers openresty HTTP 500 on every path, including "/" — while the surviving coohua.com pages carry no developer, API or SDK entry anywhere in their navigation.
This is an honest zero, not a gap in our research. coohua does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
http://developer.coohua.cn/→ HTTP 500http://api.coohua.cn/→ HTTP 500https://www.coohua.com/partner.html→ HTTP 200https://www.coohua.com/.well-known/agent-card.json→ HTTP 404https://www.coohua.com/openapi.json→ HTTP 404
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.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from coohua'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/coohua/"
title="coohua on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/coohua.svg"
alt="coohua Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/coohua/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/coohua/"
title="coohua on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/coohua/card.svg"
alt="coohua 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 coohua
Each block below is one kind of artifact we hold for coohua. 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.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Coohua Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Coohua Rate Limits
RATE LIMITSSecurity 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 coohua — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/coohua · machine-readable index on apis.io
This is an independent, third-party profile of coohua, 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.