Query import/export trade trends analysis — retrieve monthly import and export trend data for a specified HS code over recent months. Returns both export and import data with monthly breakdowns including trade counts, quantities, weights, amounts, buyer counts and seller counts. Designed for trade analysts, supply chain managers and market researchers who need to analyze trade trends for specific products over time, understand seasonal patterns, compare export versus import activity and monitor market dynamics across global customs data covering 220+ countries and territories.

Query import/export trade trends analysis — retrieve monthly import and export trend data for a specified HS code over recent months. Trigger: trade trends, import export analysis, HS code trends, monthly trade data, trade time series analysis

Customs Analysis Trends

Query import/export trade trend data from customs data using the UpKuaJing Open Platform API.

Overview

This skill provides monthly import and export trend data for a specified HS code over a given number of recent months. It returns both export and import data with monthly breakdowns including trade counts, quantities, weights, amounts, buyer and seller counts.

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

Trends Query (customs_analysis_trends.py)

• Return granularity: Monthly aggregated export and import data
• Use cases: Analyze trade trends for a specific product over time, understand seasonal patterns, compare export vs import activity
• Examples:
  • "Show trade trends for HS code 04021000 over the last 12 months"
  • "Get import/export trends for product 04021000 from China"
• Parameters: See 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/analysis/trends","requestId":"f47ac10b58cc4372a5670e02b2c3d479","context":"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 one page of trend data:

• 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
"Show trade trends for HS code 04021000 over 12 months"	Trends Query
"How has trade for this product changed over time?"	Trends Query
"Compare export vs import for product 04021000"	Trends Query

Usage Examples

Query Trade Trends

User request: "Show trade trends for HS code 04021000 over the last 12 months"

bash

python scripts/customs_analysis_trends.py --params '{"hscode":"04021000","recentMonths":12}'

Query with country filter:

bash

python scripts/customs_analysis_trends.py --params '{"hscode":"04021000","countryCode":"CN","recentMonths":12}'

Query the next page:

bash

python scripts/customs_analysis_trends.py --params '{"hscode":"04021000","recentMonths":12,"cursor":"eyJpZCI6MX0="}'

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

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

2. Parameters:

   • hscode and recentMonths are required
   • countryCode is optional — omit to get global trends for the HS code

3. Cross-skill usage:

   • First use customs-analysis-hscode-search and customs-analysis-hscode-detail to find and understand the HS code
   • Combine with customs-analysis-area for geographic distribution, or customs-analysis-trade-percent for company-level breakdown

Notes

• hscode and recentMonths are required parameters
• Response contains both exportData and importData with monthly breakdowns
• month is in YYYYMM format (e.g., "202406")
• 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-analysis-area — Query trade area distribution by HS code
• customs-analysis-trade-percent — Query trade percentage by company
• customs-analysis-hscode-search — Search HS codes by product name and keywords
• customs-analysis-hscode-detail — Query HS code detail descriptions
• customs-overview-trend — Query import/export trade trends by month
• customs-overview-summary — Query trade overview summary (aggregated)
• customs-company-trends — Query company trade trends (monthly breakdown)
• customs-company-stats — Query company basic trade statistics
• customs-company-product-list — Query company product list
• upkuajing-customs-trade-company-search — Search customs trade companies