# Parsyl

> Parsyl Inc. is a Denver, Colorado based technology-enabled cargo insurance company for
> perishable and temperature-sensitive supply chains, with a London office and underwriting
> capacity placed at Lloyd's of London. It pairs IoT temperature and condition sensors with a
> data platform that turns shipment telemetry into risk insight, and sells that insight back as
> connected marine cargo insurance.

<!--
generated: 2026-08-26
method: generated
source: apis.yml + repo artifacts (API Evangelist enrichment pipeline). Parsyl publishes no
llms.txt of its own: https://www.parsyl.com/llms.txt returns HTTP 404 and
https://docs.parsyl.com/llms.txt returns HTTP 302 to a login gate.
-->

## What Parsyl sells

- [Cargo Insurance](https://www.parsyl.com/cargo-insurance): connected marine cargo cover for
  perishables, pharmaceuticals, seafood, food and semiconductors, up to $55M capacity.
- [Stock Throughput](https://www.parsyl.com/stp): combined transit-and-storage cover.
- [Stock and Excess Stock](https://www.parsyl.com/stock)
- [Legal Liability](https://www.parsyl.com/legal-liability)
- [Small Business Program](https://www.parsyl.com/small-business)
- [Risk Engineering](https://www.parsyl.com/risk-engineering)
- [Global Health](https://www.parsyl.com/global-health): vaccine and health-commodity cold chain
  programs, including work with Africa CDC and PFSCM.
- Parametric spoilage policy — described by Parsyl as the cargo market's first.

## API surface — read this before assuming an integration exists

Parsyl DOES have an API, and it is NOT publicly documented.

- API documentation: https://docs.parsyl.com/ — Parsyl's own docs host, fronted by CloudFront
  and gated by an Amazon Cognito user pool named `parsyl-api-docs`. Every path, including
  `/.well-known/*` and `/openapi.json`, returns HTTP 302 to `/auth/login`, which starts an
  OAuth 2.0 Authorization Code + PKCE flow (scope `openid email profile`). You need a Parsyl
  account to read anything.
- A Parsyl-controlled API host exists at `https://api.parsyl.io` (AWS API Gateway, TLS cert
  CN=api.parsyl.io). It answers every anonymous request with HTTP 403
  `{"message":"Missing Authentication Token"}`. No public Parsyl document names it as the base
  URL, so API Evangelist has deliberately NOT recorded it as the API's baseURL.
- Integration is relationship-scoped: Parsyl describes "custom API integration" for customers,
  and a [Data Partner Program](https://www.parsyl.com/media/media/data-partner-program-launch)
  that ingests telemetry from Berlinger, Copeland (formerly Emerson), Roambee, Sensitech and
  Tive. The route in is a conversation, not a signup.

## What Parsyl does NOT publish (all verified absent 2026-08-26)

- No OpenAPI, Swagger, AsyncAPI, GraphQL SDL, gRPC/Protobuf or WSDL contract.
- No MCP server (hosted or stdio) and no A2A agent card at `/.well-known/agent-card.json` or
  `/.well-known/agent.json` on any Parsyl host.
- No `/.well-known/security.txt`, `/.well-known/api-catalog` or OIDC discovery document.
- No client SDK on npm, PyPI or any other registry, and no CLI.
- No public pricing page, no published rate limits, no status page, no changelog, no public
  error reference, no sandbox and no developer portal.
- The GitHub organization https://github.com/parsyl is real (Parsyl Inc., 8 public repos) but
  contains only generic Go/Kotlin/Python infrastructure libraries — parquet, sqrl, go-postgis,
  go-athena, kable, tinyb, jira-lint, fuzzy-feature-foundry — not an API client.

## Security and compliance

- Parsyl states it completes a [SOC 2 Type II examination](https://www.parsyl.com/media-old/soc2-type2-exam)
  annually, evaluated by a licensed CPA firm, and lists two-factor authentication, encryption,
  documented security policies and a security training program among its controls.
- No trust center, no vulnerability disclosure policy and no bug bounty program were found.
- Domain security as probed: HTTPS with TLS 1.3 and HSTS (max-age 31536000) on both
  www.parsyl.com and docs.parsyl.com; SPF and DMARC present on parsyl.com with policy
  `quarantine`; no DNSSEC and no CAA records.

## Contact and legal

- Contact / support: https://www.parsyl.com/contact
- Claims: https://www.parsyl.com/claims — claims@parsyl.com
- For brokers: https://www.parsyl.com/brokers
- Resources and news: https://www.parsyl.com/media
- Terms and Conditions: https://www.parsyl.com/terms-and-conditions
- Privacy Policy: https://www.parsyl.com/privacy
- About: https://www.parsyl.com/about
- Careers: https://www.parsyl.com/careers

## About this file

This llms.txt was generated by [API Evangelist](https://apievangelist.com) from publicly
reachable Parsyl surfaces. It is a third-party profile, not a Parsyl publication, and it is not
endorsed by Parsyl. Corrections: https://github.com/api-evangelist/parsyl/issues