PMPS

Cover Block

PUBLIC

Field	Value
Name	PMPS
Tagline	"The Probability Rails for the Outcome Economy" [pmps.ai]
Business Model	API / Developer Platform
Industry	Fintech
Technology Type	AI / Machine Learning

Links

PUBLIC

• Website: https://www.pmps.ai/

Executive Summary

PUBLIC

PMPS is positioning itself as infrastructure for what its website calls the "outcome economy," a category in which predictive signals are packaged into financial instruments rather than consumed as standalone analytics. The company describes its product as software that "turns predictions into programmable financial primitives," with stated use cases spanning outcome-based incentives, dynamic pricing, and risk routing across commerce and capital markets [pmps.ai]. That framing places PMPS at the intersection of three active investment themes: AI-driven forecasting, programmable money infrastructure, and prediction-market mechanics moving into enterprise contexts. The company's public footprint is presently thin: there is no disclosed funding round, no named founder, and no confirmed headquarters in the sources reviewed for this report. The absence of a LinkedIn company record, Crunchbase profile, or press coverage in the captured sources is itself a signal that PMPS is at pre-seed or stealth stage. For investors tracking the prediction-infrastructure category, the next twelve to eighteen months should clarify whether PMPS converts its conceptual positioning into a launched product with named design partners, and whether a founding team with relevant quantitative finance or ML infrastructure experience is disclosed. Until then, this report should be read as a category briefing anchored on a single primary source rather than a traction-validated company assessment.

Data Accuracy: RED -- Single primary source (company website) with no independent third-party corroboration of team, funding, or traction.

Taxonomy Snapshot

Axis	Value
Business Model	API / Developer Platform
Industry / Vertical	Fintech
Technology Type	AI / Machine Learning

Company Overview

PUBLIC

Public information on PMPS is limited to what the company publishes on its own website at pmps.ai, which presents the firm as a provider of "probability rails for the outcome economy" [pmps.ai]. The site frames the product as infrastructure rather than an application, suggesting the intended buyer is a developer, a fintech platform, or a capital-markets desk rather than an end consumer. No founding date, incorporation state, or registered legal entity name appears in the sources reviewed.

No founder names, executive bios, or investor relationships were surfaced in any of the secondary sources captured during research, including searches against LinkedIn, Crunchbase, and Pitchbook surfaces. The headquarters location is likewise undisclosed in the public record reviewed. A separate New York-based company called Primitives appears in PitchBook [PitchBook, 2025] and an India-based showcase page named Fintech Primitives by Cybrilla appears on LinkedIn, but neither is the same entity as PMPS, and they should not be conflated.

Given the absence of press releases, hiring announcements, or a populated careers page, PMPS reads as either pre-launch stealth or a very early commercial deployment limited to private design partners. Investors evaluating the company should treat the company overview as a placeholder pending direct outreach to confirm entity status, founding team, and corporate history.

Data Accuracy: RED -- Company website only; no third-party corroboration of founding date, HQ, or legal entity.

Product and Technology

MIXED

The product, as described on the company website, takes machine-generated predictions (the probability that an event will occur, that a customer will repay, that a shipment will arrive on time, that a contract will perform) and converts them into what PMPS calls "programmable financial primitives" [pmps.ai]. In practice, that language describes objects an application can price, settle, or hedge against programmatically, similar to how stablecoin infrastructure converted dollar balances into composable on-chain primitives. The three named use cases are outcome-based incentives (paying suppliers, employees, or counterparties contingent on a measured result), dynamic pricing (adjusting prices in response to a continuously updated probability), and risk routing (directing exposure to the counterparty best positioned to underwrite it) [pmps.ai].

No public documentation, SDK, API reference, pricing page, or sandbox URL was identified in the sources reviewed, so the technical implementation is not verifiable from the outside. The phrase "AI / Machine Learning" in the company taxonomy reflects the website's emphasis on prediction as the input layer rather than confirmed disclosure of model architecture, training data, or inference infrastructure (inferred from website copy). There is no captured evidence of a GitHub organization, an open-source release, or third-party integrations.

