HelloSafe website screenshot

HelloSafe

HelloSafe distributes travel insurance through APIs, under the Atlas platform at atlas.hellosafe.com. The Travel Insurance API returns multi-insurer pricing, tracked attributed links and a pre-sale coverage assessment, aimed at travel agencies, tour operators, OTAs, booking engines and travel apps. A second surface, the Coach API, sits alongside it. The contract is an OpenAPI 3.1 document of 4 operations and 8 schemas, and requests are HMAC-SIGNED rather than bearing a plain API key — three headers, AtlasKeyId, AtlasTimestamp and AtlasSignature, which is materially stronger than what most providers this size ship.

HelloSafe publishes 3 APIs on the APIs.io network: Conversion API, Links API, and Quotes API. Tagged areas include Travel Insurance, Insurance Distribution, Pricing, and Travel.

🌐 Visit website 📡 Source on GitHub
31.3/100 thin ▬ flat Agent 49/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-09-21 · rubric v0.22.0
2 APIs
Travel InsuranceInsurance DistributionPricingTravel

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Insurance Distribution Management
BC-2110
LinksQuotes
POST /api/v1/travel/quotes POST /api/v1/travel/links

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-21 · rubric v0.22.0
Composite quality — 31.3/100 · thin
Contract Quality 10.9 / 19
Developer Ergonomics 3.9 / 15
Access Clarity 5.1 / 15
Operational Transparency 0.0 / 10
Contract Governance 0.0 / 9
Discoverability 4.7 / 8
Regulatory Posture 3.2 / 15
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 49/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 6 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hellosafe: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

HelloSafe Conversion API

Server-to-server conversion postback.

HelloSafe Links API

Turn a chosen offer into a tracked, attributed subscription link.

HelloSafe Quotes API

Price a trip and read the catalogue vocabulary.

Resources

Get Started 2

Portal, sign-up, and the first successful call

Onboarding
Onboarding
 DeveloperPortal
DeveloperPortal

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Company 1

The organization behind the API

Website
Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap
CapabilityMap
 APIsJSON
APIsJSON

Source (apis.yml)

apis.yml Raw ↑ 
aid: hellosafe
name: HelloSafe
description: HelloSafe distributes travel insurance through APIs, under the Atlas platform at atlas.hellosafe.com. The Travel
  Insurance API returns multi-insurer pricing, tracked attributed links and a pre-sale coverage assessment, aimed at travel
  agencies, tour operators, OTAs, booking engines and travel apps. A second surface, the Coach API, sits alongside it. The
  contract is an OpenAPI 3.1 document of 4 operations and 8 schemas, and requests are HMAC-SIGNED rather than bearing a plain
  API key — three headers, AtlasKeyId, AtlasTimestamp and AtlasSignature, which is materially stronger than what most providers
  this size ship.
