How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
1Fort website screenshot

1Fort

1Fort is a New York City based insurtech platform that automates the commercial insurance workflow for brokers and agencies. Its AI "copilot" autofills submissions across 300+ coverages, quotes direct and wholesale markets, generates white-labeled proposals with side-by-side coverage comparisons and cross-sell recommendations, then processes binders, invoicing, premium finance, payments and payables through to ongoing policy servicing. Coverage lines span cyber, technology errors and omissions, professional liability, management liability, general liability and workers compensation. The platform runs on AWS, holds SOC 2 Type II, HIPAA and CCPA attestations, and exposes a large REST API at api.1fort.com whose Swagger 2.0 definition is published publicly at /api-docs — 574 operations across broker, application, quote, market, billing, checkout, storefront and Email AI Agent surfaces, plus inbound webhook receivers for Stripe, Ascend, Herald, Gmail and Office 365.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles 1Fort the way a machine reads it — 187 machine-readable artifacts across 89 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — 1Fort scores 51.1/100 (developing), with a separate agent-readiness read of 49/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 51.1/100 · developing
Contract Quality 15.9 / 25
Developer Ergonomics 7.3 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 6.5 / 13
Governance 2.5 / 12
Discoverability 6.3 / 10
Regulatory · Insurance 8.2 / 15
Agent readiness — 49/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract derived 2.5 / 10
MCP Server derived 3.0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface derived 1.5 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
1Fort Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from 1Fort's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/1fort/"
   title="1Fort on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/1fort.svg"
       alt="1Fort Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile 1Fort

Each block below is one kind of artifact we hold for 1Fort. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 89

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

1Fort agent_runtime (v2) API

**Access:** requires a JWT access token.

1Fort Analytics API

**Access:** requires a JWT access token.

1Fort application: applications API

**Access:** requires a JWT access token.

1Fort application: clients API

**Access:** requires a JWT access token.

1Fort application (v2): applications API

**Access:** requires a JWT access token.

1Fort application (v2): coverages API

**Access:** requires a JWT access token.

1Fort Ascend API

