Enterprise Profile and Upstream-Downstream Relationship Analysis

The Problem to Solve

In enterprise operations, obtaining an accurate and comprehensive profile quickly is critical for decisions, partnership assessments, or risk control. Traditional methods like public database queries or manual research are time-consuming, fragmented, and lack traceable project evidence. This skill addresses this by using structured API calls to generate a detailed profile from the full company name, covering business fundamentals, operational data, project performance, and upstream-downstream relationships.

Core Capabilities and Workflow

The core capability of this skill is to extract and integrate multi-dimensional enterprise information via the SBKJ API service. Key workflow steps include:
- Data Acquisition and Summary: First, call the 企业画像汇总 API to retrieve basic information such as company type, industry, registration area, operational status, and bid/win statistics, forming an initial overview.
- Relationship Detail Analysis: Based on needs, sequentially call paginated APIs for 联系人, 客户, and 供应商, focusing on fields like partnerCompanyName, relatedProjectId, and relationshipType to analyze upstream-downstream relationships.
- Project Verification and Traceability: For key related projects, use the 项目详情 API to verify enterprise roles, ensuring relationship conclusions are traceable to specific projects returned by APIs, and distinguishing between "API facts" and "analytical judgments".
- Descriptive Analysis: Perform descriptive analysis on bid industries, win industries, customer concentration, and supplier concentration, outputting opportunity and risk assessments while avoiding inferences about equity or control.
- Structured Output: Sequentially generate enterprise overview, operational information, bid performance, contacts, key customers, suppliers, related projects, and conclusions, clearly noting unmatched fields.

Applicable Boundaries and Notes

When using this skill, note:
- Data Scope: Project counts and amounts within API coverage do not represent the full operational scale of the enterprise.
- Relationship Inference Limits: Customer and supplier relationships are limited to bidding project cooperation, not implying current collaboration; no inferences about equity, control, or exclusive relationships are made.
- Privacy and Compliance: Contact information from APIs must be used in compliance with applicable privacy, marketing, and communication rules.
- Manual Verification Needs: Unmatched fields or complex analytical conclusions (e.g., group attribution guesses) require human intervention to avoid over-reliance on automation.
- Call Conventions: Enterprise names must use the legal full name, API keys are securely stored, and results explicitly indicate "未命中" (not found) for accuracy.