Celestial Divide API

Build a dependable estate integration

Connect your systems to Celestial Divide through a predictable JSON API.

Send a standard JSON request

Pass the key in the X-API-Key request header, and declare JSON explicitly.

Method GET, POST, PUT, PATCH, or DELETE
Authentication X-API-Key: your_api_key
Response format Accept: application/json
Request bodies Content-Type: application/json
HTTP request Organization members
GET /api/v1/organization?limit=10&offset=0 HTTP/1.1
Host: celestialdivide.com
X-API-Key: your_api_key
Accept: application/json
Keys are organization-scoped.

The credential determines the organization. Estate resources outside that organization are not available to the key.

List organization members

These examples list organization members and deserialize the JSON response.

interface OrganizationMember {
  id: number;
  email: string;
  first_name: string;
  last_name: string;
  phone_number: string;
  timezone: string;
  role: "admin" | "member";
  role_display: string;
}

interface PagedOrganizationMembers {
  items: OrganizationMember[];
  count: number;
}

class CelestialApi {
  constructor(private readonly apiKey: string) {}

  async listOrganizationMembers(): Promise<PagedOrganizationMembers> {
    const response = await fetch(
      "https://celestialdivide.com/api/v1/organization?limit=10&offset=0",
      {
        headers: {
          "X-API-Key": this.apiKey,
          "Accept": "application/json",
        },
      },
    );

    if (!response.ok) {
      throw new Error(`Request failed: ${response.status}`);
    }

    return (await response.json()) as PagedOrganizationMembers;
  }
}

const api = new CelestialApi(process.env.CELESTIAL_API_KEY!);
const { items: members } = await api.listOrganizationMembers();
console.log(members);
import os
from typing import Literal

import requests
from pydantic import BaseModel


class OrganizationMember(BaseModel):
    id: int
    email: str
    first_name: str
    last_name: str
    phone_number: str
    timezone: str
    role: Literal["admin", "member"]
    role_display: str


class PagedOrganizationMembers(BaseModel):
    items: list[OrganizationMember]
    count: int


response = requests.get(
    "https://celestialdivide.com/api/v1/organization?limit=10&offset=0",
    headers={
        "X-API-Key": os.environ["CELESTIAL_API_KEY"],
        "Accept": "application/json",
    },
    timeout=30,
)
response.raise_for_status()
members = PagedOrganizationMembers.model_validate(response.json())
print(members.items)

Treat status codes as recovery instructions

401

Authenticate again

The key is missing, invalid, revoked, or expired. Confirm the header and rotate the credential if needed.

409

Refresh state before retrying

The operation conflicts with lifecycle state, uniqueness rules, or a concurrent change. Read the detail and refetch the resource.

422

Correct the request

Schema or business validation failed. A detail list identifies fields; a detail string describes a broader rule.

500

Retry with restraint

An unexpected failure occurred. Use capped exponential backoff for safe requests and contact support if it persists.

Validation detail422
{
  "detail": [
    {
      "loc": ["body", "name"],
      "msg": "Field required",
      "type": "missing"
    }
  ]
}
Business rule detail409 / 422
{
  "detail": "The submitted value violates an asset rule."
}
Unexpected server error500
{
  "detail": "Internal Server Error"
}

Send machine values, display readable labels

These references are generated from current application choices and asset types. Use the machine value in payloads.

