AI Agent Hub
Back to skills
⚖️

Qichacha Company Data Query

Professional Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_db7424f5/udb7-qcc-company-query using https://skillhub.cn/install/skillhub.md.

About this skill

What It Solves

When evaluating suppliers, partners, or investment targets, engineers often spend time jumping between scattered company records: business registration, equity structure, risk indicators, and bidding history usually live in different tables, pages, and documents. Qichacha Company Data Query focuses on turning that lookup into a clearer workflow by organizing company data around common query topics and supporting filtering and relationship checks, so less time is spent reconciling fields by hand.

How It Works

The skill is scoped to company data lookup, filtering, and relationship analysis, with coverage of the business registration, equity, risk, and bidding areas listed in the source material. It requires KUAICHA_API_KEY before use. A typical workflow is:
- identify the target entity, such as a company name, registration identifier, or related party;
- choose the data area to inspect, for example registration details, equity relationships, risk items, or bidding records;
- filter the returned fields to remove irrelevant entities or records;
- connect multiple entities to understand holding, investment, shared ownership, or business relationships.

Boundaries and Caveats

It fits cases where the needed company data is already clear, such as initial due-diligence screening, supplier background checks, or equity-chain review. Because it depends on an external API, the key must be valid before calls, and the data usage limits of the underlying service should be respected. The provided material states that KUAICHA_API_KEY is required but does not define exact fields, response shapes, or endpoint details, so implementation should be guided by the actual API response. Treat results as supporting evidence, not legal or credit conclusions; material decisions still require manual verification against primary records.

Use Cases

  • Before due diligence, cross-check a company's business registration against its actual equity structure.
  • When vetting suppliers, batch-filter recent bidding records and exclude abnormal entities.
  • In investment analysis, trace a group's multi-tier holding chain to locate the actual controller and cross-holdings.
  • During compliance review, pull a target company's risk items to check for pending litigation or administrative penalties.

Best For

  • Procurement engineers doing supplier onboarding who need to verify registration status and past bidding records.
  • Investment analysts conducting fund due diligence who need to trace multi-tier holding chains and identify cross-investments.
  • Compliance lawyers who need to pull target companies' administrative penalties and pending litigation lists.
  • Data engineers building enterprise knowledge graphs who need bulk registration and equity fields for structured ingestion.