slug: citi provider: Citi generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 5 edges: - tag: Worldlinkservices spec_file: citi-worldlinkservices-api-openapi.yml capability_id: BC-210.40 capability_id_l1: BC-210 capability_name: Foreign Exchange Management confidence: 0.8 evidence: POST /worldlinkservices/v5/fx/bookfx WorldLink FX Booking; POST /worldlinkservices/v5/fx/raterequest WorldLink FX Rate Inquiry reason: Both operations are purely FX rate inquiry and FX deal booking, matching Foreign Exchange Management (exposure, hedging, settlement) in the treasury domain. - tag: Contract status inquiry spec_file: citi-contract-status-inquiry-api-openapi.yml capability_id: BC-210.40 capability_id_l1: BC-210 capability_name: Foreign Exchange Management confidence: 0.75 evidence: CitiConnect API now offers you WorldLink services of FX Contract Status Inquiry, FX rate enquiry, FX deal booking reason: The operation processContractStatus on /worldlinkservices/v1/fx/inquiry with FxDealInquiryRsp / FxGetDealOperationResponse schemas is FX deal (contract) status enquiry — squarely foreign-exchange exposure and deal administration. Only the single inquiry operation limits confidence. - tag: Fxgateway spec_file: citi-fxgateway-api-openapi.yml capability_id: BC-210.40 capability_id_l1: BC-210 capability_name: Foreign Exchange Management confidence: 0.75 evidence: '"Submit Standard Orders", "Market Order Synchronous Request", "Order Cancellation Asynchronous Request", "Quote Request and Quote Report Request API"; schemas FXMarketOrder_Rated, FXOrderCancel, FXBenchmarkOrder' reason: Operations quote, submit, report on and cancel FX orders — FX trade execution and settlement, which maps to Foreign Exchange Management. Deducted for the fact that this is dealer-side trading infrastructure rather than corporate FX exposure/hedging governance, which is how the capability is worded. - tag: WorldLink Cancel FX spec_file: citi-worldlink-cancel-fx-api-openapi.yml capability_id: BC-210.40 capability_id_l1: BC-210 capability_name: Foreign Exchange Management confidence: 0.75 evidence: POST /v1/fx/cancelfx cancelFx WorldLink Cancel; "complete cross-border payment and Foreign-Exchange (FX) service" reason: Cancelling a booked FX deal is an FX exposure/hedging-execution activity in the treasury domain; for the consuming corporate this realises Foreign Exchange Management. Single narrow operation keeps confidence moderate. - tag: WorldLink v3 spec_file: citi-worldlink-v3-api-openapi.yml capability_id: BC-210.40 capability_id_l1: BC-210 capability_name: Foreign Exchange Management confidence: 0.7 evidence: POST /v3/fx/raterequest WorldLink FX Rate Inquiry; POST /v3/fx/bookfx WorldLink FX Booking; POST /v3/payment/initiation reason: Two of three operations are FX rate inquiry and FX deal booking, which is Foreign Exchange Management; the third (payment initiation) is cash movement, creating some sub-capability ambiguity.