Intelligence · min plan: starter · ai (20u) · scope: write:ai · both
AI Trade Impact Analyze
Returns the same grounded decision payload used by the AI Trade Impact workspace, including checks, risks, opportunities, actions, evidence resolution, citations, and source links. A successful live call uses 20 API units plus depth credits: basic 5, advanced 10, deep 50, or dedicated 50. AI credits are waived when no chargeable AI output is delivered.
POST /v1/ai/impact-analyze
Required scope
write:ai
Weighted API units
20 per success
Minimum plan
starter
Rate-limit bucket
ai
AI credits
basic 5 · advanced 10 · deep 50 · dedicated 50
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| query | body | string | yes | Natural-language trade question. |
| entity | body | string | — | Optional entity or customer. |
| depth | body | string | — | basic, advanced, deep, or dedicated. |
Sample request
curl -X POST "https://getway.clearie.ai/v1/ai/impact-analyze" -H "Authorization: Bearer $CLEARIE_API_KEY" -H "Content-Type: application/json" -d '{"query":"Red Sea routing impact","depth":"basic"}'Sample response
{
"id": "an_01JTRADEIMPACT",
"query": "How could Red Sea disruption affect our India electronics imports?",
"entity": "Electronics import portfolio",
"generated_at": "2026-09-12T10:30:00Z",
"exposure_level": "elevated",
"active_events": 3,
"top_regions": [
"Red Sea",
"India",
"Southeast Asia"
],
"recent_context": "Verified route disruption and India import context indicate longer transit times and landed-cost pressure.",
"context_citations": [
"src_event_01",
"src_cbic_01"
],
"risk_factors": [
{
"id": "risk_01",
"title": "Transit delay",
"description": "Rerouting can extend lead time.",
"severity": "elevated",
"confidence": "high",
"timeline": "0-30d",
"drivers": [
"Carrier rerouting"
],
"citations": [
"src_event_01"
]
}
],
"opportunities": [
{
"id": "opp_01",
"title": "Alternate origin review",
"description": "Compare qualified suppliers on unaffected lanes.",
"timeline": "30-90d",
"confidence": "medium",
"citations": [
"src_event_01"
]
}
],
"recommendations": [
{
"id": "rec_01",
"title": "Reprice open purchase orders",
"detail": "Refresh freight and buffer assumptions before confirmation.",
"tier": "immediate",
"owner": "Trade operations",
"citations": [
"src_event_01"
]
}
],
"resilience_score": 6.4,
"resilience_confidence": "medium",
"exposure": {
"customers": [
{
"name": "Portfolio",
"share": 1,
"trend": "flat",
"note": "Portfolio-level request"
}
],
"lanes": [
{
"name": "Asia to India",
"share": 0.7,
"trend": "up",
"note": "Red Sea routing exposure"
}
],
"products": [
{
"name": "Electronics",
"share": 0.6,
"trend": "up",
"note": "Freight-sensitive imports"
}
]
},
"sectors": [
{
"sector": "Electronics",
"intensity": 0.72,
"direction": "headwind"
}
],
"analysis_checks": [
{
"id": "recent_trade_events",
"label": "Recent trade events",
"status": "completed",
"summary": "3 relevant events validated"
}
],
"markdown": "## Decision brief\\nReprice affected purchase orders and compare alternate lanes.",
"citations": [
"src_event_01",
"src_cbic_01"
],
"source_references": [
{
"id": "src_event_01",
"title": "Verified disruption notice",
"url": "https://www.cbic.gov.in/",
"publisher": "Official authority",
"source_type": "official",
"published_at": "2026-09-10T08:00:00Z",
"confidence": "high",
"freshness": "current",
"age_days": 2
}
],
"evidence_resolution": {
"search_mode": "getway_only",
"internal_source_count": 2,
"live_source_count": 0,
"official_source_count": 1,
"institutional_source_count": 1,
"secondary_source_count": 0,
"unknown_source_count": 0,
"current_source_count": 2,
"stale_source_count": 0,
"unknown_freshness_count": 0,
"sufficiency_score": 0.86,
"minimum_score": 0.4,
"target_score": 0.7,
"search_performed": false,
"search_queries": [],
"searched_at": null,
"coverage_gaps": [],
"source_tier_counts": {
"official": 1,
"institutional": 1
},
"chargeable": true,
"no_charge_reason": null,
"summary": "Grounded with current internal evidence."
},
"usage": {
"environment": "live",
"weighted_api_units": 20,
"api_units_charged": 20,
"sandbox_calls_charged": 0,
"ai_credits_scheduled": 5,
"ai_credits_charged": 5,
"depth": "basic",
"status": "charged",
"no_charge_reason": null
}
}Live response contract
Live calls require API-key authentication, write:ai scope, plan access, and available quota. Successful calls consume 20 weighted API units plus the selected depth's AI credits; failed responses release reservations. AI credits are waived when no chargeable AI output is delivered.
Sandbox sample response
Workspace try-it calls use isolated representative sandbox records. They are for integration validation, not production filing.
Error examples
401 invalid key · 403 missing scope or plan · 429 quota/rate limit · 404 no verified data where applicable.
Response schema
Try this API live in the workspace
The in-app try-it console runs against the isolated deterministic sandbox repository. It never reads live customer or reference records.