UpKuaJing LinkedIn company search, find companies from LinkedIn data by name, industry, size, and founded year. UpKuaJing helps sales teams, marketers, and B2B lead builders discover LinkedIn company profiles, research target accounts, and enrich firmographic data — perfect for customer development, market research, competitor analysis, and account-based sales.

SKILL.md

---
name: linkedin-company-search
description: Official skill for upkuajing (跨境魔方). Search companies (找公司) from LinkedIn data. Find companies by name, industry, size, and founded year. Ideal for customer development and market research on LinkedIn data.
metadata: {"version":"1.0.1","homepage":"https://www.upkuajing.com","clawdbot":{"emoji":"🏢","requires":{"bins":["python"],"env":["UPKUAJING_API_KEY"]},"primaryEnv":"UPKUAJING_API_KEY"}}
---

# LinkedIn Company Search

Search company data from LinkedIn using the UpKuaJing Open Platform API.

## Overview

This skill provides access to UpKuaJing's LinkedIn company data through one list search script. API key generation and top-up are provided through the `auth.py` script.

## Running Scripts

### Environment Setup

1. **Check Python**: `python --version`
2. **Install dependencies**: `pip install -r requirements.txt`

Script directory: `scripts/*.py`
Run example: `python scripts/*.py`

**Important**: Always use direct script invocation like `python scripts/linkedin_company_search.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_company_search.py`

### LinkedIn Company List Search (`linkedin_company_search.py`)
- **Return granularity**: Each company as one record
- **Use cases**: Focus on "which companies exist" in LinkedIn data
- **Examples**:
  - "Find manufacturers producing LED lights"
  - "Find tech companies with 100-500 employees"
- **Parameters**: See [LinkedIn Company List](references/linkedin-company-list-api.md)

## API Key and Top-up

This skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:
```bash
cat ~/.upkuajing/.env
```
**Example file content**:
```
UPKUAJING_API_KEY=your_api_key_here
```
### **API Key Not Set**
First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;
If UPKUAJING_API_KEY is not set, prompt the user to choose:
1. User has one: User provides it (manually add to ~/.upkuajing/.env file)
2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env
Wait for user selection;

### **Account Top-up**
When API response indicates insufficient balance, explain and guide user to top up:
1. Create top-up order (`auth.py --new_rec_order`)
2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;

### **Get Account Information**
Use this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`

## API Key and UpKuaJing Account
- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account

## Fees

**All API calls incur fees**, different interfaces have different billing methods.

**Latest pricing**: Users can visit [Detailed Price Description](https://www.upkuajing.com/web/openapi/price.html)
Or use: `python scripts/auth.py --price_info` (returns complete pricing for all interfaces)

### List Search Billing Rules

Billed by **number of calls**, each call returns up to 20 records:
- Number of calls: `ceil(query_count / 20)` times
- **Whenever query_count > 20, must before execution:**
  1. Inform user of expected number of calls
  2. Stop, wait for explicit user confirmation in a separate message, then execute script

### Fee Confirmation Principle

**Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.**


## Workflow

Choose parameters based on user intent.

### Decision Guide

| User Intent | Use API |
|-------------|---------|
| "Find companies producing XXX" | LinkedIn company list (keywords / companyNames) |
| "Find companies with email/phone" | LinkedIn company list existEmail=1 / existPhone=1 |
| "Find companies with 100-500 employees" | LinkedIn company list companySizes=["51-200","201-500"] |
| "Find companies founded after 2015" | LinkedIn company list minCompanyFounded=2015 |

## Usage Examples

### Scenario 1: Small Query — Search Companies

**User request**: "Find Chinese manufacturers producing LED lights"
```bash
python scripts/linkedin_company_search.py \
  --params '{"keywords": ["LED lights"], "countryCodes": ["CN"], "existEmail": 1}' \
  --query_count 20
```

### Scenario 2: Large Query — Multiple Script Calls Required

**User request**: "Find 1000 US electronics companies with email addresses"
**Before execution** inform user: ceil(1000/20) = 50 API calls, confirm before executing.
```bash
python scripts/linkedin_company_search.py --params '{"keywords": ["electronics"], "countryCodes": ["US"], "existEmail": 1}' --query_count 1000
```
**After execution**: Script responds {"task_id":"a1b2-c3d4", "file_url": "xxxxx", ……}
**Continue execution, append data**: Specify task_id, script continues from where it left off and appends to file
```bash
python scripts/linkedin_company_search.py --task_id 'task-id-here' --query_count 2000
```

## Error Handling

- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` file
- **Insufficient balance**: Guide user to top up
- **Invalid parameters**: **Must first check the corresponding API documentation in references/ directory**, get correct parameter names and formats from documentation, do not guess

### API Documentation Reference

- [LinkedIn Company List API](references/linkedin-company-list-api.md)

## Best Practices

1. **Check API documentation**:
   - **Before executing queries, must first check the corresponding API reference documentation**
   - Check [references/linkedin-company-list-api.md](references/linkedin-company-list-api.md)
   - Do not guess parameter names, get accurate parameter names and formats from documentation

2. **Optimize query parameters**:
   - Use `keywords` / `companyNames` to filter precisely; industry and product names must be in **English**
   - Use `existEmail=1` or `existValidEmail=1` to filter companies with contact information
   - Use `countryCodes` to limit country scope; use `companySizes` to limit company size

3. **Large result sets**:
   - For large queries, pay attention to the jsonl file size

## Notes
- Company records use `pid` as the unique identifier
- All timestamps are in **seconds** (incorp_date is a second-level timestamp)
- Country codes use ISO 3166-1 alpha-2 format (e.g., CN, US, JP)
- File paths use forward slashes on all platforms
- Industry names must be in **English**
- Search quantity affects API response time, recommend setting timeout: 120
- **Prohibit outputting technical parameter format**: Do not display code-style parameters in responses, convert to natural language
- **Do not** estimate or guess per-call fees — use `python scripts/auth.py --price_info` to get accurate pricing information
- **Do not** guess parameter names, get accurate parameter names and formats from documentation

## Related Skills

Other UpKuaJing skills you might find useful:

- linkedin-person-search — Search people from LinkedIn data
- global-company-person-search — Search people from the global company database
- global-company-search — Search companies from the global company database
- upkuajing-global-company-people-search — Unified company and people search across all sources
- upkuajing-customs-trade-company-search — Search customs trade companies
- upkuajing-contact-info-validity-check — Check contact info validity