Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计通过

upkuajing-customs-trade-company-search上夸晶海关贸易公司搜索

Agent Skill

upkuajing-customs-trade-company-search 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,190

周安装

180

GitHub Stars

公开资料未说明

下载量

1,469
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:upkuajing-customs-trade-company-search(上夸晶海关贸易公司搜索)
来源仓库:https://github.com/upkuajing/upkuajing-customs-trade-company-search
安装命令:
openclaw skills install upkuajing-customs-trade-company-search
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install upkuajing-customs-trade-company-search

简介

基于海关贸易数据搜索进出口企业与全球买家信息。

  • 提供订单详情、联系人及物流关联数据,助力外贸业务。
  • 适用于寻找潜在客户或分析行业竞争格局的场景。
  • 使用前需开通边境魔方贸易数据接口权限。upkuajing-customs-trade-company-search 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 注意部分历史数据可能存在延迟,实时性依赖海关申报进度。

SKILL.md

name
upkuajing-customs-trade-company-search
description
Official skill for upkuajing (跨境魔方). Find companies (找公司) and global buyers using customs trade data. Get trade order details, business contact info, and lead generation tools for import/export market research and supply chain analysis.
metadata
{"version":"1.0.6","homepage":"https://www.upkuajing.com","clawdbot":{"emoji":"🏢","requires":{"bins":["python"],"env":["UPKUAJING_API_KEY"]},"primaryEnv":"UPKUAJING_API_KEY"}}

UpKuaJing Customs Trade Company Search

Search for companies through customs trade data using the UpKuaJing Open Platform API. This skill uses a data-driven approach: finding companies by analyzing trade records and transaction patterns.

Overview

This skill provides access to UpKuaJing's customs trade data API through four scripts: two search methods (trade list, company list) and two enhancement interfaces (company details, contact information). 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/trade_list_search.py. Do NOT use shell compound commands like cd scripts && python trade_list_search.py.

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

Two Search Methods

Trade List Search (trade_list_search.py)

  • Return granularity: Each trade order as one record
  • Use cases: Focus on "what transactions occurred"
  • Examples:

- "Show all orders where Company A purchased LED" - "Find soybean trade records imported/exported to US" - "View specific transaction details within a time period"

Company List Search (company_list_search.py)

  • Return granularity: Trade orders aggregated by company, each company as one row
  • Use cases: Focus on "which companies exist"
  • Examples:

- "Find companies that purchased LED" - "Find US companies with electronics import/export business with China" - "Find companies with China-US trade" (logistics industry customer development)

Two Enhancement Features

After obtaining trade list or company list, use these interfaces to enrich company IDs in the results when necessary: Company Details (company_get_details.py --companyIds *)

  • Get company information (excluding contact information)
  • Parameters: --companyIds List of company IDs (space-separated), max 20 at a time
  • API business parameters: Company Details

Contact Information (company_get_contact.py --companyIds *)

  • Get contact details: email, phone, social media, website
  • Parameters: --companyIds List of company IDs (space-separated), max 20 at a time
  • API business parameters: Get Contact Information

API Key and Top-up

This skill requires an API key. The API key is stored in the ~/.upkuajing/.env file:

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

Fees

All API calls incur fees, different interfaces have different billing methods. Latest pricing: Users can visit Detailed Price Description 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

Enhancement Interface Billing Rules

Billed by number of IDs passed, max 20 IDs per call:

  • Pass 1 ID = billed 1 time
  • Pass 20 IDs = billed 20 times (single call limit)
  • Before batch retrieval must:

1. Inform user of number of IDs passed and corresponding fee count 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 the appropriate API based on user intent

Decision Guide

User IntentUse API
"Analyze trade patterns/order data"Trade list
"Find companies purchasing XXX"Company list
"Find suppliers for XXX with email"Company list existEmail=1
"Get company detailed information"Company details
"Get contact information"Contact information

Usage Examples

Scenario 1: Small Query — Trade Data Analysis

User request: "Show 2024 LED lighting fixture trade data exported to US"

python scripts/trade_list_search.py \
  --params '{"products": ["LED lights"], "buyerCountryCodes": ["US"], "dateStart": 1704067200000, "dateEnd": 1735689599999}' \
  --query_count 20

To further get supplier details (supports batch queries):

python scripts/company_get_details.py --companyIds 123456 789012 ...

Scenario 2: Large Query — Big Data Analysis

User request: "Analyze 100 soybean trade records from 2024" Before execution inform user: ceil(100/20) = 5 API calls, confirm before executing;

python scripts/trade_list_search.py --params '{"products": ["soybean"], "dateStart": 1704067200000, "dateEnd": 1735689599999}' --query_count 100

Scenario 3: Ultra Large Query - Multiple Script Calls Required

User request: "Find 2000 companies importing electronics from China, with email addresses" Before execution inform user: ceil(2000/20) = 100 API calls, confirm before executing;

python scripts/company_list_search.py --params '{"companyType": 2, "sellerCountryCodes": ["CN"], "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 query from last cursor and appends to file

python scripts/company_list_search.py --task_id 'a1b2-c3d4' --query_count 1000

Error Handling

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

Best Practices

Choosing the Right Method

  1. Understand user intent:

- Analyze trade data? → Use trade list search - Find customers/partners? → Use company list search

  1. Check API documentation:

- Before executing list queries, must first check the corresponding API reference documentation - Trade list: Check references/trade-list-api.md - Company list: Check references/company-list-api.md

  1. Identify parameter conditions:

- Set date range - HS codes are usually more precise than product names for filtering - Reduce noise by filtering specific countries - Use ISO country codes: CN, US, JP, etc. - Use filters to find companies with contact information

Handling Results

  1. Handle jsonl files carefully: For large data queries, pay attention to file size
  1. Gradually enrich information: Only call details/contact interfaces when needed

- Company IDs returned by both list interfaces can be used for both detail interfaces - If user only needs a few companies, don't get details for all companies

Notes

  • All timestamps are in milliseconds
  • Country codes use ISO 3166-1 alpha-2 format (e.g., CN, US, JP)
  • File paths use forward slashes on all platforms
  • Product names and 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:

  • upkuajing-global-company-people-search — Global company and people search
  • upkuajing-email-tool — Send emails and manage email tasks
  • upkuajing-map-merchants-search — Map-based merchant search
  • upkuajing-sms-tool — Send SMS and manage SMS tasks
  • upkuajing-contact-info-validity-check — Check contact info validity

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

79.32%
按下载量换算1,165

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills