Institutional ingestion guide

BridgePoint provides pull-based public research feeds and can support authenticated partner delivery where an institution explicitly authorizes the connection. The public surface does not anonymously push payloads into third-party systems.

Recommended record envelope

{
  "bridgepoint_version": "5203",
  "record_type": "hazard_observation | property_exposure",
  "provider": "NOAA/NWS",
  "source_url": "https://...",
  "source_updated_at": "ISO-8601",
  "bridgepoint_first_seen_at": "ISO-8601",
  "source_to_bridgepoint_seconds": 83.65,
  "hazard_type": "FLOOD",
  "confidence": 0.91,
  "property_exposure_count": 1234,
  "interpretation_flags": {
    "damage_determination": false,
    "securities_instruction": false,
    "claims_decision": false
  }
}

Delivery surfaces available now

JSON, XML and RSS exposure feeds
JSON/CSV public-audit exports
OpenAPI discovery document
Settlement Lab shadow contract
GIS/BII embeds for site-owner integrations

Authorized enterprise delivery

For a signed partner integration, the same envelope can be delivered over authenticated HTTPS pull, signed webhook, S3/object delivery or a customer-specific queue. Authentication, rate limits, entitlement and source-license restrictions should be defined in the partner contract.

No “ingestion attack.” BridgePoint does not disguise payloads as errors, exploit intake forms, or force data into systems that have not authorized delivery. A financial platform can ingest the data when it deliberately connects to BridgePoint.

Partner delivery contract · Public Evidence Audit · OpenAPI · Settlement contract