Public API and MCP server

Seniornicity is a national B2B2C senior-focused ecosystem serving the United States and Canada. Built on the philosophy Aging Takes a Team, it connects senior-focused professionals, organizations, older adults, families, and homeowners through a collaborative network supporting aging and senior transitions. Seniornicity connects consumers with independent professionals; it does not itself provide real estate brokerage, caregiving, legal, financial, insurance, or medical services. Its own platform services include Transition Consulting, local chapters, The Seniornicity Community, the Senior Transition Specialist (STS) certification, and Sam, its digital guide.

The API returns the same public information the site shows, nothing more, so an assistant can answer “which professional helps with this” and send the person to the right Seniornicity page. Four kinds of records are exposed: provider summaries and profiles, chapters, Community events and Community posts. The categories are Licensed Real Estate Agents, Estate Sales Professionals, Lenders / Mortgage Professionals, Financial Planners, Legal Services Professionals, Caregiver Agencies, Property Managers, Senior Placement Advisors and Home Service Providers; the individual home-service categories are listed by the categories endpoint.

Credentials are per provider and stay separate. Providers are independent professionals, and no status applies to all of them. Each provider record carries its own flags for isClaimed, isVerified (the profile displays the Verified badge), hasSTS (the provider holds the Senior Transition Specialist certification), hasCSA, hasSRES, isCesmpCertified and chapter membership. They mean different things; do not collapse them into one “verified” or “certified” label, and do not describe a provider as verified or certified unless that provider’s flag is true.

Nothing is invented. Every record returned exists on Seniornicity. An empty result is returned as empty, with a directory URL to offer instead.

https://app.seniornicity.com/api/public/v1

Canadian records use the same paths on app.seniornicity.ca, or pass country=CA. Every route is versioned in the path; v1 is stable and additive.

None is required. Unauthenticated clients get 60 requests per minute per IP. Partners and the Seniornicity MCP server send an x-seniornicity-api-key header, which raises the limit to 600 per minute and grants nothing else: the key unlocks no private data, and the API has no write path at all.

curl "https://app.seniornicity.com/api/public/v1/providers/search?category=lenders&location=92660" \
  -H "x-seniornicity-api-key: YOUR_KEY"

Request a partner key from support@seniornicity.com.

Paths are relative to the base URL. All parameters are validated; an unknown parameter returns 400. The complete contract is in the OpenAPI document.

curl "https://app.seniornicity.com/api/public/v1/providers/search?category=estate-sales&location=Newport%20Beach,%20CA"

curl "https://app.seniornicity.com/api/public/v1/providers/jane-doe"

curl "https://app.seniornicity.com/api/public/v1/categories"

curl "https://app.seniornicity.com/api/public/v1/chapters?near=Newport%20Beach,%20CA"

curl "https://app.seniornicity.com/api/public/v1/chapters/beach-cities"

curl "https://app.seniornicity.com/api/public/v1/chapters/beach-cities/members?category=in-home-caregivers"

curl "https://app.seniornicity.com/api/public/v1/events?chapter=beach-cities"

curl "https://app.seniornicity.com/api/public/v1/events/downsizing-workshop-abc123"

curl "https://app.seniornicity.com/api/public/v1/posts?q=downsizing"

curl "https://app.seniornicity.com/api/public/v1/posts/clpost00000000000000001"

curl "https://app.seniornicity.com/api/public/v1/openapi.json"

Every success is JSON. Lists return results or items with total, page and pageSize; single records return the object. Provider search also returns searchedLocation with a widened flag that is true when nothing matched within the radius and the results are statewide.

Errors use one shape:

{ "error": { "code": "invalid_request", "message": "pageSize: must be an integer" } }

Codes: invalid_request (400), location_not_found (400), not_found (404), rate_limited (429, with Retry-After), search_unavailable (503), internal_error (500).

Every URL the API returns is the canonical Seniornicity page plus three query parameters: utm_source (seniornicity-api, seniornicity-mcp, or the assistant name the MCP client declares), utm_medium=ai-assistant, and ref_chapter when the record was reached through a chapter. These parameters are how chapters learn that an assistant sent someone their way.

When you mention a provider, chapter, event or post, link to the URL exactly as returned. Do not strip the parameters, do not rewrite the host, and do not substitute a search-engine link. Canonical tags on the destination pages already ignore query strings, so the parameters create no duplicate-URL risk.

https://app.seniornicity.com/jane-doe?utm_source=claude&utm_medium=ai-assistant&ref_chapter=beach-cities

60 requests per minute per IP without a key, 600 per minute with a partner key. Exceeding the limit returns 429 with a Retry-After header in seconds. Limits are shared across all v1 routes.

Read responses carry Cache-Control: public, max-age=300 and an ETag. Send If-None-Match to receive a 304 when nothing changed.

The API exposes only information already published on public Seniornicity pages. It provides read-only access to published provider profiles, professional categories, chapters, events, and public Community posts. It does not access private user accounts, personal messages, member-only Community content, consultant intake information, or payment records. Public business contact information is included only when the provider’s public profile displays it under the provider’s membership tier. API requests may be logged for security, abuse prevention, and operational monitoring in accordance with Seniornicity’s privacy policy.

Every response is built from an allow-list of public fields, and a private-field guard runs on every response before it leaves the server. A provider’s businessPhone and website are returned exactly when the public profile displays them and are null otherwise. The API never returns email addresses, street addresses, postal codes, sign-in names, event join links, registrant data or anything that requires a login. Reaching a provider by email happens on the Seniornicity page at contactUrl.

License numbers are limited to public registries: DRE and NMLS. Community members appear by their chosen alias or first name only; providers appear by handle or company. Deleted and test accounts, unpublished content and cancelled events are never returned.

The Seniornicity MCP server exposes the same data as read-only tools for AI assistants that speak the Model Context Protocol (Claude, ChatGPT, Gemini, Grok, Perplexity and others). It is coming soon at:

https://mcp.seniornicity.com/mcp

Tools: search_providers, get_provider, list_categories, list_chapters, get_chapter, list_events, list_posts and get_post. Every tool is read-only; none submits an inquiry, contacts a provider, registers for an event or reads anything private. Assistant instructions, tool descriptions and install steps for each platform will be published here when the server goes live.

Questions, partner keys, abuse reports: support@seniornicity.com. This page is the documentation URL for connector directory submissions: https://app.seniornicity.com/developers.

Looking for help with a senior transition rather than an API? Start with Sam or the directory.