# Interlynked > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/interlynked - **Dataset:** https://optimly.ai/brand/interlynked.json - **Markdown:** https://optimly.ai/brand/interlynked/llms.txt - **Official website:** https://interlynked.com - **Slug:** interlynked - **Categories:** data-analytics-business-intelligence ## Overview - **Tagline:** Real-time wildfire intelligence, native predictive modeling, and operational decision support combined in one deployment-ready platform. It offers agency-grade reliability, insurance portfolio analysis, and is built by a team with deep domain expertise (responders, scientists, operators). Source: Brand's website (https://interlynked.com) · 2026-10-04 - **Description:** Interlynked provides real-time disaster intelligence, predictive models, and live dashboards to enhance disaster response, strengthen relief operations, and help insurers quantify risk, reduce claims, and plan smarter coverage, primarily focusing on wildfires. It offers two operational modules: one for fire departments and first responders, and another for insurance and risk teams. Source: Brand's website (https://interlynked.com) · 2026-10-04 ## Offerings - **Core capabilities:** - Real-time disaster intelligence system with live detection - AI-driven predictive spread modeling - and actionable decision support dashboards. Key capabilities include interactive live maps - dynamic risk assessment - custom alerts - unified data streams - multi-agency coordination - and API integrations. Source: Brand's website (https://interlynked.com) · 2026-10-04 - **Pricing:** Not specified Source: Brand's website (https://interlynked.com) · 2026-10-04 ## Audience - **Target industry:** Fire Departments, first responders, emergency management agencies, and government entities for incident response and resource allocation. Insurance and Risk Teams (underwriters, risk managers) for dynamic risk scoring, portfolio-level exposure analysis, and coverage strategy. Source: Brand's website (https://interlynked.com) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.