type: Index
url: https://raw.githubusercontent.com/api-evangelist/hellosafe/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
created: '2026-08-25'
modified: '2026-08-25'
specificationVersion: '0.23'
tags:
- Travel Insurance
- Insurance Distribution
- Pricing
- Travel
tags_raw:
- travel insurance
- insurance distribution
- pricing
- travel
apis:
- aid: hellosafe:hellosafe-conversion-api
  name: HelloSafe Conversion API
  description: Server-to-server conversion postback.
  humanURL: https://atlas.hellosafe.com/platform/api
  baseURL: https://atlas.hellosafe.com/api/v1/travel
  tags:
  - Conversion
  properties:
  - type: OpenAPI
    url: openapi/hellosafe-conversion-api-openapi.yml
  - type: APIReference
    url: https://atlas.hellosafe.com/openapi.json
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/api
  - type: Onboarding
    url: well-known/hellosafe-api-onboarding.json
  - type: SignUp
    url: https://atlas.hellosafe.com/signup
  - type: TermsOfService
    url: https://atlas.hellosafe.com/legal/terms
  - type: PrivacyPolicy
    url: https://atlas.hellosafe.com/legal/privacy
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/coach
- aid: hellosafe:hellosafe-links-api
  name: HelloSafe Links API
  description: Turn a chosen offer into a tracked, attributed subscription link.
  humanURL: https://atlas.hellosafe.com/platform/api
  baseURL: https://atlas.hellosafe.com/api/v1/travel
  tags:
  - Links
  properties:
  - type: OpenAPI
    url: openapi/hellosafe-links-api-openapi.yml
  - type: APIReference
    url: https://atlas.hellosafe.com/openapi.json
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/api
  - type: Onboarding
    url: well-known/hellosafe-api-onboarding.json
  - type: SignUp
    url: https://atlas.hellosafe.com/signup
  - type: TermsOfService
    url: https://atlas.hellosafe.com/legal/terms
  - type: PrivacyPolicy
    url: https://atlas.hellosafe.com/legal/privacy
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/coach
- aid: hellosafe:hellosafe-quotes-api
  name: HelloSafe Quotes API
  description: Price a trip and read the catalogue vocabulary.
  humanURL: https://atlas.hellosafe.com/platform/api
  baseURL: https://atlas.hellosafe.com/api/v1/travel
  tags:
  - Quotes
  properties:
  - type: OpenAPI
    url: openapi/hellosafe-quotes-api-openapi.yml
  - type: APIReference
    url: https://atlas.hellosafe.com/openapi.json
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/api
  - type: Onboarding
    url: well-known/hellosafe-api-onboarding.json
  - type: SignUp
    url: https://atlas.hellosafe.com/signup
  - type: TermsOfService
    url: https://atlas.hellosafe.com/legal/terms
  - type: PrivacyPolicy
    url: https://atlas.hellosafe.com/legal/privacy
  - type: Documentation
    url: https://atlas.hellosafe.com/platform/coach
common:
- type: CapabilityMap
  url: capabilities/hellosafe-capability-edges.yml
  name: HelloSafe Business Capability Map
- type: APIsJSON
  url: well-known/hellosafe-provider-apis.json
- type: Onboarding
  url: well-known/hellosafe-api-onboarding.json
- type: LLMsTxt
  url: llms/hellosafe-llms.txt
- type: Website
  url: https://hellosafe.com
- type: DeveloperPortal
  url: https://atlas.hellosafe.com/platform/api
maintainers:
- FN: HelloSafe Atlas
  email: atlas@hellosafe.com
  url: https://atlas.hellosafe.com
x-provenance:
  added: '2026-08-25'
  method: searched
  source: https://atlas.hellosafe.com/.well-known/apis.json
  note: 'Submitted via apis.io/add on 2026-08-25 and auto-published by the gate at rating 71 (exemplar). The submitted APIs.json
    URL is CORRECT — it points at /.well-known/apis.json, which returns application/json against a control path that returns
    a real 404. Third submission in a week whose declared pointer actually resolved, after Southend and YouWork Agent. Every
    declared property was fetched: the OpenAPI (3.1, 4 paths, 8 schemas), a machine-readable api-onboarding document carrying
    aod, provider, maturity, account, registration, authentication, credentials and scopes, and an llms.txt. Only /platform/api
    308-redirects rather than serving directly, which is why the record points at the URL and not a saved copy. WORTH NOTING
    ON AUTHENTICATION. This API is not bearer-token or plain-API-key. It uses three headers — AtlasKeyId, AtlasTimestamp and
    AtlasSignature — i.e. HMAC request signing with a timestamp, which resists replay in a way a static key does not. Very
    few providers at this size ship that, and it is the kind of thing the rubric should be crediting. SLUGGED FROM THE COMPANY,
    NOT THE SUBDOMAIN. The submission is "HelloSafe Atlas" and everything is served from atlas.hellosafe.com, but the company
    is HelloSafe on hellosafe.com, which resolves and returns 200. Atlas is the API platform, and the two APIs sit inside
    the company record — the same shape as YouWork Agent / Scopewise. Their apis.json declares specificationVersion 0.18,
    which is several revisions behind current. Recorded, not corrected: it is their document.'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/hellosafe"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/hellosafe/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/hellosafe/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.