The Top-Rated Team LinkedIn API is an HTTP API that acts as a LinkedIn account you have connected. It reads what that account can see and does what that account can do: search people and posts, open chats and send messages, publish posts, comment, react, send invitations and InMail, and work with company pages, Recruiter projects and jobs. Everything is under one address, and every request names the account it is acting as.
curl "https://top-rated.team/linkedin/v2/$ACCOUNT_ID/chats" \ -H "X-API-KEY: $MAKEHYBRID_KEY"
That is the whole shape of it. One header carries the API key, which says which organisation you are; one path segment carries the account id, which says which of that organisation's connected accounts to act as. There is no OAuth dance, no app review and no second token to refresh.
How it differs from LinkedIn's own APIs
LinkedIn publishes partner APIs — Marketing, Talent, Sales — and they are a different kind of thing. They are granted to approved companies for approved purposes, they act on a page or an advertising account rather than on a person, and the parts most teams actually want are not in them: you cannot read a member's own inbox, send a connection invitation, or publish to a personal profile.
This API acts as a member. That is what makes the member's own messages, invitations and feed reachable, and it is also why pacing matters here and does not there: the account doing the work is a real account, with a real account's limits.
Connecting an account
An account is connected by signing in on a Top-Rated Team page, with either the session cookie from a browser already signed in or the account's own email and password. Both ask which country to sign in from, because a sign-in that arrives from the wrong side of the world is the one LinkedIn stops to ask about. Once it is connected you get an account id, and that id is what every later call names.
The same thing without writing code
Everything the API does is also available to an AI assistant over MCP, at https://top-rated.team/linkedin/mcp/<your API key>. It is the same account, the same key and the same limits — a different way of reaching them, for when the work is a conversation rather than a script.
An account id is a security boundary, not a label: a call that names an account your organisation did not connect is answered 404, the same answer as an id that does not exist, so the ids of other customers cannot be probed.
What it costs
Nine dollars per seat per month, seven from a hundred seats, where a seat is one connected LinkedIn account. The first thirty days are free and cover one seat, which is enough to find out whether any of this works for you.
Questions people ask
Can an AI agent use this without me writing any code?
Yes, and that is the usual way in. Paste the MCP address into an assistant, or tick Top-Rated Team for a room AI agent, and the same operations are available in plain words. The curl examples are there because a script is sometimes the right tool, not because one is required.
Does an AI agent need its own LinkedIn account?
No. It acts as an account the organization has already connected, which is also what a seat is. Ten AI agents working through one connected account are one seat.