{"api":"Cached employee comments","apiRows":{"Employee profile":2979,"Cached employee profile":1257,"Employee email":2364,"Cached employee email":975,"Email validation":3519,"Cached email validation":611,"Employee phone":824,"Cached employee phone":465,"Company profile":996,"Cached company profile":195,"Company headcount":214,"Cached company headcount":162,"Phone validation":572,"Cached phone validation":165,"Post comments":357,"Post reactions":335,"Employee lookalikes":160,"Cached employee lookalikes":54,"Company lookalikes":470,"Cached company lookalikes":196,"Company technologies":165,"Cached company technologies":187,"Company job count":53,"Employee posts":349,"Cached employee posts":14,"Company posts":336,"Cached company posts":10,"Company funding":100,"Cached company funding":133,"Company jobs":143,"Cached company jobs":50,"Employee search":938,"Cached employee search":278,"Company search":389,"Cached company search":210,"Job search":350,"Cached job search":30,"Reverse email lookup":289,"Cached reverse email lookup":358,"Post search":239,"Cached post search":57,"Post details":384,"Job details":351,"Employee comments":208,"Cached employee comments":14,"Employee reactions":178,"Post reposts":106,"Employee recommendations":80,"Job lookalikes":34,"Employee articles":47,"Company enrichment":446,"Cached company enrichment":1065,"People search":543,"Cached people search":1099,"Company discovery":350,"Cached company discovery":1249,"Job postings":10,"Cached job postings":206,"Job posting details":15,"Cached job posting details":76,"Person enrichment":88,"Cached person enrichment":157,"Leadership changes":17,"Cached leadership changes":71,"Company hierarchy":93},"treeCounts":{"Employee profile":{"best":90,"top":3},"Cached employee profile":{"best":63,"top":3},"Employee email":{"best":108,"top":3},"Cached employee email":{"best":42,"top":3},"Email validation":{"best":151,"top":3},"Cached email validation":{"best":27,"top":3},"Employee phone":{"best":58,"top":3},"Cached employee phone":{"best":28,"top":3},"Company profile":{"best":61,"top":3},"Cached company profile":{"best":13,"top":3},"Company headcount":{"best":15,"top":3},"Cached company headcount":{"best":8,"top":3},"Phone validation":{"best":42,"top":3},"Cached phone validation":{"best":15,"top":3},"Post comments":{"best":28,"top":3},"Post reactions":{"best":26,"top":3},"Employee lookalikes":{"best":6,"top":3},"Cached employee lookalikes":{"best":6,"top":3},"Company lookalikes":{"best":22,"top":3},"Cached company lookalikes":{"best":13,"top":3},"Company technologies":{"best":22,"top":3},"Cached company technologies":{"best":19,"top":3},"Company job count":{"best":6,"top":3},"Employee posts":{"best":32,"top":3},"Cached employee posts":{"best":2,"top":2},"Company posts":{"best":32,"top":3},"Cached company posts":{"best":1,"top":1},"Company funding":{"best":15,"top":3},"Cached company funding":{"best":12,"top":3},"Company jobs":{"best":29,"top":3},"Cached company jobs":{"best":6,"top":3},"Employee search":{"best":33,"top":3},"Cached employee search":{"best":16,"top":3},"Company search":{"best":19,"top":3},"Cached company search":{"best":12,"top":3},"Job search":{"best":28,"top":3},"Cached job search":{"best":3,"top":3},"Reverse email lookup":{"best":24,"top":3},"Cached reverse email lookup":{"best":25,"top":3},"Post search":{"best":23,"top":3},"Cached post search":{"best":5,"top":3},"Post details":{"best":37,"top":3},"Job details":{"best":28,"top":3},"Employee comments":{"best":16,"top":3},"Cached employee comments":{"best":2,"top":2},"Employee reactions":{"best":13,"top":3},"Post reposts":{"best":8,"top":3},"Employee recommendations":{"best":6,"top":3},"Job lookalikes":{"best":3,"top":3},"Employee articles":{"best":5,"top":3},"Company enrichment":{"best":46,"top":3},"Cached company enrichment":{"best":61,"top":3},"People search":{"best":48,"top":3},"Cached people search":{"best":49,"top":3},"Company discovery":{"best":38,"top":3},"Cached company discovery":{"best":65,"top":3},"Job postings":{"best":4,"top":3},"Cached job postings":{"best":17,"top":3},"Job posting details":{"best":12,"top":3},"Cached job posting details":{"best":6,"top":3},"Person enrichment":{"best":11,"top":3},"Cached person enrichment":{"best":15,"top":3},"Leadership changes":{"best":4,"top":3},"Cached leadership changes":{"best":4,"top":3},"Company hierarchy":{"best":12,"top":3}},"bestPages":{"Employee profile":["/best-linkedin-profile-api","Best LinkedIn profile API in 2026"],"Cached employee profile":["/best-cached-linkedin-profile-api","Best cached LinkedIn profile API in 2026"],"Employee email":["/best-email-finder-api","Best email finder API in 2026"],"Cached employee email":["/best-cached-email-finder-api","Best cached email finder API in 2026"],"Email validation":["/best-email-verification-api","Best email verification API in 2026"],"Cached email validation":["/best-cached-email-verification-api","Best cached email verification API in 2026"],"Employee phone":["/best-phone-finder-api","Best phone finder API in 2026"],"Cached employee phone":["/best-cached-phone-finder-api","Best cached phone finder API in 2026"],"Company profile":["/best-linkedin-company-data-api","Best LinkedIn company data API in 2026"],"Cached company profile":["/best-cached-linkedin-company-data-api","Best cached LinkedIn company data API in 2026"],"Phone validation":["/best-phone-validation-api","Best phone validation API in 2026"],"Post comments":["/best-linkedin-post-comment-api","Best LinkedIn post comment API in 2026"],"Post reactions":["/best-linkedin-post-reaction-api","Best LinkedIn post reaction API in 2026"],"Company technologies":["/best-company-technology-api","Best company technology API in 2026"],"Cached company technologies":["/best-cached-company-technology-api","Best cached company technology API in 2026"],"Employee posts":["/best-linkedin-profile-post-api","Best LinkedIn profile post API in 2026"],"Company posts":["/best-linkedin-company-post-api","Best LinkedIn company post API in 2026"],"Cached company funding":["/best-company-funding-api","Best company funding API in 2026"],"Cached company jobs":["/best-company-open-jobs-api","Best company open jobs API in 2026"],"Employee search":["/best-linkedin-people-search-api","Best LinkedIn people search API in 2026"],"Cached employee search":["/best-cached-linkedin-people-search-api","Best cached LinkedIn people search API in 2026"],"Company search":["/best-linkedin-company-search-api","Best LinkedIn company search API in 2026"],"Cached company search":["/best-cached-linkedin-company-search-api","Best cached LinkedIn company search API in 2026"],"Job search":["/best-linkedin-job-search-api","Best LinkedIn job search API in 2026"],"Cached job search":["/best-cached-linkedin-job-search-api","Best cached LinkedIn job search API in 2026"],"Reverse email lookup":["/best-reverse-email-lookup-api","Best reverse email lookup API in 2026"],"Cached reverse email lookup":["/best-cached-reverse-email-lookup-api","Best cached reverse email lookup API in 2026"],"Post search":["/best-linkedin-post-search-api","Best LinkedIn post search API in 2026"],"Post details":["/best-linkedin-post-details-api","Best LinkedIn post details API in 2026"],"Job details":["/best-linkedin-job-details-api","Best LinkedIn job details API in 2026"],"Employee comments":["/best-linkedin-profile-comment-api","Best LinkedIn profile comment API in 2026"],"Employee reactions":["/best-linkedin-profile-reaction-api","Best LinkedIn profile reaction API in 2026"],"Cached company enrichment":["/best-company-enrichment-api","Best company enrichment API in 2026"],"People search":["/best-people-search-api","Best people search API in 2026"],"Cached people search":["/best-cached-people-search-api","Best cached people search API in 2026"],"Cached company discovery":["/best-company-discovery-api","Best company discovery API in 2026"],"Cached job postings":["/best-job-postings-api","Best job postings API in 2026"],"Job posting details":["/best-job-posting-details-api","Best job posting details API in 2026"],"Cached person enrichment":["/best-people-enrichment-api","Best people enrichment API in 2026"]},"first":[{"provider":"Autobound","api":"Cached employee comments","website":"https://www.autobound.ai","pricingPage":"https://www.autobound.ai/pricing","pitch":"High-intent signals from prospect LinkedIn comments. AI-filtered for signal quality with pain point extraction, initiative detection, technology mentions, and relationship context across 4M+ monitored contacts.","strengths":[],"aggregators":[],"freshness":"1 month","fieldFreshness":null,"history":null,"keep":"license to access and use the Services solely for Customer’s internal business purposes during the term of this Agreement [...] Customer shall retain a perpetual, non-exclusive license to use, copy, and distribute any Reports generated through the Services prior to the date of termination or expiration, solely for Customer’s internal business purposes","use":"Company hereby grants Customer a non-exclusive, nontransferable, revocable license to access and use the Services solely for Customer’s internal business purposes during the term of this Agreement. [...] Customer shall not, and shall not permit any third party to: Reverse engineer, decompile, disassemble, or otherwise attempt to derive the source code, algorithms, or underlying structure of the Services or any component thereof; Modify, adapt, translate, or create derivative works based upon the Services; Resell, sublicense, lease, rent, loan, distribute, or otherwise make the Services available to any third party, except as expressly authorized in writing by Company; Remove, alter, or obscure any proprietary notices, labels, or markings on or in the Services; Use the Services in a manner that could damage, disable, overburden, or impair Company’s servers, networks, or infrastructure.","plan":"Pro","who":"anyone who signs up; the agreement licenses use for internal business purposes","billing":"one-time","charged":null,"topUp":false,"pay":499,"currency":"USD","exchangeRate":1,"termMonths":null,"from":null,"graduated":null,"units":83167,"unit":"credit","renews":null,"expires":"never","costUnits":2,"calls":41583.5,"monthlyCap":null,"perThousand":12,"waterfall":null,"listPerThousand":null,"overagePerThousand":null,"addons":null,"notFoundPerThousand":null,"catchAllPerThousand":null,"bounceRefund":null,"repeatFree":null,"alsoPaysFor":[],"sharesBudgetWith":["POST /v1/companies/enrich","POST /v1/companies/search","POST /v1/contacts/search","POST /v1/buyer-intent/companies","POST /v1/buyer-intent/contacts","POST /v1/buyer-intent/export"],"startPerCall":null,"startPerCallMax":null,"monthlyFee":null,"monthlyFeePer":null,"extras":[],"per":"result","resultsPerPage":null,"resultsCap":null,"perDay":null,"perSecond":5,"concurrent":null,"batch":1,"answer":"in the call","latencyMs":128,"call":null,"method":"POST","path":"/v1/contacts/enrich","send":"contact_email or contact_linkedin_url, signal_types \"linkedin-comments-contact\"; signal_subtypes, detected_after, limit (1 to 500)","fields":["signal ID","detected at","text","date","comment URL","likes","replies","summary","intent","signal quality","relationship to post author","pain points","initiatives","technologies mentioned","competitors mentioned","commenter name","commenter URL","commenter job title","commenter company","commenter company domain","post URL","post text","post date","post likes","post comments","post summary","post pain points","post initiatives","post technologies mentioned","post competitors mentioned","post author name","post author job title","post author company","commenter work email","commenter first name","commenter last name","commenter seniority","commenter department","commenter company URL","commenter company industries","commenter company employee count minimum","commenter company employee count maximum","commenter company revenue range","commenter company description","post signal ID","post author company description","commenter ID","commenter headline","commenter city","commenter state","commenter country","commenter current job start date","commenter work history","commenter education","commenter skills","commenter emails","commenter email type","commenter email status","commenter email verification date","commenter company ID","commenter company headquarters city","commenter company headquarters state","commenter company headquarters country","commenter company founded year","commenter company employees on LinkedIn","commenter company is B2B","commenter company is B2C","commenter company employee count confidence","commenter company revenue confidence","commenter company industry confidence","commenter company products","commenter company services","commenter company target customer"]},{"provider":"Triguna","api":"Cached employee comments","website":"https://triguna.ai","pricingPage":"https://triguna.ai/pricing","pitch":"One page of a person's recent LinkedIn activity: their posts and reposts, or the posts they commented on or reacted to.","strengths":[],"aggregators":[],"freshness":"24 hours","fieldFreshness":null,"history":null,"keep":"no limit","use":"You agree not to use the API to: build a general-purpose people-search product or resell records as a database; enable unlawful discrimination, harassment, or surveillance of individuals; present retrieved values to third parties as verified facts about a person; or circumvent rate limits or the absence of a bulk endpoint.","plan":"Pay as you go","who":"anyone","billing":"one-time","charged":null,"topUp":true,"pay":null,"currency":"USD","exchangeRate":1,"termMonths":null,"from":null,"graduated":null,"units":null,"unit":"credit","renews":null,"expires":null,"costUnits":1,"calls":null,"monthlyCap":null,"perThousand":0.1667,"waterfall":null,"listPerThousand":null,"overagePerThousand":null,"addons":null,"notFoundPerThousand":5,"catchAllPerThousand":null,"bounceRefund":null,"repeatFree":"never","alsoPaysFor":[],"sharesBudgetWith":["GET /v1/people/profile","GET /v1/companies/details","POST /v1/people/bulk","GET /v1/people/experiences","GET /v1/people/social-metrics","GET /v1/posts/details","GET /v1/posts/comments","GET /v1/posts/reactions","GET /v1/posts/search"],"startPerCall":null,"startPerCallMax":null,"monthlyFee":null,"monthlyFeePer":null,"extras":[],"per":"page","resultsPerPage":30,"resultsCap":null,"perDay":null,"perSecond":10,"concurrent":null,"batch":1,"answer":"in the call","latencyMs":null,"call":null,"method":"GET","path":"/v1/activities/personal-feed","send":"entity_urn, activity_type: comments; count, pagination_token, use_cache","fields":["text","post URL","post text","post author name","post author URL","post author headline","post ID","post date","post reactions","post comments","post reposts","post reactions by type","post media","post reshared post","post author ID","post author type","post author picture","post author username","next cursor","has more"]}],"total":14,"freshness":["Live","Within an hour","Within a day","Within a week","Within a month","Within a year","Stored, age unknown"],"providers":[{"label":"Autobound","value":"Autobound on its own site"},{"label":"Triguna","value":"Triguna on its own site"}],"at":[4,11],"fields":{"Cached employee comments":["post author name","post comments","post date","post text","post URL","text","comment URL","commenter city","commenter company","commenter company description","commenter company domain","commenter company employee count confidence","commenter company employee count maximum","commenter company employee count minimum","commenter company employees on LinkedIn","commenter company founded year","commenter company headquarters city","commenter company headquarters country","commenter company headquarters state","commenter company ID","commenter company industries","commenter company industry confidence","commenter company is B2B","commenter company is B2C","commenter company products","commenter company revenue confidence","commenter company revenue range","commenter company services","commenter company target customer","commenter company URL","commenter country","commenter current job start date","commenter department","commenter education","commenter email status","commenter email type","commenter email verification date","commenter emails","commenter first name","commenter headline","commenter ID","commenter job title","commenter last name","commenter name","commenter seniority","commenter skills","commenter state","commenter URL","commenter work email","commenter work history","competitors mentioned","date","detected at","has more","initiatives","intent","likes","next cursor","pain points","post author company","post author company description","post author headline","post author ID","post author job title","post author picture","post author type","post author URL","post author username","post competitors mentioned","post ID","post initiatives","post likes","post media","post pain points","post reactions","post reactions by type","post reposts","post reshared post","post signal ID","post summary","post technologies mentioned","relationship to post author","replies","signal ID","signal quality","summary","technologies mentioned"]},"same":["api","perMonth","strengths","aggregators","waterfall","resultsCap","startPerCall","monthlyFee","extras","overagePerThousand","addons","catchAllPerThousand","bounceRefund","history","perDay","concurrent","batch","answer"],"facets":["defaults","provider","price","fields","billing","who","freshness"],"ties":{"Cached employee comments":{"tied":[],"movedPages":{},"canonicals":{"Autobound":"free","Triguna":"free"}}},"shared":[],"notes":{"name":"The row's name, unique on the sheet: the provider, then the plan's price, like \"API Builderz, $50 monthly\", \"HarvestAPI, $280 pack\", \"Crawlbase, pay as you go\", \"Bright Data, top-up\" (a prepaid balance of any amount), \"AnyAPI, top-up from $10\" (a balance you top up by $10 or more), \"free\" or \"contact us\". If two plans share a price, we add the plan's name, then the call's method and path, its units and the call's name, until no two rows share a name. We build the name for the sheet and leave it out of the sheet's CSV and JSON. datacircle.json and datacircle.csv have the name from its API's sheet.","api":"This column names each row's API. \"Employee profile\" returns a person's LinkedIn profile, on LinkedIn profiles. \"Cached employee profile\" returns it from the provider's copy of LinkedIn, on Cached LinkedIn profiles, which lists the LinkedIn profile plans whose Freshness says a copy. \"Employee email\" finds a person's work email, on Find email. \"Cached employee email\", on the Find cached email sheet, finds a person's work email in the provider's stored data. \"Email validation\" checks whether an address takes mail, on Validate email. On the Cached email validation sheet, \"Cached email validation\" may answer from data the provider keeps, without asking the mail server. \"Employee phone\" finds a person's phone number, on Find phone. \"Cached employee phone\", on the Find cached phone sheet, finds a person's phone number in the provider's stored data. \"Company profile\" returns a company's LinkedIn page, on LinkedIn company profiles. \"Cached company profile\", on the Cached LinkedIn company profiles sheet, returns a company's LinkedIn page from the provider's copy of LinkedIn. \"Company headcount\" counts a company's staff, on its own sheet. \"Cached company headcount\", on the Cached company headcount sheet, counts a company's staff from the provider's stored data. \"Phone validation\" checks whether a phone number is valid, on Validate phone. \"Cached phone validation\", on the Cached phone validation sheet, checks a phone number against data the provider has stored. \"Post comments\" returns the comments on a LinkedIn post, on LinkedIn post comments. \"Post reactions\" returns who reacted to a LinkedIn post and how, on LinkedIn post reactions. \"Employee lookalikes\" returns people similar to the one you send, on Similar people. On the Cached similar people sheet, \"Cached employee lookalikes\" returns similar people from a copy the provider keeps. On the Similar companies sheet, \"Company lookalikes\" returns companies similar to the company you send. On the Cached similar companies sheet, \"Cached company lookalikes\" returns similar companies from a copy the provider keeps. \"Company technologies\" returns the tools a company uses, on its own sheet. \"Cached company technologies\" returns the tools a company uses, from a copy the provider saved earlier. \"Company job count\" counts the jobs a company has open on LinkedIn, on its own sheet. \"Employee posts\" returns a person's LinkedIn posts, on LinkedIn person posts. \"Company posts\" returns a company's LinkedIn posts, on LinkedIn company posts. \"Cached employee posts\" and \"Cached company posts\", on Cached LinkedIn person posts and Cached LinkedIn company posts, return them from the provider's copy of LinkedIn. \"Company funding\" returns a company's funding rounds, on its own sheet. \"Cached company funding\", on the Cached company funding sheet, returns them from the provider's stored data. \"Company jobs\" returns the jobs a company has open, on Company open jobs. On the Cached company open jobs sheet, \"Cached company jobs\" returns a company's open jobs from a copy the provider keeps. \"Employee search\" finds people by job title, company and place, on LinkedIn people search. \"Cached employee search\", on the Cached LinkedIn people search sheet, finds people in the provider's copy of LinkedIn. \"Company search\" finds companies by industry, size and place, on LinkedIn company search. \"Cached company search\" finds companies by industry, size and place in the provider's copy of LinkedIn. It is on the Cached LinkedIn company search sheet. \"Job search\" finds jobs by title, company and place, on LinkedIn job search. \"Cached job search\" finds jobs by title, company and place in a copy of LinkedIn's jobs. It is on the Cached LinkedIn job search sheet. \"Reverse email lookup\" finds the person behind an email, on its own sheet. \"Cached reverse email lookup\" finds who owns an email address in data the provider already holds. It is on the Cached reverse email lookup sheet. \"Post search\" finds posts by keyword, on LinkedIn post search. \"Cached post search\" finds posts by keyword in a copy of LinkedIn posts. It is on the Cached LinkedIn post search sheet. \"Post details\" returns a post from its URL or ID, on LinkedIn post details. \"Job details\" returns a job from its URL or ID, on LinkedIn job details. \"Employee comments\" returns the comments a person left on posts, on LinkedIn person comments. On the Cached LinkedIn person comments sheet, \"Cached employee comments\" returns a person's comments from a copy the provider keeps. \"Employee reactions\" returns the posts a person reacted to, on LinkedIn person reactions. \"Post reposts\" returns the people who reposted a LinkedIn post, on LinkedIn post reposts. \"Employee recommendations\" returns the recommendations on a person's LinkedIn profile, on LinkedIn person recommendations. \"Job lookalikes\" returns jobs similar to the one you send, on Similar jobs. \"Employee articles\" returns a person's LinkedIn articles, on LinkedIn person articles. \"Company enrichment\" returns a company's profile from the provider's own database, on Company enrichment. \"Cached company enrichment\", on the Cached company enrichment sheet, returns a company's profile from the provider's stored data. \"People search\" finds people in the provider's own database. \"Cached people search\", on the Cached people search sheet, finds people in the provider's stored data. \"Company discovery\" finds companies in the provider's own database. \"Cached company discovery\", on the Cached company discovery sheet, finds companies in the provider's stored data. \"Job postings\" finds job postings in the provider's own database. \"Cached job postings\", on the Cached job postings sheet, finds job postings in a copy the provider keeps. \"Job posting details\" returns a job posting from its ID. On the Cached job posting details sheet, \"Cached job posting details\" returns a job posting from a copy the provider keeps. \"Person enrichment\" returns a person's profile. On the Cached person enrichment sheet, \"Cached person enrichment\" returns a person's profile from a copy the provider keeps. \"Leadership changes\" returns the new hires, promotions and departures in a company's senior roles. \"Cached leadership changes\" returns a company's leadership changes from a copy the provider keeps. \"Company hierarchy\" returns a company's parent companies and subsidiaries. Pick an API from the GTM APIs list on the left of the sheet. Pick \"All GTM APIs\" in the GTM APIs list to see every API in one sheet. We name each folder in the zip after its API.","score":"We score each plan out of 100 on five parts: price, data, cost to get started, bundled calls and performance. We score data and performance from our benchmark of the provider's call. Until we benchmark the call, the plan's data, performance and Overall scores are N/A. A plan whose data score is 0 has an Overall score of 0, whatever its other scores. Each API's sheet shows what we measured on each benchmarked plan, in the columns after its price. We rank a plan's price per 1,000 against the price per 1,000 of its API's other scored plans. We score cost to get started and bundled calls on the plan alone. We give N/A to yearly and contact us plans, plans over $500 to start, plans bought on a marketplace and plans that need your own LinkedIn account. A free plan gets N/A unless it has no limit and the provider has no paid plan for that call. Then we score it. Click Score in the sheet's bar to set the five weights. The JSON, datacircle.json and datacircle.csv give each plan's score at the default weights. A plan with N/A has an empty score there. The sheet's CSV has no scores.","Price score":"The plan's price score out of 100. We rank the plan's $ per 1,000 against the $ per 1,000 of the other scored plans of its API. We also count the cost of a call that finds nothing. Some plans give no $ per 1,000. For those plans, when each call returns one result, we use the price our benchmark paid per call. We scale that price by what a credit costs on the plan. We skip our benchmark's price for a plan if another paid plan for the same call lists its own $ per 1,000. Plans for one call can each charge a different price per call. On the sheet, hover over or tap the score to see how we worked it out.","Data score":"The plan's data score out of 100, from our benchmark of its provider's call: how complete the call's answer is, or how often it is right, depending on the API. Until we benchmark the call, the score is N/A, and so is the Overall score. On the sheet, point at the score to see how we scored it. Each API's sheet shows what we measured on each benchmarked plan, in the columns after its price.","Cost to get started score":"The plan's score out of 100 for getting your first result: who can get it, how you pay, and the least you pay before it. On the sheet, point at the score to see why.","Bundle score":"The plan's score out of 100 for the other calls its price gets you, as its pages list them under Also pays for. On the sheet, point at the score to see why.","Performance score":"The plan's performance score out of 100, from our benchmark of its provider's call. We divide the fastest benchmarked provider's median time by this provider's median time. A median under 0.1 s counts as 0.1 s, since the baseline we take off varies by about that much. The Performance score and the Overall score are N/A until we benchmark the call. If the call gave no answer we could time, the Performance score is N/A and the Overall score counts it as 0. The Performance score is N/A if we timed no other call in the same benchmark. The Overall score then leaves Performance out. On the sheet, point at the score to see how we scored it. Each API's sheet shows what we measured on each benchmarked plan, in the columns after its price.","perThousand":"The price of 1,000 comments on this plan, in dollars. It is 0 on a free plan. On a plan that charges by the page, we divide 1,000 by the most comments one page holds. We round that up to whole pages and add up what the pages cost. We leave it blank when the provider doesn't say how many comments a page holds. On a flat fee, we take the most comments the plan allows in one month and multiply by the number of months the fee covers. We divide the fee by that total. Then we multiply by 1,000. We leave it blank when the provider doesn't say how many comments the plan allows. On a flat fee with no cap on comments, the sheet shows \"no limit\", and the CSV and JSON leave it blank. On a waterfall's paid plan, we show the average cost of a call. We take the price of each provider listed under Waterfall. We weight each price by how often a call reaches that provider. We leave it blank when the waterfall doesn't list a hit rate or a page size for a provider a call can reach. On a plan with a Monthly fee, we first subtract one month of the fee from the plan's units. Then we divide the plan's price by the number of comments the remaining units buy. Then we multiply by 1,000. We leave it blank when the Monthly fee uses up all the plan's units. Some plans limit calls per day or per month. If that limit allows fewer comments than the units pay for, we divide the plan's price by the comments the limit allows, and multiply by 1,000. We leave it blank on a top-up, because a top-up buys no fixed number of comments. We also leave it blank when the provider's website doesn't say what a comment costs on this plan, or how many comments the plan's price buys.","billing":"How you pay: \"free\", \"on-demand\" (you pay for what you use, with nothing to buy first), \"one-time\" (a pack or a top-up you pay for first, then use), \"contact\" (no public price: you ask the provider for one), or a subscription: \"monthly\", \"quarterly\" (every three months), \"half-yearly\" (every six months) or \"yearly\". The sheet shows \"one-time\" as \"pay first\" and \"on-demand\" as \"pay as you go\".","perMonth":"On a subscription: its price for one month in dollars, its Pay divided by the months it buys (termMonths), 12 on most yearly plans. We work it out for the sheet, to the cent. We leave it out of the sheet's CSV and JSON, and datacircle.json and datacircle.csv have it. Blank (null) on every other plan.","notFoundPerThousand":"Dollars for 1,000 profiles the provider can't find. 0 when the provider charges nothing for them, as on free plans. On a waterfall, the cost of a call when no provider finds the answer: the sum of the prices of the providers that charge for a miss.","strengths":"The plan's strengths, which we work out from its row: each one is a band that many plans of its API are in. Each API has its own strengths, listed and explained under Strengths on datacircle.dev/fields, and Validate email, Find phone, Validate phone, LinkedIn company profiles, Company headcount, LinkedIn post comments, LinkedIn post reactions, Similar people, Similar companies, Company technologies, Company job count, LinkedIn person posts, LinkedIn company posts, Company funding, Company open jobs, LinkedIn people search, LinkedIn company search, LinkedIn job search, Reverse email lookup, LinkedIn post search, LinkedIn post details, LinkedIn job details, LinkedIn person comments, LinkedIn person reactions, LinkedIn post reposts, LinkedIn person recommendations, Similar jobs, LinkedIn person articles, Company enrichment, People search, Company discovery, Job postings, Job posting details, Person enrichment, Leadership changes and Company hierarchy have none yet. Cached LinkedIn profiles and Find cached email have the strengths of LinkedIn profiles and Find email, but never \"read live\" or \"found live\". The other cached sheets have none yet. Blank ([] in the JSON) when the plan has none, and we leave Strengths off its page. Under Filters, you see only the rows with every strength you tick.","aggregators":"Aggregators like treg and Deepline sell the row's call. With one aggregator account, you reach many providers. Each cell says what a call costs through the aggregator with your own provider key. It also says what 1,000 comments cost when you pay the aggregator and have no account at the provider: \"treg: your key free, paid $1.50\". We add \"per 1,000 results\" when the aggregator charges per comment it finds, and say \"paid, no fixed price\" when the aggregator publishes no price. For an aggregator that charges by the page, we take the largest page size and price the full pages you need for 1,000 results. We write \"paid, page size not stated\" when the aggregator doesn't say how many results a page holds. We write \"listed, how it's sold not stated\" when the aggregator lists the call but doesn't say if you pay the aggregator or use your own key. When the aggregator sells one of the provider's calls without saying which, the cell ends with \"this call or another\", the provider's name and \"call\": \"this call or another Pubrio call\". A cell says \"none\" when no aggregator we checked for the row's API sells the call. A blank cell (null in the JSON) means we haven't checked any aggregator for that API. We skip calls an aggregator doesn't list. In the JSON, each aggregator has these keys. aggregator is its name. url is its page for the call. ownKey is what a call costs there with your own key, or null when you can't use yours. paid is true when you can pay the aggregator. paid and ownKey are both null when the aggregator doesn't say how it sells the call. callStated is false when the aggregator sells this call or another of the provider's and doesn't say which. usd is its price in dollars for one per, or null when it sets no price. perThousand is its price in dollars for 1,000. per is \"call\", \"result\" or \"page\". resultsPerPage is the most results a page holds, or null. So far we have read AnyAPI, Clay, ColdIQ, Databar, Deepline, Monid, Orthogonal, RouterGrowth and treg.","waterfall":"Some routers, like treg's, try one provider after another until one finds the comment. On a router's call, the Waterfall column lists each provider the router tries, in order. Each provider shows the router's name for its call in brackets. Then comes its price per 1,000 on this plan, then how often it finds the comment. We add \"misses billed\" when the provider charges for a miss. For a provider that charges by the page, we count the full pages that hold 1,000 results at the largest page size, and we write \"page size not stated\" when the provider doesn't say how many results a page holds. The router publishes how often each provider finds a comment over all its calls. We assume each provider finds comments at that same rate on the calls the earlier providers miss. We leave the Waterfall column blank on calls with a single provider. In the JSON, each step has these keys. provider is the provider's name. call is the provider's call, which you can also make on its own. perThousand, per and resultsPerPage mean the same as on a plan's row. hitRate is from 0 to 1, or null when the router gives none. missesBilled is true when the provider charges for a miss.","repeatFree":"On a call that costs units: how long you can get a comment again free on this plan after you pay for it. On a flat fee with a daily or monthly limit: how long you can get a comment again without using up the limit after you first get the comment. We copy it from the provider's pages, like \"20 minutes\". \"no limit\" means the provider never charges again for a comment you paid for once. \"never\" means the provider says it charges each time you get the comment again. Blank when the provider's pages don't say.","per":"The price counts a \"call\" or a \"result\". A call asks for one comment. A result is each comment a call returns. Some calls return a page of results: a post's comments, reactions or reposts, a person's or company's posts, a person's articles, comments or reactions, a company's open jobs, the people, companies, jobs or posts a search finds, or people, companies or jobs similar to the one you send. \"result\" counts each comment on the page. \"page of 50\" counts each page, and you pay for a whole page even when it holds fewer than 50. resultsPerPage is the most comments a page holds. It is null when the price doesn't count pages or the provider doesn't say the page size. \"page, size not stated\" means the provider doesn't say how many comments a page holds.","resultsCap":"For a search API, the most results you can get from one search on this plan, however many pages you ask for. \"no limit\" when the provider says you can get every match. Blank (null in the JSON) when the provider's docs don't say, or when the API isn't a search.","startPerCall":"A fee in dollars you pay once for each call, on top of the price per comment, like an Apify Actor's start fee. You pay the same fee for a call of 1,000 comments or a call of one comment. We leave this fee out of the $ per 1,000. It is $0.00 on a free plan. It is blank when the plan has no start fee. Some providers' pages give a range, like \"2-3 credits\". When the page gives a range, startPerCall is the lowest fee and startPerCallMax is the highest. The sheet and the CSV show \"$0.04 to $0.06\". startPerCallMax is blank on a plan with one start fee or none.","monthlyFee":"A monthly fee the call needs. The provider takes it from the plan's units. For example, RouterGrowth charges $9.625 a month for each LinkedIn account you connect. monthlyFee is the fee in dollars. monthlyFeePer is what one fee pays for, like \"LinkedIn account\". The Enough for and $ per 1,000 columns count what is left after one month of the fee. Blank (null in the JSON) when the call has no monthly fee.","extras":"Fields that cost more. Each has its fields and its perThousand on top of the row's.","Also pays for":"The other calls you get for the plan's price. Each has its own limit. We use the provider's words. When a plan pays for more than 40 other calls, we write their count instead, like \"300 other calls\". We leave out apps, extensions, MCP servers, proxies and storage, since they are not calls. We also leave out features you can use only in the provider's app, like sending its email campaigns. For example, gtm-api.com's account price also buys 100 searches, 50 messages and 25 connection requests a day. \"nothing\" when you get only the row's call. The row's $ per 1,000 is for that call alone, since providers don't say how to split their price. Blank (null in the JSON) until we read the provider's plan. Also blank on a \"contact\" plan whose pages don't say what its price buys.","overagePerThousand":"On a subscription: dollars for each 1,000 comments you get past the plan's units, when the provider sells extra comments.","addons":"On an email API's subscription: the packs of units the provider sells on top of the plan, as its pricing page lists them. Each has its units, its pay in the plan's currency, when it renews (\"month\" or \"year\" when you pay for it again with the plan, \"never\" when you buy it once), and its perThousand, dollars for 1,000 emails at its price. The sheet's CSV says \"500 credits a month for $10 ($20.00 per 1,000)\". An empty list when the provider sells none. Blank (null) on every other plan.","catchAllPerThousand":"On an email API: dollars for 1,000 calls that return an address at a catch-all domain. Such a domain takes mail for any address, so you can't check whether the person's mailbox exists, and the email may bounce. 0 when they cost nothing, or when the provider returns no such address. The same as the row's $ per 1,000 when the provider charges for any address it finds. Blank when its pages don't say.","bounceRefund":"On an email API: the credit or refund the provider gives when an address it charged you for bounces, and the conditions, in its pages' words, like \"the credit, reported from the dashboard or the API and reviewed\". \"never\" when its pages say a bounced address stays charged. Blank when they don't say.","pitch":"How the provider sells the row's call, quoted from the call's own page, or the provider's own pitch when one page covers all its calls. \"[...]\" marks a cut.","freshness":"How old the answer may be, from the provider's pages. \"live\": the provider reads LinkedIn, the company's website or its job board, or finds or checks the email or phone number, when you call. A plan is \"live\" too when the provider keeps each answer for an hour or less and gives it again to anyone who asks the same question in that time. Renidly keeps each answer for 20 minutes. \"1 month\" or \"30 days\": the provider answers from a copy it refreshes that often. \"as of 2025-11-13\": from a copy last refreshed that day. \"stored\": from a copy the provider's pages don't date. We also mark an email or phone check \"stored\" when it reads only the format, the domain's DNS and the provider's own lists. That check never asks the mail server or the carrier. We leave it blank (null in the JSON) when the provider's pages don't say how fresh the answer is, or don't agree with each other. The cached sheets are Cached LinkedIn profiles, Find cached email, Cached LinkedIn company profiles, Cached company headcount, Cached company enrichment, Cached people search, Cached company discovery, Cached company funding, Cached email validation, Cached LinkedIn people search, Find cached phone, Cached reverse email lookup, Cached LinkedIn job search, Cached LinkedIn company search, Cached LinkedIn post search, Cached company technologies, Cached phone validation, Cached LinkedIn person posts, Cached LinkedIn company posts, Cached job postings, Cached leadership changes, Cached person enrichment, Cached similar people, Cached similar companies, Cached company open jobs, Cached LinkedIn person comments and Cached job posting details. We put a plan on its API's cached sheet when the plan's Freshness says the provider answers from a copy. We put every other plan on its API's own sheet. In brackets, we list the fields whose freshness differs on the provider's pages. fieldFreshness gives each of them its own freshness. Bright Data's LinkedIn profile is \"live (current title, jobs, schools: as of 2025-11-13)\", since LinkedIn put those three behind its login wall and Bright Data serves them from its cache.","history":"How far back the answers reach, on an API whose answers are dated, such as a company's funding rounds or its open jobs. \"since 2016\": back to 2016. \"open only\": only what is open now. \"the last 7 days\": a window that ends today. \"no limit\": every one ever. \", closed only\" after it: the closed ones alone. Blank (null in the JSON) when the provider's pages don't say, or when the answers aren't dated.","keep":"How long the provider's terms let you keep its API's answers. \"no limit\" when they set none. \"no API terms\" when the provider has no API terms.","use":"What the provider's terms let you use its API's answers for, and what they ask in return, like a link back or a credit. \"any\" when they limit nothing and ask nothing. \"no API terms\" when the provider has no API terms.","pay":"The plan's price, in its currency. On a subscription, the price covers the months in termMonths. In the sheet's CSV, we write the months after the price: \"$39.00/month\", \"€99.00/month\" on a plan in euros, or \"$468.00/15 months\" on gtm-api.com's yearly plan. A pack's Pay is its price. A top-up's Pay is the smallest amount you can top up. On a top-up with no minimum from the provider, Pay is blank (null in the JSON). A free plan's Pay is $0.00. On a usage tier, Pay is what you pay each month for your calls below that tier. Each of those calls costs the price of its own tier. Some tiers have a minimum. If your calls below the tier cost less than the minimum, you pay the minimum. When a usage tier sits on a subscription, you also pay the plan's price. Crawlbase has a tier for the next 10M requests. On that tier, Pay is $583: what you pay each month for your calls below it. On Mailgun's Foundation plan, you pay $95 a month for up to 5,000 validations: the $35 plan plus $60 for the validations. On a pay-as-you-go plan, the sheet's Pay column shows Charged.","units":"What the plan gives for its price, counted in unit. On a usage tier, where the tier starts: \"from the 51st call a month\".","calls":"The number of comments you get for the plan's price, counted in per. A call and a result are each one comment. On a plan that charges by the page, calls and monthlyCap count pages. calls is the number the plan's units pay for: \"100 calls, once\" for a free trial, \"1,250 results a month\" for an allowance. Some plans limit calls per day or per month. On those plans, calls is the most calls the limit allows before the units renew. This counts each call as one comment or one page. A plan with 10,000 requests a month and a limit of 200 calls a day gives you 6,000 calls a month. monthlyCap is for a call that costs 0 units, like a call on a flat fee. monthlyCap is the most comments you get a month, or \"no limit\". On a plan that limits calls per day or per month, monthlyCap is the most calls the limit allows in 30 days: 90,000 for 3,000 calls a day. The Enough for column shows 3,000 calls a day as \"90,000 calls a month\". On a free trial shorter than 30 days, monthlyCap is the most calls the plan allows over the whole trial. The trial gives these calls one time only. A 7-day trial with 1,000 calls a day shows as \"7,000 calls, once\". Enough for shows calls, or monthlyCap when a row has no calls. On a plan with a Monthly fee, calls is the number of calls left after the provider takes one month's fee from the plan's units. We count the calls again each time the provider refills the plan's units. Enough for says \"0 calls left after the monthly fee\" when the fee uses up all the plan's units. Enough for is blank when the provider doesn't say how many comments you get. Enough for is also blank on pay as you go plans, on top-ups, and on subscriptions that charge for each comment on top of the fee. Enough for is also blank when a waterfall's average call costs nothing. calls and monthlyCap are null when Enough for is blank.","expires":"When the units you don't use lapse, in the provider's words: \"never\", \"365 days\", \"at renewal: unused credits do not carry over\". Blank when its pages don't say.","perDay":"The most calls a day.","perSecond":"The most calls a second you can keep up. When the provider counts a limit over a longer window, we divide it: a limit per minute by 60, per 5 minutes by 300, per hour by 3,600. When it sets several, we show the tightest: 25 a second and 40 a minute is 0.67. We round it to two decimals, and a rate under 0.1 to two digits past its zeros: 5 an hour is 0.0014.","concurrent":"The most calls running at once, or \"no limit\". \"n/a\" when the provider sets no cap on calls at once but limits them by the second: its \"Per second\" limits you. Blank (null) when the provider's pages don't say.","batch":"The most profiles one call takes on this plan. 1 when it takes one at a time. \"no limit\" when the provider says a call takes any number. Blank (null) when a call takes a list and the provider's pages don't say how long.","answer":"The way you get the call's answer. \"in the call\" when the call's response holds the answer. \"by polling or webhook\" when the call returns a job. Once the job is done, you get the answer from another call or at your webhook. \"in the call or by polling\" when the call returns the answer if it is ready in time. If it isn't ready, the call returns a job you check later. An Apify Actor returns a job when it runs past 5 minutes. \"in the call or by webhook\" when you choose in your request. \"by polling\" when only another call gets the answer. \"by webhook\" when only a URL you give gets the answer. Blank (null) when the provider's pages don't say.","latencyMs":"The median time a call takes. If we benchmarked the row's call, we show our benchmark's median, as in its API's benchmark columns: each call's time minus the mean time of three free calls to the same provider before it. If that mean is longer than the call, we use the provider's median baseline, capped at the call's time, so no time is below zero. For other rows, it is the time the provider's pages give, or one we measured when we added the row. Blank (null) when we have neither, or when we benchmarked the call and it gave no answer we could time. Milliseconds in the JSON and datacircle.csv, seconds on the sheet and in its CSV.","send":"What you give the call: a profile URL or a person's ID. The call needs the inputs before \"Optional:\". The optional ones come after it, or after a semicolon in the CSV and the JSON.","method":"The call's HTTP method.","path":"We give the path from the provider's docs. When that path fails, we give the path that works. Each plan of a call has the same path. A plan the provider serves at its own address has its own path.","plan":"The plan, as the provider names it on its pricing page.","who":"Who the provider offers the plan to: \"anyone\", or the condition its pages set, like \"anyone with a work email\" or \"on approval of an application\".","readFrom":"The pages we read the row's values from. They are the sheet's last column: click a cell to see each page, or press ⌘C to copy them all."},"billed":{"free":"Free: nothing to pay","on-demand":"Nothing to buy first: you pay as you go","one-time":"You buy credit first, as a pack or any amount you like, then spend it on calls","contact":"No public price: you ask the provider for one","monthly":"A monthly subscription","quarterly":"A quarterly subscription","half-yearly":"A subscription for 6 months","yearly":"A yearly subscription"},"defaults":["No contact us plans","No free plans","$500 or less to start"],"kept":2,"paid":{"ranked":{"Cached employee comments":[0.1667,12,14.9997,18.0015,20]},"bench":{"Cached employee comments|Autobound|/v1/contacts/enrich":{"data":0.0543,"performance":null,"median":128,"measured":128,"fastest":"Autobound","fastestMedian":128,"fastestMeasured":128,"called":20,"inputs":20,"fewer":false,"days":["2026-10-25"],"row":"Autobound","alone":true}}},"alert":false,"bench":{"groups":[{"name":"Time per profile","note":"We called each provider once on the same 20 profiles, on 25 October 2026. Time is each call minus a baseline, so the distance to the provider's servers drops out. Each value is a call's time minus a baseline time we explain below. We count only our first call on each profile, and only when the provider found that profile. Where we called the providers again, side by side on the same profiles, beside ones we added later, each one called there is timed on that run instead, so those are timed on the same day. Any other later call on the same profile isn't timed, since the provider may answer it from its cache. We don't time a call the provider billed as a repeat of one of our earlier searches. The baseline is the mean of three free calls to the same provider just before the call, on the same connection. If that mean is longer than the call, we use the provider's median baseline, capped at the call's time, so no time is below zero. Sometimes a provider's app is slow on every free call, even for a page that doesn't exist. When a provider's app is that slow, we use three pages of its website for its baseline. We read those pages on a later day. If we checked for a provider's answer every few seconds, the time is when we saw the answer. The answer may have come a few seconds earlier. Nothing to time means the provider found none of the profiles we asked for.","columns":[{"name":"Median","kind":"ms","values":{"Autobound":128}},{"name":"10th percentile","kind":"ms","values":{"Autobound":124}},{"name":"90th percentile","kind":"ms","values":{"Autobound":129}},{"name":"Fastest","kind":"ms","values":{"Autobound":123}},{"name":"Slowest","kind":"ms","values":{"Autobound":129}},{"name":"Baseline","kind":"ms","values":{"Autobound":262}}]},{"name":"Profiles","note":"Called: the profiles we called each provider on. Found: those it returned. Parts returned: the fields below that its answer held at least once.","columns":[{"name":"Called","kind":"count","values":{"Autobound":[20,20]}},{"name":"Found","kind":"count","values":{"Autobound":[3,20]}},{"name":"Parts returned","kind":"count","values":{"Autobound":[12,28]}}]},{"name":"Their comments checked","note":"We asked for 10 comments of each person, by their LinkedIn profile, and read each comment returned on its own LinkedIn page. Returned: comments in the answer. Theirs: comments whose page names the person as the author, out of the most any answer held. Not theirs: someone else's comments. Not read: comments LinkedIn shows only to members, like replies, counted neither way.","columns":[{"name":"Returned","kind":"count","values":{"Autobound":[20,200]}},{"name":"Theirs","kind":"count","values":{"Autobound":[20,108]}},{"name":"Not theirs","kind":"count","values":{"Autobound":[0,20]}},{"name":"Not read","kind":"count","values":{"Autobound":[0,20]}}]},{"name":"The profile comments call","note":"This table shows the provider's call for comments, looked up by the person's LinkedIn profile. It also shows what one profile cost on this run.","columns":[{"name":"Call","kind":"text","values":{"Autobound":"POST signals.autobound.ai/v1/contacts/enrich signal_types linkedin-comments-contact, limit 10"}},{"name":"Charged per profile","kind":"text","values":{"Autobound":"$0.02 a comment, $0.01 with none, nothing when not found"}}]},{"name":"The comments","note":"The person's comments where the answer held this field, out of the most comments any answer held it on, person by person. A value that differs from the comment's LinkedIn page doesn't count. Not in the answer means the call has no such field.","columns":[{"name":"Comment URL","kind":"count","values":{"Autobound":[20,108]}},{"name":"Comment ID","kind":"count","values":{"Autobound":null}},{"name":"Activity ID","kind":"count","values":{"Autobound":null}},{"name":"Text","kind":"count","values":{"Autobound":[20,107]}},{"name":"Posted at","kind":"count","values":{"Autobound":[11,108]}},{"name":"Pinned","kind":"count","values":{"Autobound":null}},{"name":"Edited","kind":"count","values":{"Autobound":null}},{"name":"Contribution","kind":"count","values":{"Autobound":null}}]},{"name":"The comments' engagement","note":"The person's comments where the answer held this field, out of the most comments any answer held it on, person by person. A value that differs from the comment's LinkedIn page doesn't count. Not in the answer means the call has no such field.","columns":[{"name":"Reactions","kind":"count","values":{"Autobound":[20,108]}},{"name":"Reactions by type","kind":"count","values":{"Autobound":null}},{"name":"Replies","kind":"count","values":{"Autobound":[20,108]}}]},{"name":"The post commented on","note":"The person's comments where the answer held this field, out of the most comments any answer held it on, person by person. A value that differs from the comment's LinkedIn page doesn't count. Not in the answer means the call has no such field.","columns":[{"name":"Post URL","kind":"count","values":{"Autobound":[12,108]}},{"name":"Post ID","kind":"count","values":{"Autobound":null}},{"name":"Post share URN","kind":"count","values":{"Autobound":null}},{"name":"Post text","kind":"count","values":{"Autobound":[3,108]}},{"name":"Post posted at","kind":"count","values":{"Autobound":[11,108]}},{"name":"Post author's name","kind":"count","values":{"Autobound":[19,108]}},{"name":"Post author's URL","kind":"count","values":{"Autobound":null}},{"name":"Post author's ID","kind":"count","values":{"Autobound":null}},{"name":"Post author's headline","kind":"count","values":{"Autobound":null}},{"name":"Post author's picture","kind":"count","values":{"Autobound":null}},{"name":"Post reactions","kind":"count","values":{"Autobound":[19,108]}},{"name":"Post comments","kind":"count","values":{"Autobound":[20,108]}},{"name":"Post reposts","kind":"count","values":{"Autobound":null}},{"name":"Post reactions by type","kind":"count","values":{"Autobound":null}}]},{"name":"The comments' mentions and the post's media","note":"Items the answer held over the person's comments, out of the most any answer held, person by person. Not in the answer means the call has no such field.","columns":[{"name":"Mentions","kind":"count","values":{"Autobound":null}},{"name":"Post media","kind":"count","values":{"Autobound":null}}]}],"inputs":{"said":"We don't list the 20 profiles we called, as they hold people's data.","keys":[],"rows":[]}},"more":"/assets/sheet-NDnjcZIo.json"}