Bidding round statuses
Machine value Readable label
active Active
completed Completed
locked Locked
Debt types
Machine value Readable label
MORTGAGE Mortgage
LIEN Lien
AUTOMOBILE Automobile
PERSONAL Personal
BUSINESS Business
LINE_OF_CREDIT Line of Credit
STUDENT_LOAN Student Loan
CREDIT_CARD Credit Card
DEBT_CONSOLIDATION Debt Consolidation
OTHER Other
Financial asset account types
Machine value Readable label
TRAD_IRA Traditional IRA
ROLLOVER_IRA_TRAD Rollover IRA (pre-tax)
401K_TRAD 401(k) (Traditional)
403B_TRAD 403(b)
457B_TRAD 457(b)
457F_TRAD 457(f)
TSP_TRAD Thrift Savings Plan (TSP)
PROFIT_SHARING_PLAN Profit-Sharing Plan
MONEY_PURCHASE_PENSION Money Purchase Pension Plan
DEFINED_BENEFIT_PLAN Defined Benefit Plan
SEP_IRA SEP IRA
SIMPLE_IRA SIMPLE IRA
SOLO_401K_TRAD Solo 401(k) / Individual 401(k) (pre-tax portion)
KEOGH_PLAN Keogh Plan
NONQUAL_DEF_COMP_409A Nonqualified Deferred Compensation Plan (409A)
ROTH_IRA Roth IRA
ROTH_401K Roth 401(k)
ROTH_403B Roth 403(b)
ROTH_457B Roth 457(b)
TSP_ROTH Roth Thrift Savings Plan (Roth TSP)
Filing statuses
Machine value Readable label
single Single
married_jointly Married Filing Jointly
head_of_household Head of Household
married_separately Married Filing Separately
Taxable income changes
Machine value Readable label
1 Decrease significantly
2 Decrease modestly
3 No change
4 Increase modestly
5 Increase significantly
Property types
Machine value Readable label
SFH Single Family Home
CONDO Condominium
TOWNHOUSE Townhouse
MULTI Multi-Family
LAND Vacant Land
COMMERCIAL Commercial Property
OTHER Other
Pronouns
Machine value Readable label
she she / her
he he / him
they they / them
Estate roles
Machine value Readable label
BENEFICIARY Beneficiary
PR Personal Representative
PROFESSIONAL Professional
Organization roles
Machine value Readable label
admin Admin
member Member
Estate phases
Machine value Readable label
ESTATE_SETUP Intake
BIDDING_OPEN Bids
BIDDING_FINALISED Allocation & results
ADMINISTRATION Administration
Lien types
Machine value Readable label
HELOC HELOC
SECOND_MORTGAGE Second Mortgage
TAX_LIEN Tax Lien
OTHER Other
Asset types
Machine name Readable name Divisible Non-divisible
collectibles_antiques Collectibles & Antiques Yes Yes
jewelry_precious_metals Jewelry & Precious Metals Yes Yes
marketable_security Marketable Security Yes Yes
other Other Yes Yes
traditional_ira Pre-Tax Retirement Accounts Yes No
real_estate Real Estate No Yes
roth_ira Roth Accounts Yes No
vehicles Vehicles No Yes

Available operations

Descriptions are generated from the live API contract. Open the full docs for schemas, parameters, and interactive request details.

Browse generated endpoints
GET /api/v1/assets/types

List Asset Types

List supported asset types.

POST /api/v1/organization/invitations

Create Organization Invitation

Create an organization invitation and schedule its delivery.

409: The invitee email already belongs to an organization member or has a
pending invitation.

422: The requested inviter is not an administrator of this organization, or
invitation values fail domain validation.

GET /api/v1/organization/invitations

List Organization Invitations

List organization invitations, optionally filtered by lifecycle status.

GET /api/v1/organization/invitations/{invitation_id}

Get Organization Invitation

Get an organization invitation by ID.

DELETE /api/v1/organization/invitations/{invitation_id}

Cancel Organization Invitation

Cancel a pending organization invitation, attribute it to canceled_by, and return it.

This endpoint preserves the invitation as canceled; it does not hard-delete it.

409: The invitation was already accepted or canceled; only pending invitations
can be canceled.

422: The requested canceled_by user is missing from this organization, belongs
only to another organization, or is not an organization administrator.

GET /api/v1/organization

List Members

List members in the organization.

GET /api/v1/organization/{user_id}

Get Member Detail

Get details of an organization member by user ID.

PUT /api/v1/organization/{user_id}

Update Member Role

Update an organization member's role by user ID.

409: Returned when demoting the target member from admin to member would leave the
organization without any admins. This includes concurrent demotion attempts where
another request removes the only other remaining admin first.

POST /api/v1/estates

Create Estate

Create an estate in the organization.

Slug must be in the following format if provided: `estate-slug`
(lowercase, alphanumeric, hyphens only).
If not provided, it will be generated from the name.

409: Indicates that the request conflicts with existing estate state.
This can happen when an explicit slug is already taken, or when a concurrent
insert causes the database to reject the generated or explicit slug. If using
a generated slug, retrying the request will likely return 201. If the endpoint
continues throwing 409, you can contact support to investigate further.

422: Can be returned for schema validation failures, and can also
be returned when the name is blank after trimming whitespace or an explicit
slug is reserved for an application route.

NOTE: All admins of the organization at the time of estate creation will be assigned as admins
to the estate by default, you will need to manually remove them via API or the application to
remove them from the estate.

