Luminary

Luminary is AI-powered estate planning software for wealth advisors, family offices, attorneys, and professional services firms. It turns static estate planning documents into organized, digital records — with AI document digitization and summarization, dynamic estate flowcharts and waterfalls, scenario modeling, and role-based collaboration. Its public REST API (v1) exposes households, individuals, entities, documents, AI document summaries, and entity valuations so estate data can sync with CRMs, client portals, and planning tools. First-party TypeScript and Go SDKs are published on GitHub. OAuth2-secured (authorizationCode + clientCredentials) and SOC 2 Type II audited. Backed by 8vc.

Luminary publishes 6 APIs on the APIs.io network, including Documents API, Entities API, Households API, and 3 more. Tagged areas include Company, Estate Planning, Wealth Management, Financial-Services, and Legal Tech.

Luminary’s developer surface includes engineering blog, pricing, support, authentication, and 22 more developer resources.

🌐 Visit website 📡 Source on GitHub

40.5/100 developing ▬ flat Agent 29/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

1 APIs

Company Estate Planning Wealth Management Financial-Services Legal Tech Document AI Family Office Authentication

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 40.5/100 · developing

Contract Quality 12.2 / 23

Developer Ergonomics 5.0 / 18

Access Clarity 9.7 / 18

Operational Transparency 0.3 / 12

Contract Governance 0.5 / 11

Discoverability 6.8 / 9

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 29/100 · agent ready

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

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 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 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/luminary: 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 6

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

Luminary Documents API

The Documents API from Luminary — 8 operation(s) for documents.

Luminary Entities API

The Entities API from Luminary — 4 operation(s) for entities.

Luminary Households API

The Households API from Luminary — 5 operation(s) for households.

Luminary Individuals API

The Individuals API from Luminary — 3 operation(s) for individuals.

Luminary Users API

The Users API from Luminary — 2 operation(s) for users.

Luminary Valuations API

The Valuations API from Luminary — 1 operation(s) for valuations.

Open Collections 7

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

API Collection

OPEN COLLECTION

Luminary Documents API

OPEN COLLECTION

Luminary Documents Entities API

OPEN COLLECTION

Luminary Documents Households API

OPEN COLLECTION

Luminary Documents Individuals API

OPEN COLLECTION

Luminary Documents Users API

OPEN COLLECTION

Luminary Documents Valuations API

OPEN COLLECTION

Scroll for all 7

Security Posture 3

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

Luminary Authentication

oauth2 · 1 scheme

SECURITY

Luminary Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Luminary Trust Center

SOC 2

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Luminary Scopes

4 scopes · authorizationCode/clientCredentials

4 scopes

SCOPES

Agentic Access 1

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

Luminary Agentic Access

31 operations · 12 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

LLMsTxt

AgenticAccess

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 5

Authentication, authorization, and security posture

Compliance

TrustCenter

DomainSecurity

Authentication

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: luminary
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: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/luminary.png
name: Luminary
description: Luminary is AI-powered estate planning software for wealth advisors, family offices, attorneys, and professional
  services firms. It turns static estate planning documents into organized, digital records — with AI document digitization
  and summarization, dynamic estate flowcharts and waterfalls, scenario modeling, and role-based collaboration. Its public
  REST API (v1) exposes households, individuals, entities, documents, AI document summaries, and entity valuations so estate
  data can sync with CRMs, client portals, and planning tools. First-party TypeScript and Go SDKs are published on GitHub.
  OAuth2-secured (authorizationCode + clientCredentials) and SOC 2 Type II audited. Backed by 8vc.
url: https://raw.githubusercontent.com/api-evangelist/luminary/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 8vc
x-tier: active
x-tier-reason: public-api-found
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Estate Planning
- Wealth Management
- Financial-Services
- Legal Tech
- Document AI
- Family Office
- Authentication
tags_raw:
- Company
- Estate Planning
- Wealth Management
- Financial Services
- Legal Tech
- Document AI
- Family Office
- OAuth2
apis:
- aid: luminary:luminary-documents-api
  name: Luminary Documents API
  description: The Documents API from Luminary — 8 operation(s) for documents.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - Documents
  properties:
  - type: OpenAPI
    url: openapi/luminary-documents-api-openapi.yml
- aid: luminary:luminary-entities-api
  name: Luminary Entities API
  description: The Entities API from Luminary — 4 operation(s) for entities.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - Entities
  properties:
  - type: OpenAPI
    url: openapi/luminary-entities-api-openapi.yml
- aid: luminary:luminary-households-api
  name: Luminary Households API
  description: The Households API from Luminary — 5 operation(s) for households.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - Households
  properties:
  - type: OpenAPI
    url: openapi/luminary-households-api-openapi.yml
- aid: luminary:luminary-individuals-api
  name: Luminary Individuals API
  description: The Individuals API from Luminary — 3 operation(s) for individuals.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - Individuals
  properties:
  - type: OpenAPI
    url: openapi/luminary-individuals-api-openapi.yml
- aid: luminary:luminary-users-api
  name: Luminary Users API
  description: The Users API from Luminary — 2 operation(s) for users.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/luminary-users-api-openapi.yml
- aid: luminary:luminary-valuations-api
  name: Luminary Valuations API
  description: The Valuations API from Luminary — 1 operation(s) for valuations.
  humanURL: https://withluminary.com/integrations
  baseURL: https://lum.withluminary.com/api/public/v1
  tags:
  - Valuations
  properties:
  - type: OpenAPI
    url: openapi/luminary-valuations-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/luminary-openapi-overlay.yaml
- type: Website
  url: https://withluminary.com
- type: GitHubOrganization
  url: https://github.com/withluminary
- type: Blog
  url: https://withluminary.com/resources
- type: Pricing
  url: https://withluminary.com/pricing
- type: Login
  url: https://app.withluminary.com
- type: Support
  url: https://withluminary.com/contact
- type: TermsOfService
  url: https://withluminary.com/terms
- type: PrivacyPolicy
  url: https://withluminary.com/privacy
- type: Compliance
  url: https://withluminary.com/security
- type: TrustCenter
  url: security/luminary-trust-center.yml
- type: DomainSecurity
  url: security/luminary-domain-security.yml
- type: Authentication
  url: authentication/luminary-authentication.yml
- type: OAuthScopes
  url: scopes/luminary-scopes.yml
- type: WellKnown
  url: well-known/luminary-well-known.yml
- type: Packages
  url: packages/luminary-packages.yml
- type: SDKs
  url: packages/luminary-packages.yml
- type: X-MCPServerCandidate
  url: mcp/luminary-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: LLMsTxt
  url: llms/luminary-llms.txt
- type: Conformance
  url: conformance/luminary-conformance.yml
- type: ErrorCatalog
  url: errors/luminary-problem-types.yml
- type: Lifecycle
  url: lifecycle/luminary-lifecycle.yml
- type: Conventions
  url: conventions/luminary-conventions.yml
- type: DataModel
  url: data-model/luminary-data-model.yml
- type: AgenticAccess
  url: agentic-access/luminary-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 22
  pass: local-v1

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

All providers

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

Every operation they expose

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

How their score was established

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