For investors, the product question that matters most is whether PMPS sits at the prediction-generation layer (competing with forecasting and ML platforms), the settlement-and-contracts layer (competing with programmable-payments and smart-contract platforms), or the marketplace layer (competing with prediction exchanges and parametric insurance providers). The website's language straddles all three, and clarification will likely come only from a launched product or a public design-partner case study.

Data Accuracy: RED -- Product description sourced exclusively from company marketing copy; no independent technical validation.

Market Research and Opportunity

PUBLIC

The market PMPS is addressing matters now because three previously separate technology stacks (machine-learning forecasting, programmable payments, and prediction markets) are converging into a single workflow in which a probability is priced, contracted, and settled inside one system.

No third-party TAM, SAM, or SOM figure for "programmable financial primitives" or the "outcome economy" appears in the sources captured for this report, and the category itself is not yet a recognized line item in the major analyst taxonomies. As an analogous reference, the broader fintech-infrastructure and embedded-finance category has attracted sustained venture investment, and prediction-market platforms moved into mainstream regulatory and media discussion through 2024 and 2025. Investors should treat any sizing claim for PMPS specifically as estimated until a credible third-party report names the segment.

Demand drivers cited or implied by the company's positioning include the maturation of enterprise ML forecasting (which produces a steady supply of usable probabilities), the growth of usage-based and outcome-based contracting in B2B software, and the expansion of parametric structures in insurance and supply-chain finance. Adjacent or substitute markets include parametric insurance providers, prediction exchanges such as those that gained regulatory clarity in U.S. event-contracts markets through 2024 to 2025, dynamic-pricing engines used in travel and e-commerce, and smart-contract settlement infrastructure. Each of these is an independently funded category, which both validates investor appetite for the underlying primitives and raises the question of whether "programmable financial primitives" is a horizontal layer above them or a new vertical alongside them.

Regulatory forces are material. Outcome-based incentives that pay contingent on measured events sit close to definitions of derivatives, insurance, and gaming depending on jurisdiction and structure. Any platform that routes risk between counterparties will at some point intersect CFTC, state insurance regulator, or equivalent international oversight. That regulatory surface is a barrier to entry for the company that clears it first and a meaningful execution risk for everyone, PMPS included.

Data Accuracy: RED -- Category framing supported by company website only; no third-party market sizing report cited.

Competitive Landscape

MIXED

No direct competitors to PMPS are named in any of the sources captured for this report, so the competitive analysis below is structured by adjacent category rather than by named rival.

The competitive map for an infrastructure provider in this space breaks into four adjacent segments. First, prediction and forecasting platforms (the layer that produces the probabilities PMPS would consume) include large cloud ML services and specialized forecasting vendors; these are upstream suppliers more than rivals, but any of them could extend downward into financial primitives. Second, programmable-payments and smart-contract infrastructure providers offer the settlement rails that contingent contracts ultimately require; if PMPS does not own this layer, it depends on it. Third, prediction-market and event-contract exchanges have built regulated venues for trading binary outcomes and represent the most direct conceptual analogue to "turning predictions into financial primitives," though their model is exchange-based rather than embedded-API. Fourth, parametric insurance and structured-product providers have spent the last decade building outcome-contingent contracts for weather, flight delay, and supply-chain risk, and they are the incumbent buyers of the kind of primitive PMPS describes.

Where PMPS could establish a defensible edge, on the evidence available today, is in being the horizontal API layer that sits between prediction producers and settlement venues, abstracting away the contract construction, pricing logic, and counterparty routing. That edge would be durable if the company accumulates a library of standardized primitives that downstream developers integrate against (a network effect comparable to early payments APIs) and perishable if larger platforms in adjacent segments add equivalent functionality before PMPS reaches escape velocity. The company's public footprint, with no disclosed funding, team, or design-partner case studies, means none of this edge is yet evidenced.

Where PMPS is most exposed is on two axes. The first is regulatory: a well-capitalized event-contract exchange operating under existing CFTC oversight can offer a similar economic outcome inside an already-licensed venue, which is a channel a pre-seed infrastructure provider cannot easily match. The second is distribution: embedded-finance and payments platforms with existing developer footprints can ship a "contingent payment" feature to thousands of fintechs overnight, and PMPS would need to either partner with or out-execute them. The most plausible eighteen-month scenario is bifurcated: the winner if regulated event-contract venues remain narrow in product scope is an independent infrastructure layer like PMPS that serves builders who want embedded outcome logic without exchange membership; the loser if a major payments or smart-contract platform ships a competing primitives SDK is the standalone infrastructure startup that has not yet locked in design partners.