GET /api/v1/estates

List Estates

List estates in the organization.

GET /api/v1/estates/{estate_slug}

Get Estate Detail

Get details of an estate by its slug.

PATCH /api/v1/estates/{estate_slug}

Update Estate

Update an estate's name and/or slug by its current slug.

Slug must be in the following format if provided: `estate-slug`
(lowercase, alphanumeric, hyphens only).

409: The Estate is formally closed and read-only.

409: The requested slug is already used, or a concurrent update causes the
database to reject it.

422: Returned for schema validation failures, and can also
be returned when a provided name is blank after trimming whitespace, a provided
slug is blank or null, or a provided slug is reserved for an application route.

DELETE /api/v1/estates/{estate_slug}

Delete Estate

Delete an estate by its slug.

409: The Estate is formally closed and must be reopened before deletion.

POST /api/v1/estates/{estate_slug}/close

Close Estate

Formally close an Estate.

409: The Estate is already closed.

409: An allocation is currently running; closure must wait for it to finish.

POST /api/v1/estates/{estate_slug}/reopen

Reopen Estate

Formally reopen an Estate.

409: The Estate is not closed.

409: The organization's shared open-case allowance is full.

409: The Estate's organization or demo classification changes concurrently
while reopening is underway.

GET /api/v1/{estate_slug}/rounds

List Bidding Rounds

List bidding rounds for an estate.

GET /api/v1/{estate_slug}/rounds/active

Get Active Bidding Round

Get the active bidding round for an estate.

GET /api/v1/{estate_slug}/rounds/{round_no}

Get Bidding Round Detail

Get a bidding round by its public round number.

GET /api/v1/{estate_slug}/users

List Estate Users

List users for an estate by estate slug.

NOTE: This does not include organization members that will have access via the organization
to this estate, only explicit members of the estate will be shown here.

GET /api/v1/{estate_slug}/users/{user_id}

Get Estate User Detail

Get details for an estate user by estate slug and user ID.

NOTE: This does not include organization members that will have access via the organization
to this estate, only explicit members of the estate will be shown here.

PATCH /api/v1/{estate_slug}/users/{user_id}

Update Estate User

Partially update an estate user by estate slug and user ID.

NOTE: Supplied roles atomically replace direct estate roles. Adding BENEFICIARY
normally creates a missing Beneficiary. If a pending invitation for the user's
email already references a Beneficiary, no duplicate is created. Removing
BENEFICIARY deletes the Beneficiary.

409: The requested email address is already in use.

409: The update would remove the estate's last Personal Representative role. This
ensures that there is always at least one PR acting as an estate admin.

409: The update changes roles for an estate that is no longer in the estate setup
phase.

409: The Estate is formally closed and read-only.

422: payload fails validation, including invalid email
format, blank email values, invalid IANA timezone identifiers, or unsupported
estate role codes.

DELETE /api/v1/{estate_slug}/users/{user_id}

Remove Estate User

Remove a user from an estate by estate slug and user ID.

409: The estate is no longer in the estate setup phase, as members can only be
removed during that phase.

409: The removal would remove the estate's last Personal Representative. This
ensures that there is always at least one PR acting as an estate admin.

409: The Estate is formally closed and read-only.

NOTE: Clears all direct estate roles and membership. If the BENEFICIARY role
existed, deletes the Beneficiary; preserves the user account and access to
other estates.

POST /api/v1/{estate_slug}/invitations

Send Invitation

Create and send an invitation for an estate by estate slug.

409: A pending invitation already exists for the invitee email address.

409: The requested beneficiary is already linked to a user account.

409: The requested beneficiary already has a pending invitation.

409: The requested invitee email address is already attached to a beneficiary
in this estate.

409: The Estate is formally closed and read-only.

422: Returned for schema validation failures, and can also be returned when
invited_by is not a member of the estate or organization, beneficiary is
provided without the BENEFICIARY role, or beneficiary does not belong to
this estate.

GET /api/v1/{estate_slug}/invitations

List Invitations

List invitations for an estate by estate slug.

GET /api/v1/{estate_slug}/invitations/{invitation_id}

Get Invitation Detail

Get details for an estate invitation by estate slug and invitation ID.

DELETE /api/v1/{estate_slug}/invitations/{invitation_id}

Revoke Invitation

Revoke a pending invitation for an estate by estate slug and invitation ID.

