TradePulse: Global trade intelligence API. AI-synthesized tariff rates, HS code classification, FTA duty analysis, landed cost calculation, trade compliance guidance, sanctions screening, market entry analysis, a Coverage: Global Endpoints: • classify ($0.15): HS code classification • tariff ($0....
AI agents call tradepulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | Response language code (en, zh, ja, de, fr, es, ar, hi, etc.) |
mode | string | — | ocean | air | both (default: ocean) |
term | string | — | Incoterms 2020 rule — EXW | FCA | FAS | FOB | CFR | CIF | CPT | CIP | DAP | DPU | DDP |
topic | string | — | tariffs | fta | sanctions | wto | supply-chain | all |
value | string | — | Declared customs value in USD |
action | string | Yes | Which endpoint to call. Options: classify | tariff | landed | fta | sanctions | market | compliance | freight-rates | nearshore | supplier-risk | incoterms | ne |
checks | string | — | forced_labor | esg | sanctions | geo_risk | all (default: all) |
entity | string | — | Company or individual name to screen |
origin | string | — | Origin port city or country — e.g. Shanghai, Rotterdam, Los Angeles |
sector | string | — | textiles | electronics | food | chemicals | automotive | mining | any (default: any) |
country | string | — | Country to screen — e.g. Russia, Iran, Cuba, Myanmar, Belarus |
end_use | string | — | Stated end-use — affects license requirement |
Parameters from the server's own tool schema.
While TradePulse operates in a trade/financial domain and provides compliance-relevant intelligence, the tool itself is fundamentally a read-only information service. It retrieves and synthesizes trade data (tariffs, HS codes, FTA terms, sanctions lists) but does not execute trades, move money, or trigger irreversible actions.
From the tool's definition TradePulse provides intelligence retrieval endpoints: 'HS code classification', 'Tariff rates', 'landed cost calculation', 'FTA duty analysis', 'sanctions screening', 'market entry analysis', and 'export compliance guidance'.
Risk signalsAccepts file system path (destination) · High parameter count (26 properties)
Attacks that exploit this kind of access
TradePulse: Global trade intelligence API. AI-synthesized tariff rates, HS code classification, FTA duty analysis, landed cost calculation, trade compliance guidance, sanctions screening, market entry analysis, a Coverage: Global Endpoints: • classify ($0.15): HS code classification • tariff ($0.12): Tariff rates by HS code and country pair • landed ($0.15): Full landed cost calculator • fta ($0.15): Free Trade Agreement analyzer • sanctions ($0.12): Sanctions and trade restrictions screening • market ($0.15): Market entry intelligence • compliance ($0.15): Export compliance — EAR/ITAR/dual-use • freight-rates ($0.10): Live freight rate intelligence by lane • nearshore ($0.20): Nearshoring and reshoring advisor • supplier-risk ($0.15): Supplier country risk — UFLPA, ESG, and geopolitical • incoterms ($0.10): Incoterms 2020 decoder • news ($0.08): Trade policy intelligence. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
tradepulse accepts 12 parameters: lang, mode, term, topic, value, action, checks, entity, origin, sector, country, end_use. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for tradepulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
tradepulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tradepulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for tradepulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
tradepulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
tradepulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →