[ DELIVERY METHODS ]

One source of social data. Three ways in.

Call it over raw HTTPS, hand it to an AI agent, or pull it into a typed TypeScript app. Same data, same fields, same sub-second responses — whichever shape your stack prefers.

{ }API◇MCP</>SDK
{ }
[ API ]

Data as an API. Plain HTTPS.

Every platform action is a single POST endpoint that returns normalized JSON. The browser sessions, proxies, and anti-bot handling all run on our side — your code sends a bearer token and reads back the response, from any language or runtime that can make an HTTP call.

✓One POST endpoint per platform action
✓Bearer-token auth, no OAuth dance
✓Every response tagged with timing & credit cost
Read the API docs →
request
curl -X POST \
https://api.bridgly.app/linkedin/get-profile-from-url \
-H "Authorization: Bearer $BRIDGLY_KEY" \
-H "Content-Type: application/json" \
-d '{"memberIdentity":"satya-nadella"}'
response200 · 428 ms
{
  "timeMs": 428,
  "creditsCost": 1,
  "data": {
    "name": "Satya Nadella",
    "headline": "Chairman & CEO, Microsoft",
    "followers": 10840213
  }
}
agent sessionvia bridgly mcp
user
Find the CEO of Microsoft on LinkedIn and tell me their follower count.
tool call
linkedin_get_profile_from_url({ memberIdentity: "satya-nadella" })
tool result
{ name: "Satya Nadella", headline: "Chairman & CEO, Microsoft", followers: 10840213 }
assistant
Satya Nadella is Chairman & CEO of Microsoft. He has 10,840,213 followers on LinkedIn.
▮
[ MCP ]

Give your AI eyes on social.

Bridgly hosts a remote Model Context Protocol server, so any MCP-aware client — Claude, Cursor, Codex — connects over HTTP and pulls live profiles, posts, and follower data as native tools. No glue code, no scraping logic in your prompts.

✓Typed tools the model discovers on its own
✓Remote server over Streamable HTTP
✓One tool per endpoint, auto-generated
mcp.json
{
  "mcpServers": {
    "bridgly": {
      "url": "https://mcp.bridgly.app/mcp",
      "headers": { "Authorization": "Bearer bgly_YOUR_KEY" }
    }
  }
}
</>
[ SDK ]

TypeScript, fully typed.

The official SDK ships ready-made types and API clients for every endpoint — autocomplete on every field, compile-time safety on every response, retries and pagination handled for you. Write less glue, ship faster.

✓Typed inputs and responses on every call
✓Errors returned as typed results, never thrown
✓ESM & CJS builds, zero config
$ npm i bridgly
View on npm →
</> enrich.ts
import { Bridgly } from "bridgly";
const bridgly = new Bridgly({ apiKey: process.env.BRIDGLY_KEY });
const profile = await bridgly.linkedin.getProfileFromUrl({
memberIdentity: "satya-nadella",
});
profile.▮
◆followersnumber
◆handlestring
◆headlinestring
◆locationstring
◆namestring
◆verifiedboolean
(property) Profile.followers: number

Pick a method. Pull your first profile.

Start with 100 free credits — the same data flows through API, MCP, and SDK alike.

Start with 100 credits →