NOTE: Only pending invitations can be revoked. An accepted invitation or an
unknown invitation_id returns 404.

409: The Estate is formally closed and read-only.

GET /api/v1/{estate_slug}/assets

List Assets

List assets in an estate.

GET /api/v1/{estate_slug}/assets/{asset_id}

Get Asset Detail

Get details for one asset in an estate.

DELETE /api/v1/{estate_slug}/assets/{asset_id}

Delete Asset

Delete an asset from an estate while the estate is in setup.

PATCH /api/v1/{estate_slug}/assets/{asset_id}

Update Asset

Partially update a generic or financial asset in an estate.

409: The estate is no longer in the Estate Setup phase, as assets can only
be updated during setup.

409: A concurrent write or database constraint rejects the save. Retrying may
succeed if the conflict was transient.

422: Returned for schema validation failures, and can also be returned when
a provided name is blank after trimming whitespace, updated_by_id does
not reference an estate or organization user, the resulting
expected_sale_value is greater than market_value, the requested
divisible value is incompatible with the asset type, account_type is
provided for a non-financial asset, account_type is explicitly null or
incompatible for a financial asset, original valuation amount/date are
not both provided or both omitted, or original_market_value_date is later
than market_value_date.

POST /api/v1/{estate_slug}/assets/real_estate

Create Real Estate Asset

Create a real estate asset in an estate.

409: The estate is no longer in the Estate Setup phase, as assets can only
be created during setup.

409: A concurrent write or database constraint rejects the save. Retrying may
succeed if the conflict was transient.

422: Returned for schema validation failures, and can also be returned when
the asset name is blank after trimming whitespace, expected_sale_value is
greater than market_value, created_by_id does not reference an estate or
organization user, original valuation amount/date are not both provided
or both omitted, or original_market_value_date is later than
market_value_date.

PATCH /api/v1/{estate_slug}/assets/real_estate/{asset_id}

Update Real Estate Asset

Partially update a real estate asset in an estate.

409: The estate is no longer in the Estate Setup phase, as assets can only
be updated during setup.

409: A concurrent write or database constraint rejects the save. Retrying may
succeed if the conflict was transient.

422: Returned for schema validation failures, and can also be returned when
a provided name is blank after trimming whitespace, updated_by_id does
not reference an estate or organization user, the resulting
expected_sale_value is greater than market_value, original valuation
amount/date are not both provided or both omitted, or
original_market_value_date is later than market_value_date.

POST /api/v1/{estate_slug}/assets/marketable_security

Create Marketable Security Asset

Create a marketable security asset in an estate.

409: The estate is closed or no longer in the Estate Setup phase.

409: A concurrent write or database constraint rejects the save.

422: The asset name is blank after trimming whitespace, expected_sale_value
exceeds market_value, created_by_id does not reference an estate or
organization user, or the requested divisibility is incompatible with
the asset type. Original valuation amount/date must be both provided
or both omitted, and original_market_value_date cannot be later than
market_value_date.

PATCH /api/v1/{estate_slug}/assets/marketable_security/{asset_id}

Update Marketable Security Asset

Partially update a marketable security asset in an estate.

409: The estate is closed or no longer in the Estate Setup phase.

409: A concurrent write or database constraint rejects the save.

422: A provided name is blank after trimming whitespace, updated_by_id does
not reference an estate or organization user, the resulting expected
sale value exceeds market value, or the requested divisibility is
incompatible with the asset type. Original valuation amount/date must
be both provided or both omitted in the resulting asset, and the
original valuation date cannot be later than the current valuation date.
Non-nullable common asset fields cannot be cleared with null.

POST /api/v1/{estate_slug}/assets/{asset_type}

Create Asset

Create a generic or financial asset in an estate.

409: The estate is no longer in the Estate Setup phase, as assets can only
be created during setup.

409: A concurrent write or database constraint rejects the save. Retrying may
succeed if the conflict was transient.

422: Returned for schema validation failures, and can also be returned when
the asset name is blank after trimming whitespace, expected_sale_value is
greater than market_value, created_by_id does not reference an estate or
organization user, the requested divisible value is incompatible with
the asset type, account_type is provided for a non-financial asset,
account_type is missing or incompatible for a financial asset, original
valuation amount/date are not both provided or both omitted, or
original_market_value_date is later than market_value_date.

POST /api/v1/{estate_slug}/beneficiaries

Create Admin Beneficiary

