coohua website screenshot

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.

coohua is profiled on the APIs.io network. Tagged areas include Company, Advertising, Mobile, AdTech, and Incentive Advertising.

coohua’s developer surface includes support and 9 more developer resources.

7.4/100 minimal ▬ flat Agent 3/100 human only Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
0 APIs
CompanyAdvertisingMobileAdTechIncentive AdvertisingChinaConsumer

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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. Kin Score badge preview for coohua It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/coohua/"><img src="https://apis.io/badge/coohua/card.svg" alt="coohua 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):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
  • 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
12 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/coohua/apis.yml: open an issue on github.com/api-evangelist/coohua 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.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification) undeclared - - -

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.

coohua API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Coohua Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Coohua Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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

Coohua Domain Security

TLSv1.2

SECURITY

Resources

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

Source (apis.yml)

apis.yml Raw ↑
aid: coohua
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: none
  source:
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/coohua.png
name: coohua
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/coohua/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- qiming
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-12'
tags:
- Company
- Advertising
- Mobile
- AdTech
- Incentive Advertising
- China
- Consumer
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.coohua.com/about.html
- type: TermsOfService
  url: https://www.coohua.com/terms.html
- type: Support
  url: https://www.coohua.com/faq.html
- type: Contact
  url: https://www.coohua.com/contact.html
- type: GitHubOrganization
  url: https://github.com/coohua-dev
- type: Packages
  url: packages/coohua-packages.yml
- type: DomainSecurity
  url: security/coohua-domain-security.yml
- type: LLMsTxt
  url: llms/coohua-llms.txt
- type: Plans
  url: plans/coohua-plans-pricing.yml
- type: RateLimits
  url: rate-limits/coohua-rate-limits.yml
x-enrichment:
  date: '2026-08-12'
  status: minimal
  artifacts_added: 6
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: 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.
  evidence:
  - url: http://developer.coohua.cn/
    status: 500
  - url: http://api.coohua.cn/
    status: 500
  - url: https://www.coohua.com/partner.html
    status: 200
  - url: https://www.coohua.com/.well-known/agent-card.json
    status: 404
  - url: https://www.coohua.com/openapi.json
    status: 404
  checked: '2026-08-12'

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

A second provider on the same verified email joins the account you already have.