> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# PredictLeads: Discover Portfolio Company Connections

> List portfolio companies found on the portfolio pages of VCs, accelerators and incubators, newest first. Includes SDK V2 examples, schemas, and cost.

List portfolio companies found on the portfolio pages of VCs, accelerators and incubators, newest first.

> [!NOTE]
>
> Tool ID: `predictleads_discover_portfolio_company_connections`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'predictleads_discover_portfolio_company_connections',
  {
    "first_seen_at_from": "2026-01-15",
    "first_seen_at_until": "2026-01-15",
    "last_seen_at_from": "2026-01-15"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute predictleads_discover_portfolio_company_connections --input '{
  "first_seen_at_from": "2026-01-15",
  "first_seen_at_until": "2026-01-15",
  "last_seen_at_from": "2026-01-15"
}' --json
```

## Example response

The static output schema lacks the details for a reliable example. Use `deepline describe predictleads_discover_portfolio_company_connections --json` for the complete live contract.

## Input reference

Returns the Portfolio Companies found on the portfolio pages of thousands of VCs, accelerators, and incubators, as a list of Connections categorized as `investor`, ordered by the `first_seen_at`, descending.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.first_seen_at_from` | `string` | No | — | Only return `TechnologyDetections` first seen after given date (ISO 8601). Format: `date`. |
| `payload.first_seen_at_until` | `string` | No | — | Only return `TechnologyDetections` first seen before given date (ISO 8601). Format: `date`. |
| `payload.last_seen_at_from` | `string` | No | — | Only return `TechnologyDetections` last seen after given date (ISO 8601). Format: `date`. |
| `payload.last_seen_at_until` | `string` | No | — | Only return `TechnologyDetections` last seen before given date (ISO 8601). Format: `date`. |
| `payload.page` | `integer` | No | `1` | Page number of shown items. **NOTE**: If the parameter is not provided, the meta property `count` will be omitted from response for performance reasons. Minimum: 1. |
| `payload.limit` | `integer` | No | `30` | Limit the number of shown items per page. Maximum: 1000. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Returns the Portfolio Companies found on the portfolio pages of thousands of VCs, accelerators, and incubators, as a list of Connections categorized as `investor`, ordered by the `first_seen_at`, descending.",
    "properties": {
      "first_seen_at_from": {
        "type": "string",
        "description": "Only return `TechnologyDetections` first seen after given date (ISO 8601).",
        "format": "date"
      },
      "first_seen_at_until": {
        "type": "string",
        "description": "Only return `TechnologyDetections` first seen before given date (ISO 8601).",
        "format": "date"
      },
      "last_seen_at_from": {
        "type": "string",
        "description": "Only return `TechnologyDetections` last seen after given date (ISO 8601).",
        "format": "date"
      },
      "last_seen_at_until": {
        "type": "string",
        "description": "Only return `TechnologyDetections` last seen before given date (ISO 8601).",
        "format": "date"
      },
      "page": {
        "type": "integer",
        "description": "Page number of shown items. **NOTE**: If the parameter is not provided, the meta property `count` will be omitted from response for performance reasons.",
        "default": 1,
        "minimum": 1
      },
      "limit": {
        "type": "integer",
        "description": "Limit the number of shown items per page.",
        "default": 30,
        "maximum": 1000
      }
    },
    "required": [],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Since 2019, PredictLeads has detected over 230 million business connections between companies globally. The Company Connections Dataset describes relationships between some 48 million companies. Connections are sourced from Case Study pages, Testimonials, Our Customers sections, and is done through image recognition of company logos. The Connections Dataset includes fields such as Connection Category, Source Category, Source URL, Context, First Seen At, Last Seen At, and other Connection See the live schema for the complete constraint. |
