180 Insurance

180 Seguros (180 Insurance) is the first tech-native insurer in Brazil, an SUSEP-authorized insurtech that lets fintechs, digital banks, credit cooperatives and other financial and non-financial businesses embed insurance into their own products through a single API — the Sagas API. The platform covers the full insurance lifecycle: product/combo listing, quotation (cotação), proposal (proposta), sale/policy issuance (venda), endorsements, renewals (renovações) and claims (sinistros), plus HMAC-signed webhooks for real-time visibility. Authentication is OAuth2 client-credentials via Auth0, errors follow RFC 9457 problem-details, and the company publishes a security posture including AICPA SOC 2, LGPD and SUSEP Circular 638 compliance. 180 Seguros is backed by 8VC, Monashees, Dragoneer, Atlantico and Canary, and was added to the API Evangelist network as an 8VC portfolio company.

180 Insurance publishes 7 API contracts indexed on the APIs.io network, including Cotações API, Produtos API, Propostas API, and 4 more. Tagged areas include Company, Insurtech, Insurance, Embedded Insurance, and Brazil.

The 180 Insurance catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

180 Insurance’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 26 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

48.0/100 developing ▬ flat Agent 44/100 agent ready Front door AI 2/6 trace Heartbeat 17/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 published contract 2 Agent Skills

Company Insurtech Insurance Embedded Insurance Brazil Fintech Webhook

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 48.0/100 · developing

Contract Quality 11.0 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 3.9 / 15

Operational Transparency 1.8 / 10

Contract Governance 3.2 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 44/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/180-insurance/"><img src="https://apis.io/badge/180-insurance/card.svg" alt="180 Insurance on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 26.3 — up to +14.7 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points
Contract Quality scores 58.4 — up to +10.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/180-insurance/apis.yml: open an issue on github.com/api-evangelist/180-insurance to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Brazil BCB Authorized Institutions (Banco Central do Brasil register beyond Pix)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 7

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

180 Insurance Cotações API

The Cotações API from 180 Insurance — 2 operation(s) for cotações.

180 Insurance Produtos API

The Produtos API from 180 Insurance — 1 operation(s) for produtos.

180 Insurance Propostas API

The Propostas API from 180 Insurance — 7 operation(s) for propostas.

180 Insurance Renovações API

The Renovações API from 180 Insurance — 3 operation(s) for renovações.

180 Insurance Sinistros API

The Sinistros API from 180 Insurance — 8 operation(s) for sinistros.

180 Insurance Vendas API

The Vendas API from 180 Insurance — 6 operation(s) for vendas.

180 Insurance Webhooks API

The Webhooks API from 180 Insurance — 3 operation(s) for webhooks.

Scroll for all 7

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Quote to policy (cotação → proposta → venda)

AGENT SKILL

Subscribe to and verify 180 Seguros webhooks

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

180 Insurance Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

180 Insurance API Rules

11 rules · 7 errors 2 warnings 2 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

180 Insurance Authentication

oauth2 · 1 scheme

SECURITY

180 Insurance Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

180 Insurance Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

180 Insurance Agentic Access

33 operations · 20 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

WellKnown

LLMsTxt

AgentSkill

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Spectral

Vocabulary

Conventions

ErrorCatalog

Webhooks

Lifecycle

Conformance

DataModel

Scroll for all 8

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

OAuthScopes

Authentication

Compliance

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Deprecation

Deprecation

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: 180-insurance
name: 180 Insurance
description: '180 Seguros (180 Insurance) is the first tech-native insurer in Brazil, an SUSEP-authorized insurtech that lets
  fintechs, digital banks, credit cooperatives and other financial and non-financial businesses embed insurance into their
  own products through a single API — the Sagas API. The platform covers the full insurance lifecycle: product/combo listing,
  quotation (cotação), proposal (proposta), sale/policy issuance (venda), endorsements, renewals (renovações) and claims (sinistros),
  plus HMAC-signed webhooks for real-time visibility. Authentication is OAuth2 client-credentials via Auth0, errors follow
  RFC 9457 problem-details, and the company publishes a security posture including AICPA SOC 2, LGPD and SUSEP Circular 638
  compliance. 180 Seguros is backed by 8VC, Monashees, Dragoneer, Atlantico and Canary, and was added to the API Evangelist
  network as an 8VC portfolio company.'
url: https://raw.githubusercontent.com/api-evangelist/180-insurance/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://files.readme.io/21b0f8e-small-180_seguros_logo.jpeg
x-type: company
x-source: vc-portfolio
x-backed-by:
- 8vc
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-17
tags:
- Company
- Insurtech
- Insurance
- Embedded Insurance
- Brazil
- Fintech
- Webhook
tags_raw:
- Company
- Insurtech
- Insurance
- Embedded Insurance
- Brazil
- Fintech
- API
- Webhooks
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/180-insurance-agentic-access.yml
- type: Spectral
  url: rules/180-insurance-rules.yml
- type: Vocabulary
  url: vocabulary/180-insurance-vocabulary.yml
- type: Deprecation
  url: lifecycle/180-insurance-lifecycle.yml
