Veezee vs LinkdAPI
What LinkdAPI publishes
LinkdAPI is a LinkedIn-focused B2B data API advertising 50+ endpoints across 10+ data categories: profiles with employment history, education, and skills, companies, a searchable index of 60k+ active job listings, posts, articles, services, contacts, people search, and Sales Navigator intelligence (linkdapi.com). It ships official SDKs for three languages, an OpenAPI spec, and a Postman collection.
Pricing is volume-tiered and cheap: nine tiers from 100 credits per dollar (Testing) up to 400 credits per dollar at the top, with rate limits from 7 to 550 requests per minute; its own blog works this out to roughly half a cent to one cent per enrichment (linkdapi.com/pricing, linkdapi.com/blog/professional-data-api-pricing). 100 free credits to start, no card, and credits never expire.
What it does not ship, as of 2026-07-11: an MCP server, or an llms.txt (the llms.txt path returns HTML, not a spec). Getting an API key requires a human to sign up in a dashboard.
What Veezee offers
Veezee is scoped to LinkedIn only, with seven tools over MCP and REST: provision, resolve_url, get_profile, search_people, get_company, get_posts, get_usage. An agent can mint its own key in one provision call (500 credits free, no signup, no card), and a keyless taste of 20 credits per IP per day works before any key at all. Auth is API key only (no OAuth); no uptime guarantee is published.
| LinkdAPI | Veezee | |
|---|---|---|
| Scope | LinkedIn, 50+ endpoints incl. jobs and Sales Navigator | LinkedIn, 7 tools; no jobs, no Sales Navigator |
| Pricing | 100-400 credits per dollar by tier; roughly half a cent to one cent per enrichment | per call: 4 credits profile, 10 credits search, 4 credits company, 4 credits posts |
| Free start | 100 credits, no card, human signup required | 500 credits credits, no card, no signup: the agent provisions itself |
| MCP server | none as of 2026-07-11 | hosted, streamable-http; listed as io.veezee/linkedin (registry.modelcontextprotocol.io) |
| llms.txt | path returns HTML, not a spec | yes, plus markdown twins of every docs page |
| Contact data | a "contacts" category is listed (contents not publicly itemized) | none: no emails, no phone numbers |
Where each wins
LinkdAPI wins on price and LinkedIn breadth: it is several times cheaper per call at volume, and it serves job listings and Sales Navigator intelligence that Veezee does not have. A high-volume enrichment pipeline optimizing dollars per record should pick it, and if it needs contact details, Veezee is not even a candidate.
Veezee wins when the caller is an agent. A hosted MCP server, typed tools, markdown docs, and a key the agent mints itself in one provision call, with a keyless taste before that: an agent can discover, evaluate, and start using Veezee unattended. That path does not exist on LinkdAPI today, where a human must sign up first.