Data Accuracy: RED -- No named competitors in source material; analysis is category-based and inferential.

Opportunity

PUBLIC

If PMPS executes against the positioning it has staked out, the prize is becoming the default API layer for contingent financial logic across commerce and capital markets.

The headline opportunity. The single largest outcome PMPS could plausibly become is the Stripe-equivalent of outcome-contingent contracts: the developer-facing infrastructure that any application reaches for when it needs to price, issue, or settle a payment, incentive, or hedge whose value depends on a future probability. The cited evidence that makes this reachable rather than aspirational is narrow but pointed: the company's own framing identifies three discrete enterprise use cases (incentives, dynamic pricing, risk routing) that today are each solved with bespoke contract engineering inside individual firms [pmps.ai]. Any horizontal primitive that compresses that bespoke work into an API call is the kind of abstraction that historically captures durable category share, provided it ships before larger adjacent platforms add the same functionality natively.

Growth scenarios. The plausible paths to scale break into three named scenarios.

Scenario	What happens	Catalyst	Why it's plausible
Embedded primitives for fintech	PMPS becomes the contingent-payment SDK that vertical fintechs and embedded-finance platforms integrate by default	A reference integration with a recognized embedded-finance or payments platform	The company explicitly names commerce as a target surface [pmps.ai]
Capital-markets risk routing	PMPS wins adoption at trading desks and structured-product groups that need programmatic counterparty selection	A design-partner case study with a buy-side or insurance counterparty	Capital markets is named as a target surface [pmps.ai]
Outcome-incentive standard	PMPS becomes the rails for performance-based supplier, employee, and channel-partner contracts in B2B software	A multi-tenant rollout inside a major SaaS vendor's partner program	Outcome-based incentives are the first named use case [pmps.ai]

What compounding looks like. The flywheel for an infrastructure platform of this shape has three reinforcing loops. First, every primitive PMPS standardizes (a contingent payment, a probability-weighted price, a routed risk transfer) becomes a reusable building block that lowers integration cost for the next customer, which is the same compounding logic that drove early payments APIs. Second, transaction data flowing through the platform becomes pricing intelligence that improves the quality of the probabilities and the fairness of the routing, a data moat that is hard for a pure-software competitor to replicate without comparable volume. Third, developer mindshare in a new category tends to consolidate around the first credible API, and the documentation, SDKs, and reference integrations that follow create distribution lock-in. None of these loops is yet evidenced in the public record for PMPS, so each remains a thesis rather than a measured advantage.

The size of the win. A credible public comparable for the upper-bound outcome is the payments-infrastructure category, where the largest private and public players carry valuations in the tens of billions of dollars and revenue multiples that reflect deep developer lock-in. A more conservative comparable is the parametric-insurance and structured-product infrastructure category, which has produced multiple venture-scale outcomes in the high hundreds of millions to low billions of dollars in enterprise value. If PMPS reaches the embedded-primitives scenario above and captures even a small share of contingent-contract flow, the resulting business would sit in the parametric-infrastructure comparable range (scenario, not a forecast). If it reaches the broader outcome-incentive standard scenario across B2B software, the comparable migrates toward the payments-infrastructure range (scenario, not a forecast). Both outcomes require the company to first clear the basic disclosure threshold of a named team, a funded round, and a launched product, none of which is yet present in the public record.

Data Accuracy: RED -- Opportunity framing extrapolated from company website positioning and analogous public categories; no PMPS-specific traction or sizing data available.

Sources

PUBLIC

1. [pmps.ai] PMPS, The Probability Rails for the Outcome Economy | https://www.pmps.ai/

2. [PitchBook, 2025] Primitives (Social/Platform Software) Company Profile | https://pitchbook.com/profiles/company/489267-19

3. [LinkedIn] Fintech Primitives (by Cybrilla) showcase page | https://in.linkedin.com/showcase/fintech-primitives