Provides aggregated customs-trade statistics for overseas companies. It pulls tradingfrequency, shipment weight, product quantity, transaction value and partner counts viacompany ID with customs data covering more than 220 countries and territories. It enablesexport teams, analysts and researchers to access summarized trade overviews, assesscorporate trading scale and evaluate partner networks. This tool is well-suited forsupplier screening, buyer validation and trade-intelligence analysis.

Fetch aggregated customs‑trade stats by company ID across 220+ regions. Assess business scale and partners for supplier screening and trade‑intelligence research. Trigger: customs trade statistics lookup, company import‑export analysis, overseas partner network assessment, global trade intelligence, supplier vetting

Customs Company Basic Trade Statistics

Query company basic trade statistics from customs data using the UpKuaJing Open Platform API.

Overview

This skill provides access to company basic trade statistics from UpKuaJing's customs database. Given a company ID (companyId) and company type, it returns the trade summary including total trade count, weight, quantity, amount, partner count, and trade date range.

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/customs_company_stats.py. Do NOT use shell compound commands like cd scripts && python customs_company_stats.py

Company Basic Trade Statistics Query (customs_company_stats.py)

• Return granularity: One record per company, containing aggregated trade statistics
• Use cases: View a company's overall trade summary, get trade volume and partner count
• Examples:
  • "Get trade statistics for company 100001 as a supplier"
  • "Query trade stats for company 100001 as a buyer"
• Parameters: See Company Basic Trade Statistics API

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:

text

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, then bind account

Report Skill Call Errors

When an API call fails or returns abnormal data (server error, timeout, malformed response, etc.), explain the anomaly to the user in natural language and ask whether to report it to the platform for troubleshooting. Only run the report after user confirmation:

bash

python scripts/error_report.py --params '{"requestPath":"/agent/customs/company/stats","requestId":"f47ac10b58cc4372a5670e02b2c3d479","context":"Company stats query failed with a server error"}'

• Do not report normal business conditions (insufficient balance, invalid API key, parameter errors) — handle them via their own flows
• Error reporting does not incur query fees
• Parameters: See Error Report API

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)

Query Billing Rules

Billed by number of calls, each call returns trade statistics for one company:

• Each API call incurs a fee
• Before execution:
  1. Inform user that this query will incur a fee
  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

Decision Guide

User Intent	Use API
"Get trade statistics for company 100001 as a supplier"	Company Basic Trade Statistics Query
"Query trade summary for company 100001 as a buyer"	Company Basic Trade Statistics Query

Usage Examples

Query Company Basic Trade Statistics

User request: "Get trade statistics for company 100001 as a supplier"

bash

python scripts/customs_company_stats.py --companyId 100001 --companyType 1

User request: "Query trade stats for company 100001 as a buyer"

bash

python scripts/customs_company_stats.py --companyId 100001 --companyType 2

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
• Skill call errors / abnormal responses: Explain to the user and, with user confirmation, report to the platform via python scripts/error_report.py (see Report Skill Call Errors)

API Documentation Reference

• Company Basic Trade Statistics: Check references/customs-company-stats-api.md
• Error Report: Check references/skill-error-report-api.md

Best Practices

1. Check API documentation:

   • Before executing queries, must first check the corresponding API reference documentation
   • Check references/customs-company-stats-api.md
   • Do not guess parameter names, get accurate parameter names and formats from documentation

2. Data interpretation:

   • countTrade is the total number of trade transactions
   • countWeight, countQuantity, countAmount are aggregated totals
   • countPartner is the total number of unique trading partners
   • earliestTradeDate and latestTradeDate define the trade activity time range

3. Cross-skill usage:

   • The company ID from results can be used with customs-company-trends to get monthly trade trends
   • The company ID can also be used with customs-company-partner-stats to get partner distribution data

Notes

• companyType determines the company's role (1=supplier, 2=buyer)
• earliestTradeDate is a date string (e.g., "2020-01-15"), while latestTradeDate is a millisecond timestamp
• File paths use forward slashes on all platforms
• 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:

• customs-company-trends — Query company trade trends (monthly breakdown)
• customs-company-partner-stats — Query company trade partner distribution
• upkuajing-customs-trade-company-search — Search customs trade companies
• upkuajing-global-company-people-search — Unified company and people search across all sources
• global-company-search — Search companies from the global company database
• global-company-person-search — Search people from the global company database
• global-company-shareholder — Query shareholder list from the global company database
• global-company-employee — Query employee list from the global company database
• upkuajing-contact-info-validity-check — Check contact info validity
• phone-validity-check — Check phone number validity