funeralOne

funeralOne is a funeral-home technology company whose f1Connect platform delivers funeral-home websites, memorial/tribute pages, Life Tributes tribute videos, memorial webcasting, and e-commerce for independent funeral homes. funeralOne publishes a partner integration API (base https://api.funeralone.com) that lets funeral-management / case-management systems push deceased, obituary, service-event, tribute-video, and family-administration data into a funeral home's f1Connect account so an At-Need case automatically populates the memorial website and Life Tributes. The API is partner-gated - access requires an API key issued by a funeralOne engineer and per-customer AccountExternalId associations - and uses HTTP Basic authentication. Only the Cases resource is publicly documented; the broader website, e-commerce, and webcasting products are delivered through the f1Connect platform rather than a public API.

funeralOne publishes 1 API on the APIs.io network: Cases API. Tagged areas include Funeral Homes, Death Care, Obituaries, Tribute Videos, and Memorial Websites.

funeralOne’s developer surface includes authentication, documentation, support, and 7 more developer resources.

🌐 Visit website 📡 Source on GitHub

25.9/100 emerging ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-09-15 · rubric v0.22.0

AccessPaid

1 APIs

Funeral Homes Death Care ObituariesTribute VideosMemorial WebsitesLife TributesCase Management Partner API

Kin Score

Kin Score How this is scored →
scored 2026-09-15 · rubric v0.22.0

Composite quality — 25.9/100 · emerging

Contract Quality 0.0 / 23

Developer Ergonomics 6.2 / 18

Access Clarity 7.1 / 18

Operational Transparency 2.5 / 12

Contract Governance 0.0 / 11

Discoverability 6.2 / 9

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

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/funeralone: 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 1

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

funeralOne Cases API

Create, update, and retrieve funeral cases (obituaries) for an account.

Open Collections 2

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

API Collection

OPEN COLLECTION

funeralOne Cases API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Funeralone Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Funeralone Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Funeralone Finops

FINOPS

Security Posture 2

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

Funeralone Authentication

http · 1 scheme

SECURITY

Funeralone Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Funeralone Agentic Access

3 operations · 1 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

LinkedIn

Source (apis.yml)

aid: funeralone
url: https://raw.githubusercontent.com/api-evangelist/funeralone/refs/heads/main/apis.yml
name: funeralOne
kind: company
description: funeralOne is a funeral-home technology company whose f1Connect platform delivers funeral-home websites, memorial/tribute
  pages, Life Tributes tribute videos, memorial webcasting, and e-commerce for independent funeral homes. funeralOne publishes
  a partner integration API (base https://api.funeralone.com) that lets funeral-management / case-management systems push
  deceased, obituary, service-event, tribute-video, and family-administration data into a funeral home's f1Connect account
  so an At-Need case automatically populates the memorial website and Life Tributes. The API is partner-gated - access requires
  an API key issued by a funeralOne engineer and per-customer AccountExternalId associations - and uses HTTP Basic authentication.
  Only the Cases resource is publicly documented; the broader website, e-commerce, and webcasting products are delivered through
  the f1Connect platform rather than a public API.
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
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/funeralone.png
tags:
- Funeral Homes
- Death Care
- Obituaries
- Tribute Videos
- Memorial Websites
- Life Tributes
- Case Management
- Partner API
tags_raw:
- Funeral Homes
- Deathcare
- Obituaries
- Tribute Videos
- Memorial Websites
- Life Tributes
- Case Management
- Partner API
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: funeralone:funeralone-cases-api
  name: funeralOne Cases API
  description: Create, update, and retrieve funeral cases (obituaries) for an account.
  humanURL: https://api.funeralone.com/docs/
  baseURL: https://api.funeralone.com
  tags:
  - Cases
  properties:
  - type: OpenAPI
    url: openapi/funeralone-cases-api-openapi.yml
  - type: Documentation
    url: https://api.funeralone.com/docs/
  - type: APIReference
    url: https://api.funeralone.com/docs/
  - type: PostmanCollection
    url: collections/funeralone.postman_collection.json
common:
- type: AgenticAccess
  url: agentic-access/funeralone-agentic-access.yml
- type: DomainSecurity
  url: security/funeralone-domain-security.yml
- type: Authentication
  url: authentication/funeralone-authentication.yml
- type: Website
  url: https://www.funeralone.com
- type: LinkedIn
  url: https://www.linkedin.com/company/funeralone
- type: Documentation
  url: https://api.funeralone.com/docs/
- type: Support
  url: https://support.funeralone.com
- type: Plans
  url: plans/funeralone-plans-pricing.yml
- type: RateLimits
  url: rate-limits/funeralone-rate-limits.yml
- type: FinOps
  url: finops/funeralone-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/funeralone"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/funeralone/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.