> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/linkedin-1.md).

# Treg LinkedIn

Read public LinkedIn profiles and company pages through [Treg](https://treg.to), without a LinkedIn account or your own scraper. Needs a Treg API key from treg.to. Every paid call is billed by Treg from your team's prepaid balance at the provider's price, and the block reports the charge as `cost_usd`. Treg blocks run on your own Treg key, and the platform charges no credits for them.

## Treg Get LinkedIn Company

### What it is

Read a LinkedIn company page through Treg, without a LinkedIn account or scraper.

### How it works

The block sends one request to `POST https://treg.to/call/treg.linkedin.company.profile` with your Treg key in the `X-Treg-Token` header. Treg tries the providers that do this job, your team's own keys first and then the cheapest per answer, and moves on when one fails or has no answer, until one answers or `max_cost_usd` (sent as `X-Treg-Route-Max-Cost`) would be passed. Turning off `try_more_providers` stops after the first provider. When nobody has an answer the block emits `found: false` rather than an error; some providers bill a miss, so `cost_usd` can be above zero. Failed calls raise a block error with Treg's reason (for example an empty balance, with the top-up link) and are not retried, because a repeated paid call can be billed again. Give the company page URL or just its handle.

### Inputs

| Input                | Description                                                                                                                                              | Type  | Required |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | -------- |
| max\_cost\_usd       | The most this run may spend, in USD, across every provider Treg tries. A call that would go over it is refused without charge.                           | float | No       |
| try\_more\_providers | When a provider has no answer, try the next cheapest one, up to the spending cap. Some providers bill a miss. Turn off to stop after the first provider. | bool  | No       |
| linkedin\_url        | The company page URL, e.g. '<https://www.linkedin.com/company/modal-labs>', or just the handle, e.g. 'modal-labs'.                                       | str   | Yes      |

### Outputs

| Output           | Description                                                                                                               | Type            |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------- |
| error            | Error message if the operation failed                                                                                     | str             |
| found            | True when a provider had an answer, false when none did.                                                                  | bool            |
| served\_by       | The Treg tool that answered, e.g. 'hunter.email.finder'. Emitted only when one did.                                       | str             |
| providers\_tried | Providers Treg asked, in order.                                                                                           | List\[str]      |
| cost\_usd        | What Treg charged for this run, in USD.                                                                                   | float           |
| call\_id         | Treg's id for this call, to look it up in your Treg activity.                                                             | str             |
| advice           | Treg's note on how far to trust the answer, e.g. that an email was found but not checked. Emitted only when there is one. | str             |
| raw              | The serving provider's full answer, with fields beyond the standard ones. Emitted only when one answered.                 | Dict\[str, Any] |
| name             | Company name.                                                                                                             | str             |
| description      | The page's About text.                                                                                                    | str             |
| website          | Website URL.                                                                                                              | str             |
| followers        | Follower count.                                                                                                           | int             |
| employees        | Headcount or headcount range.                                                                                             | str             |
| location         | Headquarters.                                                                                                             | str             |
| linkedin\_url    | Canonical page URL.                                                                                                       | str             |

### Possible use case

**Account research**: Read a company's LinkedIn description, size and follower count.

**Monitoring**: Track follower growth for a list of companies.

***

## Treg Get LinkedIn Profile

### What it is

Read a LinkedIn member's public profile through Treg, without a LinkedIn account or scraper.

### How it works

The block sends one request to `POST https://treg.to/call/treg.linkedin.user.profile` with your Treg key in the `X-Treg-Token` header. Treg tries the providers that do this job, your team's own keys first and then the cheapest per answer, and moves on when one fails or has no answer, until one answers or `max_cost_usd` (sent as `X-Treg-Route-Max-Cost`) would be passed. Turning off `try_more_providers` stops after the first provider. When nobody has an answer the block emits `found: false` rather than an error; some providers bill a miss, so `cost_usd` can be above zero. Failed calls raise a block error with Treg's reason (for example an empty balance, with the top-up link) and are not retried, because a repeated paid call can be billed again. Give a profile URL or just the handle. Counts such as followers are returned as numbers when the provider gives one; a value like "500+" is left out of `connections` and stays in `raw`.

### Inputs

| Input                | Description                                                                                                                                              | Type  | Required |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | -------- |
| max\_cost\_usd       | The most this run may spend, in USD, across every provider Treg tries. A call that would go over it is refused without charge.                           | float | No       |
| try\_more\_providers | When a provider has no answer, try the next cheapest one, up to the spending cap. Some providers bill a miss. Turn off to stop after the first provider. | bool  | No       |
| linkedin\_url        | The profile URL, e.g. '<https://www.linkedin.com/in/janedoe>', or just the handle, e.g. 'janedoe'.                                                       | str   | Yes      |

### Outputs

| Output           | Description                                                                                                               | Type            |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------- |
| error            | Error message if the operation failed                                                                                     | str             |
| found            | True when a provider had an answer, false when none did.                                                                  | bool            |
| served\_by       | The Treg tool that answered, e.g. 'hunter.email.finder'. Emitted only when one did.                                       | str             |
| providers\_tried | Providers Treg asked, in order.                                                                                           | List\[str]      |
| cost\_usd        | What Treg charged for this run, in USD.                                                                                   | float           |
| call\_id         | Treg's id for this call, to look it up in your Treg activity.                                                             | str             |
| advice           | Treg's note on how far to trust the answer, e.g. that an email was found but not checked. Emitted only when there is one. | str             |
| raw              | The serving provider's full answer, with fields beyond the standard ones. Emitted only when one answered.                 | Dict\[str, Any] |
| full\_name       | Full name.                                                                                                                | str             |
| first\_name      | First name.                                                                                                               | str             |
| last\_name       | Last name.                                                                                                                | str             |
| headline         | Profile headline.                                                                                                         | str             |
| location         | Location on the profile.                                                                                                  | str             |
| about            | The About section.                                                                                                        | str             |
| followers        | Follower count.                                                                                                           | int             |
| connections      | Connection count.                                                                                                         | int             |
| linkedin\_url    | Canonical profile URL.                                                                                                    | str             |

### Possible use case

**Meeting prep**: Pull a person's headline and About section before a call.

**Candidate screening**: Read profiles for a shortlist in bulk.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/linkedin-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
