API

PropsOracle is monetized through a subscription API for platforms that need to manage player-prop settlement risk before finalizing prediction markets.

The public on-chain layer is intentionally minimal: it publishes finalized results only. It does not publish risk signals, trigger reasons, stat-change diagnostics, or postponement explanations. Those fields are paid API data.

What the API answers

For a specific player-prop market, the API answers:

Is this market safe to settle now, or should settlement remain pending because the underlying stat still has correction risk?

The API is designed for prediction-market operators, exchanges, and protocols that need a deterministic settlement gate between the final buzzer and irreversible payout.

Core response

A market-level risk response can include:

{
  "ids": {
    "props_oracle": {
      "market_id": "0x...",
      "canonical_event_id": "0x...",
      "game_id": 42
    }
  },
  "market": {
    "status": "pending",
    "final_market_result": null,
    "final_stat_value": null
  },
  "risk": {
    "risk_level": "MEDIUM",
    "recommended_settlement_time": "2026-05-13T05:30:00Z",
    "trigger_codes": ["ASSIST_ATTRIBUTION_AMBIGUITY"]
  }
}

Settlement statuses

Status	Meaning	Typical client action
`pending`	The game or market has not reached a final settlement state	Keep the local market pending
`resolved`	PropsOracle has a final market result and final stat value	Resolve according to the returned result
`void`	The market cannot be settled under the market rules	Void or apply your fallback policy
`manual_review`	Automated settlement is unavailable	Use platform fallback policy

API products

Settlement API

Returns the current settlement state for a specific market:

PropsOracle market_id
external_provider + external_market_id

Use this before resolving a market or paying out positions. Paid callers can use mapped Kalshi or Polymarket IDs and receive the corresponding PropsOracle IDs in the response.

Event lookup

Returns the mapped PropsOracle event and currently mapped PropsOracle markets for a paid external event lookup:

external_provider + external_event_id

Use this for discovery when a platform starts from an event page rather than an individual market.

Webhooks

Webhooks are not part of v1. The current consumption model is polling: clients call the paid API with the market or event identifier they already have, then settle only after the response reports a resolved market.

Evidence API

Returns the private settlement-risk evidence package: operator snapshots, trigger codes, and stat-change history. This is for operators, auditors, and support teams. It is not part of the public UMA claim.

Public result vs paid API

Data	Public Arweave / UMA / on-chain	Paid API
Final market result	Yes	Yes
Final stat value	Yes	Yes
Risk level	No	Yes
Postponement reason	No	Yes
Trigger codes	No	Yes
Stat-change history	No	Yes
Recommended settlement time	No	Yes
Evidence package for operators	No	Yes
External event and market mappings	No	Yes

The public result may simply appear later. It should not explain why it was postponed. The paid API explains the delay and gives the client enough information to manage user-facing settlement states.

Recommended platform flow

Query the paid API using the identifier your platform already has: PropsOracle market_id, Kalshi market ID, or Polymarket market ID.
If market.status is pending, keep the local market pending. If it is void, apply your platform fallback or voiding policy. If it is manual_review, apply your platform fallback policy.
If market.status is resolved and risk.risk_level is acceptable for your policy, settle from market.final_market_result or market.final_stat_value.
If risk.risk_level is HIGH or CRITICAL, hold or route to manual review according to your own settlement policy.
Optionally verify the UMA assertion and Arweave evidence using the returned PropsOracle IDs.

PropsOracle does not price markets, hold funds, grade parlays, compute multipliers, or decide your payout rules. It provides the settlement-risk signal and final result data your platform uses inside its own resolution policy.