| `result.data.data` | `array` | Yes | — | — |
| `result.data.data[].id` | `string` | Yes | — | ID of the `Connection` object. Format: `uuid`. |
| `result.data.data[].type` | `"connection"` | Yes | — | Type of the `Connection` object. |
| `result.data.data[].attributes` | `object` | Yes | — | Attributes of the `Connection` object. |
| `result.data.data[].attributes.category` | `"partner" \| "vendor" \| "integration" \| "investor" \| "parent" \| "rebranding" \| "published_in" \| "badge" \| "other"` | Yes | — | `Connection` category. |
| `result.data.data[].attributes.source_category` | `"undefined" \| "partner_page" \| "vendor_page" \| "integration_page" \| "investor_page" \| "about_page" \| "parent_page" \| "case_study_page" \| "testimonial_page" \| "manual_input" \| "domain_redirect" \| "same_subpage" \| "partner_section" \| "vendor_section" \| "integration_section" \| "investor_section" \| "parent_section" \| "case_study_section" \| "testimonial_section" \| "social_section" \| "published_in_section" \| "vendor_inverse_section" \| "investor_inverse_section" \| "parent_inverse_section" \| "footer" \| "header" \| "vendor_inverse_page" \| "cookie_section" \| "badge_section"` | Yes | — | Describes source where the `Connection` category was found. Allowed: `undefined`, `partner_page`, `vendor_page`, `integration_page`, `investor_page`, `about_page`, `parent_page`, `case_study_page`, `testimonial_page`, `manual_input`, `domain_redirect`, `same_subpage`, `partner_section`, `vendor_section`, `integration_section`, `investor_section`, `parent_section`, `case_study_section`, `testimonial_section`, `social_section`, `published_in_section`, `vendor_inverse_section`, See the live schema for the complete constraint. |
| `result.data.data[].attributes.source_url` | `null \| string` | Yes | — | URL where `Connection` information was found. Format: `uri`. |
| `result.data.data[].attributes.individual_source_url` | `null \| string` | Yes | — | URL where Connection`additional information was found. Format:`uri\`. |
| `result.data.data[].attributes.context` | `null \| string` | Yes | — | Text found near the connection. Often contains additional relationship information between the two companies. |
| `result.data.data[].attributes.first_seen_at` | `string` | Yes | — | Date & time (ISO 8601) of when the `Connection` was first seen. Format: `date-time`. |
| `result.data.data[].attributes.last_seen_at` | `string` | Yes | — | Date & time (ISO 8601) of when the `Connection` was last seen. Format: `date-time`. |
| `result.data.data[].relationships` | `object` | Yes | — | The data contains references to related objects listed in the `included` property. Order of companies is guaranteed and necessary to preserve the meaning of the `category`. For example: Company1 is a `vendor` to Company2. |
| `result.data.data[].relationships.company1` | `object` | Yes | — | The data contains a reference to related `CompanyLite` object listed in the `included` property. |
| `result.data.data[].relationships.company1.data` | `object` | Yes | — | — |
| `result.data.data[].relationships.company1.data.id` | `string` | Yes | — | ID of the included `CompanyLite` object. Format: `uuid`. |
| `result.data.data[].relationships.company1.data.type` | `"company"` | Yes | — | Type of the included `CompanyLite` object. |
| `result.data.data[].relationships.company2` | `object` | Yes | — | The data contains a reference to related `CompanyLite` object listed in the `included` property. |
| `result.data.data[].relationships.company2.data` | `object` | Yes | — | — |
| `result.data.data[].relationships.company2.data.id` | `string` | Yes | — | ID of the included `CompanyLite` object. Format: `uuid`. |
| `result.data.data[].relationships.company2.data.type` | `"company"` | Yes | — | Type of the included `CompanyLite` object. |
| `result.data.data[].relationships.technology` | `object` | Yes | — | The data contains a reference to related `TechnologyLite` object listed in the `included` property. |
| `result.data.data[].relationships.technology.data` | `object \| null` | Yes | — | — |
| `result.data.data[].relationships.technology.data.id` | `string` | Yes | — | ID of the included `TechnologyLite` object. Format: `uuid`. |
| `result.data.data[].relationships.technology.data.type` | `"technology"` | Yes | — | Type of the included `TechnologyLite` object. |
| `result.data.included` | `array` | Yes | — | Contains objects referenced in property `relationships`. |
| `result.data.meta` | `object` | No | — | Meta information about `ConnectionsDataset` object. |
| `result.data.meta.schema_version` | `string` | Yes | — | Represents schema version of objects. |
| `result.data.meta.record_state` | `"active"` | Yes | — | Represents record state of objects. |
| `result.data.meta.count` | `integer` | No | — | Total number of results. **NOTE**: Only included in API responses when the request parameter `page` is provided, for performance reasons. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

> [!NOTE]
>
> This output schema is too large for an inline display. Read the complete live contract with `deepline describe predictleads_discover_portfolio_company_connections --json`.

## Deepline cost

* Pricing model: `per_result` (per result).
* Estimated Deepline credits: `0.56` per pricing unit.

## Related documentation

* [PredictLeads provider guide](https://deepline.com/docs/providers/predictleads/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.