Delivers monthly trade-trend insights from customs records. It pulls monthly breakdowns ofshipment frequency, product quantity, gross weight and transaction value with optionalfilters by company ID and covers customs data across 220+ countries and territories.Export teams, analysts and supply-chain managers can analyze trading patterns, trackseasonal fluctuations and monitor long-term business activities. This tool fitsmarket-trend research, supplier performance tracking and trade-flow intelligence analysis.

Get monthly customs‑trade breakdowns via company‑ID. Analyze seasonal shifts and long‑term trade trends for supplier monitoring and global market research. Trigger: monthly customs trade trends, import‑export seasonal analysis, supplier sales monitoring, global trade‑flow research, customs‑data breakdown

Customs Company Trade Trends

Query company monthly trade trends from customs data using the UpKuaJing Open Platform API.

Overview

This skill provides access to company monthly trade trends from UpKuaJing's customs database. Given a company ID, company type, and optional filters (date range, products, HS codes, countries, partners, port), it returns the monthly breakdown of trade count, quantity, weight, and amount.

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

Company Trade Trends Query (customs_company_trends.py)

• Return granularity: One record per month
• Use cases: View a company's trade trends over time, analyze seasonal patterns
• Examples:
  • "Get monthly trade trends for company 100001 as a supplier"
  • "Query trade trends for company 100001 as a buyer with date range"
• Parameters: See Company Trade Trends 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/trends","requestId":"f47ac10b58cc4372a5670e02b2c3d479","context":"Company trend 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 trends 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 monthly trade trends for company 100001 as a supplier"	Company Trade Trends Query
"Show trade trends of company 100001 from 2024 to 2025"	Company Trade Trends Query

Usage Examples

Query Company Trade Trends

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

bash

python scripts/customs_company_trends.py --params '{"companyId":100001,"companyType":1}'

Query with date range and filters:

bash

python scripts/customs_company_trends.py --params '{"companyId":100001,"companyType":1,"dateStart":1700000000000,"dateEnd":1735689599999,"products":["LAPTOP","MOBILE PHONE"],"countryCodes":["US","KR"]}'

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 Trade Trends: Check references/customs-company-trends-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-trends-api.md
   • Do not guess parameter names, get accurate parameter names and formats from documentation

2. Filtering:

   • Use dateStart and dateEnd (millisecond timestamps) to narrow down the time range
   • Use ISO country codes (e.g., "US", "KR") for country filters
   • Use HS codes for product filtering when possible (more precise than product names)

3. Cross-skill usage:

   • The company ID can be obtained from customs-company-stats or upkuajing-customs-trade-company-search

Notes

• companyType determines the company's role (1=supplier, 2=buyer)
• monthText provides a human-readable month string (e.g., "2024-01")
• month 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-stats — Query company basic trade statistics
• 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