Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
caimitech website screenshot

caimitech

caimitech.com is the domain of Wacai (挖财, Hangzhou Wacai Network Technology Co.), a Chinese personal-finance and wealth-management company founded in 2009 that offers accounting/bookkeeping apps, personal financial management (PFM) tools, wealth-management services, and credit solutions. Its developer surface is the Wacai Open Platform (挖财开放平台) — an HMAC-signed API gateway addressed by (api_name, api_version) pairs rather than REST paths, with first-party client SDKs in Java (published to Maven Central under com.wacai), Node.js, PHP, Go, and C#, plus a separate topic-based message gateway (pull/ack). Access uses an app_key/app_secret credential with MAC or RSA request signing and an optional token service. No OpenAPI document is published; this profile was enriched from the provider's public GitHub SDKs and package registries.

human only

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.

Kin Score

API Evangelist profiles caimitech the way a machine reads it — 2 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 — caimitech scores 14.0/100 (minimal), with a separate agent-readiness read of 10/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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 14.0/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 6.5 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 10/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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

How we profile caimitech

Each block below is one kind of artifact we hold for caimitech. 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 2

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.

Caimitech Authentication

app-credential/request-signature/bearer-token · 3 schemes

SECURITY

Caimitech Domain Security

TLSv1.2 · DNSSEC

SECURITY

Resources

Every other property we hold for caimitech — 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.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/caimitech · machine-readable index on apis.io