**Deprecated.** Legacy Ascend billing/payments; use the Billing (v2) endpoints instead. **Access:** mixed; some endpoints are public, others require JWT or an API key (per endpo...

1Fort ascend (v2) API

**Deprecated.** Legacy Ascend billing/payments; use the Billing (v2) endpoints instead. **Access:** requires a JWT access token.

1Fort Auth API

Sign in / sign up via Google or Office365 OAuth and refresh JWT access tokens. **Access:** mixed; some endpoints are public, others require JWT (per endpoint).

1Fort Authentication API

One-time-password (OTP) authentication. **Access:** public; no authentication required.

1Fort billing (v2) API

Billing and payments. Replaces the deprecated Ascend payment endpoints. **Access:** requires a JWT access token.

1Fort broker: ai-customization-types API

**Access:** requires a JWT access token.

1Fort broker: ai-customizations API

**Access:** requires a JWT access token.

1Fort Broker Ams Integration API

**Access:** requires a JWT access token.

1Fort Broker API

**Access:** mixed; some endpoints are public, others require JWT (per endpoint).

1Fort broker: clients API

**Access:** requires a JWT access token.

1Fort broker: email_preferences API

**Access:** requires a JWT access token.

1Fort Broker Google API

**Access:** public; no authentication required.

1Fort Broker Groups API

**Access:** requires a JWT access token.

1Fort Broker Office365 API

**Access:** public; no authentication required.

1Fort Broker Office365 Individual API

**Access:** public; no authentication required.

1Fort broker: proposal-preferences API

**Access:** requires a JWT access token.

1Fort Broker Settings API

**Access:** requires a JWT access token.

1Fort broker: take-rates API

**Access:** requires a JWT access token.

1Fort broker: user-ai-customizations API

**Access:** requires a JWT access token.

1Fort broker: users API

**Access:** requires a JWT access token.

1Fort broker (v2): applications API

**Access:** requires a JWT access token.

1Fort broker (v2): clients API

**Access:** requires a JWT access token.

1Fort broker (v2): coverages API

**Access:** requires a JWT access token.

1Fort broker (v2): email-templates API

**Access:** requires a JWT access token.

1Fort broker (v2): quote-policies API

**Access:** requires a JWT access token.

1Fort broker (v2): quotes API

**Access:** requires a JWT access token.

1Fort broker (v2): storefront API

**Access:** requires a JWT access token.

1Fort broker (v2): team-users API

**Access:** requires a JWT access token.

1Fort Business Admin API

**Access:** requires a JWT access token.

1Fort Business API

**Access:** requires a JWT access token.

1Fort Business Broker Users API

**Access:** requires a JWT access token.

1Fort Business User API

**Access:** requires a JWT access token.

1Fort Carrier API

**Access:** requires a JWT access token.

1Fort Checkout API

Checkout and payment session endpoints. **Access:** public; no authentication required.

1Fort Email AI Agent API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Attachments API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Businesses API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Entities API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Markets API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Profiles API

**Access:** requires a JWT access token.

1Fort Email AI Agent - Reference Data API

**Access:** requires a JWT access token.

1Fort Email AI API

**Access:** requires a JWT access token.

1Fort email_ai (v2): attachments API

**Access:** requires a JWT access token.

1Fort email_ai (v2): carriers API

**Access:** requires a JWT access token.

1Fort email_ai (v2): coverage-types API

**Access:** requires a JWT access token.

1Fort email_ai (v2): emails API

**Access:** requires a JWT access token.

1Fort email_ai (v2): gmail API

**Access:** public; no authentication required.

1Fort email_ai (v2): office365 API

**Access:** public; no authentication required.

1Fort email_ai (v2): profiles API

**Access:** requires a JWT access token.

1Fort email_ai (v2): wholesalers API

**Access:** requires a JWT access token.

1Fort google_workspace (v2) API

**Access:** requires a JWT access token.

1Fort herald (v2) API

**Access:** mixed; some endpoints are public, others require JWT or an API key (per endpoint).

1Fort indications (v2) API

**Access:** requires a JWT access token.

1Fort insurance (v2) API

**Access:** requires a JWT access token.

1Fort Invite API

Invitations for broker and business users. **Access:** mixed; some endpoints are public, others require JWT (per endpoint).

1Fort Legal API

Legal documents and agreements. **Access:** requires a JWT access token.

1Fort market (v2) API

**Access:** requires a JWT access token.

1Fort Markets API

**Access:** requires a JWT access token.

1Fort Markets - Business API

**Access:** requires a JWT access token.

1Fort office365 (v2) API

**Access:** requires a JWT access token.

1Fort premium_finance (v2) API

**Access:** requires a JWT access token.

1Fort quote_ai (v2) API

**Access:** requires a JWT access token.

1Fort quote: applications API

**Access:** requires a JWT access token.

1Fort quote: clients API

**Access:** requires a JWT access token.

1Fort quote: quotes API

**Access:** requires a JWT access token.

1Fort quote (v2): application API

**Access:** requires a JWT access token.

1Fort quote (v2): binders API

**Access:** requires a JWT access token.

1Fort quote (v2): checkout API

**Access:** public; no authentication required.

1Fort quote (v2): cios API

**Access:** requires a JWT access token.

1Fort quote (v2): coverages API

**Access:** requires a JWT access token.

1Fort quote (v2): quote-policies API

**Access:** requires a JWT access token.

1Fort quote (v2): quotes API

**Access:** requires a JWT access token.

1Fort quote (v2): tasks API

**Access:** requires a JWT access token.

1Fort Reports API

**Access:** requires a JWT access token.

1Fort Reward API

**Access:** requires a JWT access token.

1Fort Risk Manager API

**Access:** requires a JWT access token.

1Fort Sanity Check AI API

**Access:** requires a JWT access token.

1Fort storefront (v2) API

Insured-facing storefront endpoints. Access is scoped by storefront identity (public links, API key, or storefront permission) rather than a user JWT. **Access:** mixed; some en...

1Fort Stripe API

**Access:** mixed; some endpoints are public, others require JWT (per endpoint).

1Fort Suggestion AI API

**Access:** requires a JWT access token or an API key.

1Fort treasury (v2) API

**Access:** requires a JWT access token.

1Fort User API

**Access:** requires a JWT access token.

1Fort user: default-access-role API

**Access:** requires a JWT access token.

Scroll within the panel for all 89 ·

Open Collections 90

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Scroll within the panel for all 90 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

1fort-mcp.yml

MCP SERVER

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

1Fort Rate Limits

4 limits

RATE LIMITS

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

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

1Fort Webhooks

ASYNCAPI

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

1Fort Authentication

apiKey · 2 schemes

SECURITY

1Fort Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

1Fort Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

1Fort Trust Center

SOC 2 Type II, HIPAA, CCPA

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

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

1Fort Agentic Access

574 operations · 241 acting · 2 human-in-the-loop

574 operations · 241 acting

AGENTIC

Resources

Every other property we hold for 1Fort — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Commercial 3

Pricing, plans, and the legal terms of use

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/1fort · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of 1Fort, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.