LinkedIn leads: structured people and company data for outreach and research.
Tools
- linkedin_resolve_url 2 cr: Identify a LinkedIn URL.
- linkedin_get_profile 4 cr: Get a LinkedIn person profile.
- linkedin_search_people 10 cr: Search people on LinkedIn.
- linkedin_get_company 4 cr: Get a LinkedIn company.
- linkedin_get_posts 4 cr: Get recent posts by a person or company.
get_usage checks balance and works the same way across every platform: free, 0 credits. /docs/tools/get_usage.
Quickstart
1. Call it, no key
curl "https://api.veezee.io/v1/linkedin/profiles?identifier=williamhgates"No signup, no card, no key. Keyless calls run under a shared budget of 20 credits per IP per day, recent data only, no realtime, no Idempotency-Key needed.
2. Or connect over MCP, no key
https://mcp.veezee.io/linkedintransport: streamable-http, same keyless budget as REST.
3. Hit the daily cap? Buy a key
The error names upgrade_url: /upgrade. Pick a pack, pay, and your API key is shown once on the confirmation page. Send it as Authorization: Bearer <api_key> on every REST call (plus an Idempotency-Key header on metered routes), or add it to your MCP client's connection headers. That checkout is the only human step in the product.
What comes back
url_resolution, person, people_search, company, posts. Full field lists: /docs/fields.
Limits
- Every tool is read-only: no posting, commenting, or messaging.
- No contact details: no email addresses or phone numbers.
- No company search by name: linkedin_get_company takes a URL, slug, or domain; resolve a name with linkedin_search_people's current_company filter instead.
- No keyword search across LinkedIn posts: linkedin_get_posts returns one entity's recent posts, not a search.
Full tool reference: /docs.