W Wellspent
Discovery API

Power advisor discovery in the next crop of personal finance apps.

The same structured advisor graph that AI assistants ingest is available to developers building personal finance products. Read access to fee-only advisor records, specialties, audiences, and geographies. Application-gated.

Who it's for

Who builds with this.

Personal finance apps

You're building the product where users consolidate their money. When someone asks "who should I talk to?", a structured match beats a directory listing.

AI assistants and agents

Your assistant answers complex personal-finance questions. When the right answer is a fee-only advisor with a specific specialty, our API returns the structured record your model can cite.

Fintech tooling and CRMs

You're building the developer infrastructure that other wealth-tech runs on. Verify advisor records, enrich profile data, or check fee-only status against canonical sources.

What's in the API

The same structured layer behind find.wellspent.co.

  • GET /v1/advisors Paginated search by country, region, specialty, audience, and free-text query.
  • GET /v1/advisors/{slug} Full canonical record for one advisor: bio, fee models, fiduciary status, credentials, and the advisor's own description of their ideal client (high-signal input for matching agents).
  • GET /v1/specialties Canonical specialty taxonomy used to filter advisors.
  • GET /v1/audiences Canonical audience taxonomy (founders, physicians, HENRY, cross-border families, more).
  • GET /v1/openapi.json OpenAPI 3.1 spec. Drop into Swagger, Redoc, Postman, or your codegen pipeline.
How it works

Authenticate, search, render.

1. Get an API key

Submit an application below. We review weekly. Approved developers receive a key over email.

2. Authenticate

Pass Authorization: Bearer wsk_live_… on every request.

3. Read

Search and fetch advisor records. Cursor-paginated, JSON responses, predictable error envelope.

Example: search advisors who handle equity comp in California

curl https://api.wellspent.co/v1/advisors \
  -H "Authorization: Bearer wsk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -G \
  --data-urlencode "country=us" \
  --data-urlencode "region=california" \
  --data-urlencode "specialty=equity-compensation"

Example response

{
  "data": [
    {
      "slug": "jane-reyes",
      "name": "Jane Reyes, CFP",
      "credentials": ["CFP", "MBA"],
      "firm": "Bridgestone Planning",
      "location": {
        "country": "us",
        "region": "California",
        "region_slug": "california",
        "city": "Palo Alto"
      },
      "is_fiduciary": true,
      "specialties": ["Equity compensation", "Founders (pre-exit)"],
      "audiences": ["Tech employees", "Founders"],
      "fee_models": ["Flat Fee/Retainer"],
      "founded_year": 2018,
      "ideal_client": "Mid-career tech employees with concentrated RSU and ISO positions, navigating a single-trigger or double-trigger IPO and the AMT decisions that come with it.",
      "profile_url": "https://find.wellspent.co/advisors/jane-reyes/",
      "status": "claimed"
    }
  ],
  "pagination": {
    "limit": 25,
    "next_cursor": "jane-reyes",
    "has_more": true
  }
}

Download OpenAPI spec →

Limits & trust

Built for production.

1,000 requests/day

Default tier. Higher quotas after vetting and a clear use case.

Versioned + stable

Versioned URL path, deprecation warnings via response header, no breaking changes mid-version.

Read-only, public-projection

The API exposes the same data published at find.wellspent.co. Member-private fields never cross the boundary.

Attribution required

Apps using the API surface advisor profile links back to find.wellspent.co. Keeps trust circulating in the graph.

Apply for access

Tell us what you're building.

We review applications weekly. Approved developers receive a key over email along with usage docs.

We'll respond within seven days. If your use case fits and we can support the volume, you'll get a key.