Tribute Technology

Tribute Technology is a funeral-home technology company serving over 9,000 funeral homes across the US and Canada with obituary publishing, memorial websites, funeral-home management software, online payments (Tribute Pay), and e-commerce (flowers and personalized products) through the Tribute Store. For partners, Tribute Technology exposes the Tribute Store API - a partner-gated, REST-style JSON API that lets funeral-home case-management systems authenticate a funeral home, push its serving locations (rooftops), and push obituary cases that automatically provision a personalized Tribute Store page for each deceased. Access requires a Provider credential, an IP allowlist, and a per-funeral-home HostName/UserName/Password triple exchanged for a bearer token; there is no public self-service developer portal.

Tribute Technology publishes 3 APIs on the APIs.io network: Authentication API, Obituaries API, and Serving Locations API. Tagged areas include Funeral Technology, Obituaries, Memorials, Funeral Homes, and E-Commerce.

Tribute Technology’s developer surface includes authentication, documentation, engineering blog, and 7 more developer resources.

27.7/100 thin ▼ -10.4 Agent 22/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
AccessPaidSelf serve
3 APIs
Funeral TechnologyObituariesMemorialsFuneral HomesE-CommerceDeath CareCase Management

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 27.7/100 · thin
Contract Quality 3.5 / 25
Developer Ergonomics 4.8 / 20
Access Clarity 7.9 / 20
Operational Transparency 4.1 / 13
Contract Governance 0.0 / 12
Discoverability 7.4 / 10
Agent readiness — 22/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 7 / 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 Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/tributetech: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

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

Tribute Technology Authentication API

Exchange a funeral-home credential triple for a bearer token.

Tribute Technology Obituaries API

Obituary cases pushed to the Tribute Store, and their retrieval.

Tribute Technology Serving Locations API

Funeral-home rooftops (serving locations) that obituaries attach to.

Open Collections 5

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

API Collection

OPEN COLLECTION

Tribute Store API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Tributetech Rate Limits

4 limits

RATE LIMITS

FinOps 1

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

Security Posture 2

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

Tributetech Authentication

http · 1 scheme

SECURITY

Tributetech Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Tributetech Agentic Access

8 operations · 3 acting

8 operations · 3 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: tributetech
url: https://raw.githubusercontent.com/api-evangelist/tributetech/refs/heads/main/apis.yml
name: Tribute Technology
kind: company
description: Tribute Technology is a funeral-home technology company serving over 9,000 funeral homes across the US and Canada
  with obituary publishing, memorial websites, funeral-home management software, online payments (Tribute Pay), and e-commerce
  (flowers and personalized products) through the Tribute Store. For partners, Tribute Technology exposes the Tribute Store
  API - a partner-gated, REST-style JSON API that lets funeral-home case-management systems authenticate a funeral home, push
  its serving locations (rooftops), and push obituary cases that automatically provision a personalized Tribute Store page
  for each deceased. Access requires a Provider credential, an IP allowlist, and a per-funeral-home HostName/UserName/Password
  triple exchanged for a bearer token; there is no public self-service developer portal.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/tributetech.png
tags:
- Funeral Technology
- Obituaries
- Memorials
- Funeral Homes
- E-Commerce
- Death Care
- Case Management
tags_raw:
- Funeral Technology
- Obituaries
- Memorials
- Funeral Homes
- E-commerce
- Death Care
- Case Management
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: tributetech:tributetech-authentication-api
  name: Tribute Technology Authentication API
  description: Exchange a funeral-home credential triple for a bearer token.
  humanURL: https://www.tributetech.com/
  baseURL: https://api.tributecenteronline.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/tributetech-authentication-api-openapi.yml
  - type: Documentation
    url: https://awheeler.funeraltechweb2.com/additional-service-info/file/3/Tribute%20Store%20API%20Documentation%201.1.pdf
  - type: PostmanCollection
    url: collections/tributetech.postman_collection.json
  - type: OpenCollection
    url: collections/tributetech.opencollection.json
- aid: tributetech:tributetech-obituaries-api
  name: Tribute Technology Obituaries API
  description: Obituary cases pushed to the Tribute Store, and their retrieval.
  humanURL: https://www.tributetech.com/
  baseURL: https://api.tributecenteronline.com
  tags:
  - Obituaries
  properties:
  - type: OpenAPI
    url: openapi/tributetech-obituaries-api-openapi.yml
  - type: Documentation
    url: https://awheeler.funeraltechweb2.com/additional-service-info/file/3/Tribute%20Store%20API%20Documentation%201.1.pdf
  - type: PostmanCollection
    url: collections/tributetech.postman_collection.json
  - type: OpenCollection
    url: collections/tributetech.opencollection.json
- aid: tributetech:tributetech-serving-locations-api
  name: Tribute Technology Serving Locations API
  description: Funeral-home rooftops (serving locations) that obituaries attach to.
  humanURL: https://www.tributetech.com/
  baseURL: https://api.tributecenteronline.com
  tags:
  - Serving Locations
  properties:
  - type: OpenAPI
    url: openapi/tributetech-serving-locations-api-openapi.yml
  - type: Documentation
    url: https://awheeler.funeraltechweb2.com/additional-service-info/file/3/Tribute%20Store%20API%20Documentation%201.1.pdf
  - type: PostmanCollection
    url: collections/tributetech.postman_collection.json
  - type: OpenCollection
    url: collections/tributetech.opencollection.json
common:
- type: AgenticAccess
  url: agentic-access/tributetech-agentic-access.yml
- type: DomainSecurity
  url: security/tributetech-domain-security.yml
- type: Authentication
  url: authentication/tributetech-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/tributetechnology
- type: Website
  url: https://www.tributetech.com/
- type: Documentation
  url: https://awheeler.funeraltechweb2.com/additional-service-info/file/3/Tribute%20Store%20API%20Documentation%201.1.pdf
- type: Plans
  url: plans/tributetech-plans-pricing.yml
- type: RateLimits
  url: rate-limits/tributetech-rate-limits.yml
- type: FinOps
  url: finops/tributetech-finops.yml
- url: https://www.tributetech.com/blog
  type: Blog
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/tributetech"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/tributetech/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/tributetech/evidence"

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

Get an API key

Free tier, no email required.

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