Fundable People Discovery API

Use the Fundable People Discovery API to discover founders, employees, angels, and lead investors. Send person type, personal attributes, employer or investment filters, and pagination to the original Fundable REST endpoint using the documented request contract. Use it for contact sourcing, founder research, and investor discovery, connecting the returned records to the rest of your research or enrichment workflow. Review the detail page for supported parameters, request and response examples, identifier formats, and the configured per-request price. Examples describe the documented interface and should be checked against your own authorized upstream account before production use.

Selected price
Composite rule pricing Published pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* object
Optional parameters (8)
company object
Current-employer attribute filters. Setting any field implicitly requires the person to have a current employer.
identifiers object
Look up specific people by identifier
investor object
Filters on the investor entity (firm) and on the person's deal activity. Setting any field (including any nested `deals.*` field) implicitly requires the person to be an investor.
Page number (0-based)
Number of results per page (max 500)
person object
Person attribute filters
Restrict results to one population. `company` returns only people with a current employer (founders, executives, employees). `investor` returns only people who invest. `any` (default) returns the union — anyone matching the other filter blocks regardless of population.
Sort order. All values are universally accepted — non-applicable values (e.g. `lead_deal_count` when no investor filter is set) resolve to 0 / null via COALESCE and naturally sort to the bottom (DESC). Ignored when `company.search_query` or `investor.deals.search_query` is set (results are then ordered by semantic relevance).
Use the Fundable People Discovery API to discover founders, employees, angels, and lead investors. Send person type, personal attributes, employer or investment filters, and pagination to the original Fundable REST endpoint using the documented request contract. Use it for contact sourcing, founder research, and investor discovery, connecting the returned records to the rest of your research or enrichment workflow. Review the detail page for supported parameters, request and response examples, identifier formats, and the configured per-request price. Examples describe the documented interface and should be checked against your own authorized upstream account before production use.

Sample response

{
  "data": {
    "people": [
      {
        "about": "<about>",
        "city": "<city>",
        "country_code": "US",
        "crunchbase_url": "https://example.com",
        "current_company": {
          "domain": "<domain>",
          "id": "550e8400-e29b-41d4-a716-446655440000",
          "name": "<name>",
          "permalink": "<permalink>"
        },
        "education_history": [
          {
            "degree": "<degree>",
            "description": "<description>",
            "end_date": "<end_date>",
            "field_of_study": "<field_of_study>",
            "school_id": "<school_id>",
            "school_name": "<school_name>",
            "school_url": "https://example.com",
            "start_date": "<start_date>"
          }
        ],
        "employment_history": [
          {
            "company_id": "<company_id>",
            "company_name": "<company_name>",
            "company_url": "https://example.com",
            "description": "<description>",
            "end_date": "2026-01-01",
            "is_current": false,
            "location": "<location>",
            "start_date": "2026-01-01",
            "title": "<title>"
          }
        ],
        "filtered_deal_count": 0,
        "filtered_lead_count": 0,
        "filtered_most_recent_date": "2026-01-01",
        "has_led_deal": false,
        "id": "550e8400-e29b-41d4-a716-446655440000",
        "investment_firms": [
          {
            "deal_count": 0,
            "domain": "<domain>",
            "id": "550e8400-e29b-41d4-a716-446655440000",
            "last_deal_date": "2026-01-01",
            "name": "<name>",
            "permalink": "<permalink>"
          }
        ],
        "investor_highlights": {
          "deal_count_last_12_months": 0,
          "lead_deal_count": 0,
          "lead_deal_count_last_12_months": 0,
          "most_recent_deal_date": "2026-01-01",
          "top_industries": [
            {
              "count": 0,
              "name": "<name>",
              "permalink": "<permalink>"
            }
          ],
          "top_locations": [
            {
              "count": 0,
              "full_name": "<full_name>",
              "name": "<name>",
              "permalink": "<permalink>",
              "type": "CITY"
            }
          ],
          "top_round_types": [
            {
              "count": 0,
              "type": "SERIES_A"
            }
          ],
          "total_deal_count": 12
        },
        "is_angel": false,
        "is_founder": false,
        "is_investor": false,
        "linkedin_url": "https://example.com",
        "location": "San Francisco, CA",
        "name": "Jane Doe",
        "title": "CEO",
        "twitter_url": "https://example.com"
      }
    ]
  },
  "message": "<message>",
  "meta": {
    "credit_source": "monthly",
    "credits_used": 1,
    "monthly_credits_remaining": 990,
    "page": 0,
    "page_size": 10,
    "purchased_credits_remaining": 500,
    "total_count": 1250
  },
  "success": true
}

Response result

Response structure

Inferred from examples
  • dataobject
    • peopleobject[]
      • aboutstring
      • citystring
      • country_codestring
      • crunchbase_urlstring
      • current_companyobject
        • domainstring
        • idstring
        • namestring
        • permalinkstring
      • education_historyobject[]
        • degreestring
        • descriptionstring
        • end_datestring
        • field_of_studystring
        • school_idstring
        • school_namestring
        • school_urlstring
        • start_datestring
      • employment_historyobject[]
        • company_idstring
        • company_namestring
        • company_urlstring
        • descriptionstring
        • end_datestring
        • is_currentboolean
        • locationstring
        • start_datestring
        • titlestring
      • filtered_deal_countinteger
      • filtered_lead_countinteger
      • filtered_most_recent_datestring
      • has_led_dealboolean
      • idstring
      • investment_firmsobject[]
        • deal_countinteger
        • domainstring
        • idstring
        • last_deal_datestring
        • namestring
        • permalinkstring
      • investor_highlightsobject
        • deal_count_last_12_monthsinteger
        • lead_deal_countinteger
        • lead_deal_count_last_12_monthsinteger
        • most_recent_deal_datestring
        • top_industriesobject[]
          • countinteger
          • namestring
          • permalinkstring
        • top_locationsobject[]
          • countinteger
          • full_namestring
          • namestring
          • permalinkstring
          • typestring
        • top_round_typesobject[]
          • countinteger
          • typestring
        • total_deal_countinteger
      • is_angelboolean
      • is_founderboolean
      • is_investorboolean
      • linkedin_urlstring
      • locationstring
      • namestring
      • titlestring
      • twitter_urlstring
  • messagestring
  • metaobject
    • credit_sourcestring
    • credits_usedinteger
    • monthly_credits_remaininginteger
    • pageinteger
    • page_sizeinteger
    • purchased_credits_remaininginteger
    • total_countinteger
  • successboolean

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Fundable People Discovery API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.