Map the upstream KSM and intermediate exposure that Indian APIs carry to China. Hidden behind India-origin labels at the API trade layer.
Of $3.50B in declared 2024 imports flowing into India for use as pharma intermediates, $2.50B (71.3%) originated in China. The next two origins, Thailand and the US, sit at 7.6% and 6.8%. The dependency is upstream and concentrated. Disruption to the China-to-India lane propagates into every downstream Indian formulation.
Type the INN. The AI agent pulls every active DMF holder for the molecule, partitioned by Indian-incorporated vs Chinese-incorporated.
Where a DMF lists intermediate manufacturing facilities, the country of the attested plant is recorded. Indian holders with Chinese intermediate plants surface as flagged rows.
Citation-anchored brief with the dependency share, all-Indian stack count, and a chip showing intermediate plant country.
An Indian-labelled API supplier may depend on a single Chinese KSM source. Without the upstream view, a buyer thinks they have India-only supply when the real risk sits one tier up.
Suppliers whose DMF lists only Indian intermediate plants are flagged separately. They are the resilience cohort against KSM disruption.
When the DMF attests to a specific Chinese intermediate plant (Changzhou Pharmaceutical, Zhejiang Apeloa, Zhejiang Tianyu), the chip names it. Country alone is too coarse for procurement risk work.
Facility attestation updates from FDA DMF amendments propagate monthly. New cross-attestations surface on the next refresh.
A real chat thread in PharmaDB. Type a question, the AI agent runs the tools, the answer lands as a saveable note.
pharmagraph_query Twenty molecules · share of Indian DMFs attesting at least one Chinese intermediate plant in the synthesis route.
The China intermediate dependency map is the upstream view that the API trade feed misses. PharmaDB joins DMF facility attestations to the plant catalog so Indian-labelled API supply with Chinese intermediate dependency surfaces as a flagged cohort. The view rests on api_docs, api_doc_facility_attestation, and plants. Refresh cadence is monthly.
The API trade feed captures the API-level export, which is the Indian holder shipping the finished active ingredient. The upstream intermediate (KSM, advanced intermediate) crosses the border earlier and shows on the intermediate trade lane, often misclassified as a chemical. Facility attestation in the DMF dossier is the cleanest cross-reference.
The flag is derived from DMF facility attestations where the holder lists intermediate plants by name and country. Confidence varies by holder: some DMFs are explicit, others list only the API plant. PharmaDB labels representative confidence on every row; live confidence is reserved for cases where the attestation is unambiguous.
Conservative. The figure counts only DMFs where the attestation explicitly names a Chinese intermediate facility. Indian holders that source Chinese KSMs informally (without naming the supplier in the dossier) are not in the 67%. The true exposure is likely higher.
Two reasons. First, a China-KSM disruption (regulatory, logistical, geopolitical) cascades to the Indian API supply that depends on it; the all-Indian stack cohort is the resilience pool. Second, regulators in the EU and US are increasingly asking dossiers to declare upstream sourcing; the cohort that can declare an all-Indian stack carries a regulatory advantage.
Yes. The same map applies to European holders with Chinese intermediates, US holders with Chinese intermediates, and so on. The Indian-with-Chinese case is the largest in the warehouse because India dominates observable API trade; the same methodology is regulator-agnostic.
Monthly. The FDA DMF amendment cycle publishes monthly. Facility attestation updates propagate on the next refresh; the catalog row carries an as-of timestamp on every result page.
Bring the molecule, the lane, or the supplier you're sourcing this week. The AI agent runs it on PharmaDB in 30 minutes. You keep the brief.