Create a beneficiary and associated non-login user.

NOTE: Atomically creates a user, estate membership, Beneficiary, and BENEFICIARY role.

409: The estate is no longer in the Estate Setup phase.

409: The generated internal email or requested username is already in use, or
a concurrent write or database constraint rejects beneficiary creation.

422: Returned for schema validation failures, and can also be returned when
created_by_id does not reference an estate or organization user, nested
user names are blank after trimming whitespace, beneficiary choices are
invalid, total_income is negative, split_percentage is outside zero to
one hundred, or model validation rejects the user or beneficiary.

GET /api/v1/{estate_slug}/beneficiaries

List Beneficiaries

List beneficiaries in an estate.

POST /api/v1/{estate_slug}/beneficiaries/{user_id}

Create Beneficiary

Add beneficiary details to an accessible existing user.

NOTE: Atomically creates the Beneficiary and adds the BENEFICIARY role,
preserving other estate roles and creating estate membership if needed.

409: The estate is no longer in the Estate Setup phase.

409: The user is already a beneficiary, has a pending linked beneficiary
invitation, or a concurrent write or database constraint rejects role
assignment or beneficiary creation.

422: Returned for schema validation failures, and can also be returned when
created_by_id does not reference an estate or organization user,
beneficiary choices are invalid, total_income is negative,
split_percentage is outside zero to one hundred, or model validation
rejects the beneficiary.

GET /api/v1/{estate_slug}/beneficiaries/{user_id}

Get Beneficiary Detail

Get a beneficiary in an estate by user ID.

PATCH /api/v1/{estate_slug}/beneficiaries/{user_id}

Update Beneficiary

Partially update a beneficiary in an estate.

409: The estate is no longer in the Estate Setup phase.

422: updated_by_id does not reference an estate or organization user, or the
submitted split percentage has more precision than the beneficiary model
can store.

DELETE /api/v1/{estate_slug}/beneficiaries/{user_id}

Delete Beneficiary

Delete a beneficiary from an estate.

NOTE: Atomically deletes the Beneficiary and removes the BENEFICIARY role,
preserves other direct roles and the user account, and deletes estate
membership if no direct estate roles remain.

409: The estate is no longer in the Estate Setup phase, as beneficiaries can
only be deleted during setup.

POST /api/v1/{estate_slug}/cash

Create Cash

Create cash for an estate's active bidding round.

409: The estate is not in the Estate Setup or Bidding Open phase.

409: The estate has no active bidding round.

409: A concurrent write or database constraint rejects the save.

422: The beneficiary is outside the estate.

422: created_by_id does not reference an estate or organization user.

GET /api/v1/{estate_slug}/cash

List Cash

List cash for an estate bidding round.

When no bidding round is provided, cash is returned for the active round,
or the latest round when none is active.

422: The requested bidding round does not exist for the estate.

GET /api/v1/{estate_slug}/cash/{cash_id}

Get Cash Detail

Get one cash record in an estate.

PATCH /api/v1/{estate_slug}/cash/{cash_id}

Update Cash

Partially update cash in an estate.

409: The estate is not in the Estate Setup or Bidding Open phase

409: The cash does not belong to an active bidding round.

409: A concurrent write or database constraint rejects the save.

422: updated_by_id does not reference an estate or organization user,

422: The merged cash values violate account type, contribution, or withholding rules.

DELETE /api/v1/{estate_slug}/cash/{cash_id}

Delete Cash

Delete cash from an estate.

409: The estate is formally closed or has no active bidding round.

409: A concurrent write or database constraint rejects the delete.

POST /api/v1/{estate_slug}/liabilities/mortgage

Create Mortgage

Create a mortgage in an estate.

409: The estate is no longer in the Estate Setup phase, the property already
has a mortgage, or a concurrent write or database constraint rejects the save.

422: The name is blank after trimming, created_by_id does not reference an
estate or organization user, or mortgage model rules reject the values.

POST /api/v1/{estate_slug}/liabilities/lien

Create Lien

Create a property lien in an estate.

409: The estate is no longer in the Estate Setup phase, or a concurrent write
or database constraint rejects the save.

422: The name is blank after trimming, created_by_id does not reference an
estate or organization user, lien_type is unsupported, or lien model rules
reject the values.

GET /api/v1/{estate_slug}/liabilities/{liability_id}

Get Liability Detail

Return one liability in an estate.

