stage-2-pricing

Stage 2 -- Pricing Agents

Package: @otaip/agents-pricing

Fare rules, fare construction, tax calculation, offer building, corporate policy validation, and (coming soon) dynamic pricing and revenue management.

---

Agent 2.1 -- Fare Rule Agent

ID: 2.1 Class: FareRuleAgent Status: Implemented

Parses ATPCO fare rules (categories 1-20) into human-readable structured format using curated tariff snapshot data.

Input (FareRuleInput):

• fare_basis -- fare basis code
• carrier -- marketing carrier IATA code
• origin -- origin IATA code
• destination -- destination IATA code
• travel_date? -- ISO date for date-based rule filtering
• categories? -- specific ATPCO categories 1-50 (all if omitted)

Output (FareRuleOutput):

• rules -- FareRuleResult[] with parsed categories, penalty summary, advance purchase, min/max stay, seasonality
• total_rules -- count of matched rules
• valid_for_date -- whether fare is valid for the specified travel date
• in_blackout -- whether travel date falls in a blackout period

---

Agent 2.2 -- Fare Construction

ID: 2.2 Class: FareConstruction Status: Implemented

NUC × IROE construction with published TPM/MPM, Resolution 024d (HX/NX) rounding, and fail-closed HIP/BHC/CTM hooks. All financial math uses decimal.js.

Licensed IROE / 024d / TPM-MPM data are not shipped in the package. Pass them via data_sources. Missing IROE, TPM, or 024d → DomainInputRequired. Haversine-as-TPM and banker's rounding are banned.

KB: docs/knowledge-base/fare-construction-data-dependencies.md

Input (FareConstructionInput):

• journey_type -- 'OW' | 'RT' | 'CT' (one-way, round-trip, circle-trip)
• components -- fare components (origin, destination, carrier, fare basis, NUC amount)
• selling_currency -- ISO 4217 currency
• point_of_sale? -- country for IROE selection context
• data_sources? -- licensed { iroe, rounding_024d, mileage } (required for a constructed fare)