For insurtech products and platforms

One enrichment layer. Fewer vendor seams.

Return COPE, valuation context, imagery, permits, Protection context, nearby exposures, reports, and transparent peril factors through one integration.

Read the API docs Plan a team evaluation

Use API, widgets, MCP, reports, or SOV processing. Review the documented request and response, then map one field set to your workflow.

GET /api/v1/score/?address=…Public API docs

Request · documented endpoint

GET https://app.perilscore.com/api/v1/score/?address=101%20Main%20St%2C%20Dallas%2C%20TX
Authorization: Bearer YOUR_API_KEY

Illustrative response fields

{
  "property": {
    "year_built": 1998,
    "construction_class_name": "Frame"
  },
  "replacement_cost": {
    "low": 475000,
    "base": 525000,
    "high": 590000,
    "confidence": "Medium"
  }
}

Representative excerpt from the public API docs. Values illustrate the documented response shape.

Stop stitching property context together.

Use one interface for the property context your submission, quoting, inspection, or underwriting product needs.

Property data

Construction, roof, age, area, permits, imagery, Protection context, and nearby exposures.

Valuation and risk

Estimated replacement cost context plus six transparent 0–10 natural-peril scores. Crime remains separate area context.

Delivery

Return structured data through API or MCP, embed a widget, generate reports, or process an SOV.

Without PerilScore

Five separate tools to source and manage

Separate contracts and implementation queues
Different schemas, coverage rules, and update cycles
More vendor logic inside your own product

With PerilScore

One property enrichment layer

One request and normalized response
Multiple delivery surfaces for different users
Available factors and source context preserved

Best fit

Products that need property enrichment inside the workflow.

Use PerilScore when users should stay in your quoting, intake, inspection, or underwriting surface instead of opening external lookup tools.

Limit

Coverage rules still need product design.

Source availability varies by address. Your application should expose confidence, fallback paths, and user override behavior.

Next action

Map one request and one response.

Start with the fields your users need back, then choose API, widget, MCP, reports, or SOV processing.

Ask your AI about PerilScore.

Compare product details, source context, and limitations with an AI assistant.