PATCH /api/v1/{estate_slug}/liabilities/{liability_id}

Update Liability

Partially update a generic liability in an estate.

409: The estate is no longer in the Estate Setup phase, or a concurrent write
or database constraint rejects the save.

422: updated_by_id does not reference an estate or organization user, or the
merged liability values violate generic liability model rules.

DELETE /api/v1/{estate_slug}/liabilities/{liability_id}

Delete Liability

Delete any liability/debt from an estate.

409: The estate is no longer in the Estate Setup phase.

POST /api/v1/{estate_slug}/liabilities/{debt_type}

Create Liability

Create a generic liability in an estate.

409: The estate is no longer in the Estate Setup phase, or a concurrent write
or database constraint rejects the save.

422: The debt type is not generic, the name is blank after trimming,
created_by_id does not reference an estate or organization user, or debt
model rules reject the values.

GET /api/v1/{estate_slug}/liabilities

List Liabilities

List liabilities in an estate.

PATCH /api/v1/{estate_slug}/liabilities/mortgage/{liability_id}

Update Mortgage

Partially update a mortgage in an estate.

409: The estate is no longer in the Estate Setup phase, the replacement
property already has a mortgage, or a concurrent write or database
constraint rejects the save.

422: updated_by_id does not reference an estate or organization user, the
merged balance and monthly payment are not both zero or both positive,
or the merged mortgage values violate mortgage model rules.

PATCH /api/v1/{estate_slug}/liabilities/lien/{liability_id}

Update Lien

Partially update a property lien in an estate.

409: The estate is no longer in the Estate Setup phase, or a concurrent write
or database constraint rejects the save.

422: updated_by_id does not reference an estate or organization user,
lien_type is unsupported, or the merged lien values violate property lien
model rules.

Need request and response schemas? Review the full OpenAPI documentation.

Connect an AI assistant over MCP

Celestial Divide runs a remote Model Context Protocol server. An assistant such as Claude or ChatGPT signs in as a Celestial Divide user and works with that user's estates, with exactly the access the user's roles give them in the web app. No API key is involved: each user connects and approves the assistant themselves.

Endpoint https://celestialdivide.com/mcp
Transport Streamable HTTP, stateless: POST only, one JSON-RPC message per request, application/json responses, no session IDs and no event streams. GET and DELETE return 405.
Protocol versions 2026-07-28, 2025-11-25, 2025-06-18
Authentication Authorization: Bearer access_token

Adding it to Claude or ChatGPT

These are the steps signed-in users also see on the Connected Assistants page.

Claude

  1. In Claude, go to Customize > Connectors.
  2. Click Add, then Add custom connector.
  3. Enter Celestial Divide as the name, paste the address above and click Continue.
  4. Keep the sign-in settings Claude detected, click Continue, then click Add.
  5. If Claude shows Connect, click it and sign in to Celestial Divide.

The Free plan allows one custom connector. On Team and Enterprise plans an Owner adds the connector for the organization in Organization settings, and you then find it under Customize > Connectors and click Connect. Claude's instructions

ChatGPT

  1. Open ChatGPT on the web, go to Plugins, select the plus button and choose Add custom MCP server.
  2. Enter Celestial Divide as the name and paste the address above as the Server URL.
  3. For authentication, pick the option that has you sign in, not No authentication. Accept the risk warning and select Create as a plugin.
  4. Install the plugin, then sign in to Celestial Divide when ChatGPT asks.

Whether you can add your own server depends on your ChatGPT plan and, in a work account, on your workspace's settings. If you do not see the option, ask your workspace administrator or check OpenAI's help. OpenAI's instructions

Authorization

  • OAuth 2.1 authorization code flow with PKCE (S256 only). Clients are public (token endpoint authentication none); the grant types are authorization_code and refresh_token.
  • Discovery starts at the endpoint: a request without a valid token gets 401 with WWW-Authenticate: Bearer resource_metadata="…". The protected resource metadata at https://celestialdivide.com/.well-known/oauth-protected-resource/mcp names the authorization server, whose metadata is at https://celestialdivide.com/.well-known/oauth-authorization-server.
  • Clients identify themselves with a client ID metadata document, accepted for allowlisted client IDs such as Claude's and ChatGPT's, or register dynamically at https://celestialdivide.com/oauth/register/. Dynamic registration is rate limited, and redirect URIs must use https or loopback http.
  • Send resource=https://celestialdivide.com/mcp on authorization and token requests. Tokens are bound to that resource; any other value fails with invalid_target.
  • At https://celestialdivide.com/oauth/authorize/ the user signs in with their normal Celestial Divide login and approves a consent screen, every time. Tokens are issued at https://celestialdivide.com/oauth/token/ and revoked at https://celestialdivide.com/oauth/revoke/.
  • Access tokens last 60 minutes. Refresh tokens rotate on every use and expire after 90 days without use.
