What is Pricing Intelligence?
Pricing Intelligence is an advanced AI-powered platform that analyzes, reasons about, and extracts insights from SaaS pricing models. By combining Large Language Models (LLMs) with rigorous Constraint Satisfaction Problem (CSP) solvers, it provides accurate, mathematically grounded answers to complex pricing questions. This project is part of the research contributions from the paper “Pricing Intelligence: Rethinking IS Engineering in Volatile SaaS Environments”.Key Capabilities
Pricing Intelligence enables you to:Extract Pricing Data
Automatically extract structured pricing models (Pricing2Yaml format) from raw website URLs using the A-MINT API.
Analyze Configurations
Perform mathematical analysis of pricing configurations including validity checks and feature combinations.
Optimize Plan Selection
Find optimal plans based on specific requirements like “Cheapest plan with SSO and 50 users”.
Natural Language Interface
Interact with the Harvey agent through a conversational chat interface powered by the ReAct pattern.
Architecture Overview
The platform consists of six microservices working in concert:Core Services
| Service | Technology | Purpose |
|---|---|---|
| Harvey API | Python/FastAPI | AI Agent implementing the ReAct pattern to orchestrate tools and answer queries |
| MCP Server | Python | Implements Model Context Protocol, exposing tools like subscriptions, optimal, and iPricing |
| Analysis API | Node.js/TypeScript | Handles core pricing analysis, validation, and statistics logic |
| CSP Service | Java/Choco | Wraps the Choco constraint solver for mathematical optimization |
| Amint API | Python | Extracts pricing data from unstructured sources and converts to Pricing2Yaml format |
| Frontend | React/Vite | Provides the chat interface and visualization |
The Harvey Agent
Harvey is a specialized AI agent that follows the ReAct (Reasoning + Acting) pattern:Grounding: Harvey verifies feature names and limits against actual YAML data before querying tools, significantly reducing hallucinations.
- Optimization: Delegates mathematical operations and logic to the Analysis API rather than relying on LLM calculations
- Context Awareness: Can compare multiple pricing models simultaneously (e.g., “Compare HubSpot vs. Salesforce”)
- Tool Orchestration: Intelligently chains MCP tools to answer complex multi-step questions
MCP Tools
The system exposes powerful tools via the Model Context Protocol:iPricing
iPricing
Downloads and structures pricing data from a URL, converting unstructured web content into the standardized Pricing2Yaml format.
subscriptions
subscriptions
Enumerates all valid plan configurations given a set of filters, exploring the entire configuration space.
optimal
optimal
Finds the best (cheapest/most expensive) configuration satisfying user constraints using CSP optimization.
validate
validate
Checks if a pricing model is mathematically consistent and identifies configuration conflicts.
summary
summary
Provides high-level statistics about a pricing model including feature counts, price ranges, and usage limits.
Use Cases
Plan Optimization
Find the most cost-effective plan for specific requirements:Multi-Product Comparison
Compare pricing across competing SaaS products:Configuration Validation
Ensure pricing models are mathematically consistent:How It Works
User asks a pricing question
Submit a natural language query through the frontend or API, optionally including a pricing page URL.
Harvey analyzes the request
The Harvey agent parses the question and determines which MCP tools to invoke.
Data extraction (if needed)
If a URL is provided, the
iPricing tool calls A-MINT to extract structured pricing data.CSP analysis
The Analysis API and CSP Service perform mathematical computations to find optimal configurations.
Pricing2Yaml Format
All pricing data is represented in a standardized YAML schema that captures:- Plans: Base subscription tiers with monthly/annual pricing
- Features: Boolean or enumerated capabilities (domain features, integrations, support levels)
- Usage Limits: Numeric constraints (users, storage, API calls, etc.)
- Add-ons: Optional extensions with additional costs
- Constraints: Dependencies and mutual exclusions between features
Next Steps
Quickstart
Get up and running in 5 minutes with Docker Compose
Installation
Detailed setup and configuration guide
Harvey API
Explore the Harvey API and chat interface
Architecture
Deep dive into system design and data flow