- type: Hosts
  url: hosts/180-insurance-hosts.yml
- type: Vendors
  url: vendors/180-insurance-vendors.yml
- type: OAuthScopes
  url: scopes/180-insurance-scopes.yml
- url: https://180s.com.br/feed/
  type: BlogRSS
- type: Website
  url: https://180s.com.br
- type: DeveloperPortal
  url: https://docs.180s.com.br/reference/introducao
- type: Documentation
  url: https://docs.180s.com.br/reference/introducao
- type: APIReference
  url: https://docs.180s.com.br/reference
- type: GettingStarted
  url: https://docs.180s.com.br/reference/introducao
- type: Blog
  url: https://180s.com.br/blog/
- type: TermsOfService
  url: https://180s.com.br/condicoes-gerais/
- type: PrivacyPolicy
  url: https://180s.com.br/wp-content/uploads/2026/03/Politica-de-Privacidade-180-Seguros-new.docx-1.pdf
- type: Support
  url: https://180s.com.br/contato/
- type: SignUp
  url: https://180s.com.br/contato/
- type: GitHubOrganization
  url: https://github.com/180seg
- type: Authentication
  url: authentication/180-insurance-authentication.yml
- type: Conventions
  url: conventions/180-insurance-conventions.yml
- type: ErrorCatalog
  url: errors/180-insurance-problem-types.yml
- type: Webhooks
  url: asyncapi/180-insurance-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/180-insurance-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Lifecycle
  url: lifecycle/180-insurance-lifecycle.yml
- type: Conformance
  url: conformance/180-insurance-conformance.yml
- type: Compliance
  url: https://180s.com.br/tecnologia-180/
- type: DataModel
  url: data-model/180-insurance-data-model.yml
- type: Sandbox
  url: sandbox/180-insurance-sandbox.yml
- type: WellKnown
  url: well-known/180-insurance-well-known.yml
- type: DomainSecurity
  url: security/180-insurance-domain-security.yml
- type: LLMsTxt
  url: llms/180-insurance-llms.txt
- type: AgentSkill
  url: skills/_index.yml
apis:
- aid: 180-insurance:180-insurance-cota-es-api
  name: 180 Insurance Cotações API
  description: The Cotações API from 180 Insurance — 2 operation(s) for cotações.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Cotações
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-cota-es-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-produtos-api
  name: 180 Insurance Produtos API
  description: The Produtos API from 180 Insurance — 1 operation(s) for produtos.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Produtos
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-produtos-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-propostas-api
  name: 180 Insurance Propostas API
  description: The Propostas API from 180 Insurance — 7 operation(s) for propostas.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Propostas
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-propostas-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-renova-es-api
  name: 180 Insurance Renovações API
  description: The Renovações API from 180 Insurance — 3 operation(s) for renovações.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Renovações
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-renova-es-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-sinistros-api
  name: 180 Insurance Sinistros API
  description: The Sinistros API from 180 Insurance — 8 operation(s) for sinistros.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Sinistros
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-sinistros-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-vendas-api
  name: 180 Insurance Vendas API
  description: The Vendas API from 180 Insurance — 6 operation(s) for vendas.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Vendas
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-vendas-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
- aid: 180-insurance:180-insurance-webhooks-api
  name: 180 Insurance Webhooks API
  description: The Webhooks API from 180 Insurance — 3 operation(s) for webhooks.
  humanURL: https://docs.180s.com.br/reference/introducao
  baseURL: https://sagas.staging.180s.com.br
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/180-insurance-webhooks-api-openapi.yml
  - type: Documentation
    url: https://docs.180s.com.br/reference/introducao
  - type: APIReference
    url: https://docs.180s.com.br/reference
  - type: Authentication
    url: authentication/180-insurance-authentication.yml
  - type: ErrorCatalog
    url: errors/180-insurance-problem-types.yml
  - type: Webhooks
    url: asyncapi/180-insurance-webhooks.yml
  - type: X-MCPServerCandidate
    url: mcp/180-insurance-mcp.yml
  - type: Conventions
    url: conventions/180-insurance-conventions.yml
  - type: DataModel
    url: data-model/180-insurance-data-model.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence
x-readme-harvest:
  date: '2026-10-14'
  ops: 33
  tool: harvest-readme-openapi.py
  portal: https://docs.180s.com.br

180 Insurance API — frequently asked questions

Does 180 Insurance have an API?

Yes. APIs.io lists 7 APIs from 180 Insurance, including 180 Insurance Cotações API, 180 Insurance Produtos API and 180 Insurance Propostas API, and 4 more.

Is there an OpenAPI specification for the 180 Insurance API?

Yes. APIs.io indexes 7 OpenAPI specifications for 180 Insurance, each linked for download from this page.

How do I authenticate with the 180 Insurance API?

180 Insurance documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as 180 Insurance Authentication.

Is the 180 Insurance API ready for AI agents?

180 Insurance has a Kin Score of 48.0 out of 100 (developing) and an Agent Readiness score of 44.3 (agent-ready), scored by API Evangelist on 2026-11-06.

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/180-insurance"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/180-insurance/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/180-insurance/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.