Scope What it allows
estates:read View your estates, assets, beneficiaries, bids and results
estates:write Create and change estates, assets, beneficiaries and bids on your behalf

Scopes limit what the assistant may do; what the user may do is checked on every call, as in the web app. A token without estates:write does not see the tools that change data in tools/list, and calling one returns 403 with an insufficient_scope challenge.

Tools

Generated from the server's tool registry. Every tool sets readOnlyHint, destructiveHint, idempotentHint and openWorldHint; tools/list has the full definitions and schemas.

Read data estates:read
Tool Title Notes
list_beneficiaries List the estate's beneficiaries
list_invitations List the estate's invitations
get_account_overview Get account overview
get_guide Get the Celestial Divide guide
list_estates List estates
get_estate Get estate details
list_asset_types List asset types
list_assets List the estate's assets
get_asset Get an asset
list_estate_cash List the estate's cash
list_liabilities List the estate's debts
get_bidding_status Get bidding status
list_bids List a beneficiary's bids
get_solver_status Get solver status
get_allocation_results Get allocation results
list_estate_activity List the estate's activity
Change data estates:write
Tool Title Notes
create_estate Create an estate
update_estate Change the estate's details Overwrites, removes or makes a permanent change
open_bidding Open bidding Overwrites, removes or makes a permanent change
complete_bidding Mark bidding complete Overwrites, removes or makes a permanent change
complete_allocation Mark allocation complete Overwrites, removes or makes a permanent change
create_asset Add an asset
update_asset Change an asset Overwrites, removes or makes a permanent change
delete_asset Delete an asset Overwrites, removes or makes a permanent change
add_estate_cash Add estate cash
update_estate_cash Change estate cash Overwrites, removes or makes a permanent change
remove_estate_cash Remove estate cash Overwrites, removes or makes a permanent change
add_liability Add a debt
update_liability Change a debt Overwrites, removes or makes a permanent change
remove_liability Remove a debt Overwrites, removes or makes a permanent change
add_beneficiary Add a placeholder beneficiary
update_beneficiary Change a placeholder beneficiary Overwrites, removes or makes a permanent change
remove_beneficiary Remove a beneficiary Overwrites, removes or makes a permanent change
set_inheritance_shares Set inheritance shares Overwrites, removes or makes a permanent change
send_invitation Invite someone to the estate Sends email
resend_invitation Resend an invitation Sends email
revoke_invitation Withdraw an invitation Overwrites, removes or makes a permanent change
place_bids Enter bids Overwrites, removes or makes a permanent change
mark_assets_not_wanted Mark assets 'Do not want' Overwrites, removes or makes a permanent change
finalize_bids Finalize bids Overwrites, removes or makes a permanent change
finalize_all_bids Finalize every beneficiary's bids Overwrites, removes or makes a permanent change
unlock_bids Unlock finalized bids Overwrites, removes or makes a permanent change
run_solver Run the solver Overwrites, removes or makes a permanent change

Rate limits

  • Every request to the endpoint: 300 per minute and 5,000 per hour, per user.
  • Tools that read data: 120 per minute and 2,000 per hour, per user.
  • Tools that change data: 30 per minute and 500 per hour, per user.
  • Tools that send email: 5 per minute and 30 per hour, per user.
  • Creating an estate: 5 per minute and 20 per hour, per user.

Over the request limit the endpoint answers 429 with Retry-After; over a tool limit the call returns a rate_limited error result that says how long to wait.

Managing connections

Signed-in users find the setup steps for Claude and ChatGPT, see which assistants are connected and disconnect them on the Connected Assistants page. Disconnecting deletes that assistant's tokens. Changing or resetting the account password disconnects every assistant.

Tell us what your integration needs

We welcome feature requests, including ordering and filtering options that reduce extra client work. Straightforward requests can often be assessed quickly; complex requests involving workflow rules or new write behavior need additional design and validation.

Share the endpoint, desired result, example payload, and the workflow it enables with our team.