Agent skill
datacircle
Every plan of every GTM API on datacircle.dev, as one file you download and query.
activeReaches the webActs undeclared12,433 words
Filed under Prospecting and list building.
From waynehamadi/datacircle · 1 skill entry · 1 · pushed 2026-11-02
What it does when it runs
Every plan of every GTM API on datacircle.dev, as one file you download and query. The file covers People, Contact, Companies, Signals, Social media, E-commerce, Real estate and Web. For each plan, the file lists the price per 1,000 results, our score for the plan and the rate limits. The file also lists the fields the plan returns and a link to the plan's docs. Use the file to compare or price a GTM API.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- datacircle.dev
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- shell
Ask about datacircle
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Rather ask a human? Talk to Cheetah
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/waynehamadi/datacircle.git /tmp/datacircle git -C /tmp/datacircle sparse-checkout set "skills/datacircle" mkdir -p ~/.claude/skills/datacircle cp -R "/tmp/datacircle/skills/datacircle/." ~/.claude/skills/datacircle/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from waynehamadi/datacircle/blob/ba7769dcfb5b1e1e2ae7678d3de4d7fc220146f0/skills/datacircle/SKILL.md, which is licensed MIT (repository). 12,433 words, 7 headings.
Datacircle
Find the best GTM APIs. We benchmark all the GTM APIs and we put the results on our website. With this skill you get every plan of every GTM API on datacircle.dev as one file.
When to use
Use it to compare or price a GTM API.
1. Download it
curl -fsSL --compressed -o datacircle.json https://datacircle.dev/datacircle.json
Or the same rows and columns as CSV: https://datacircle.dev/datacircle.csv. In the CSV, we write each list or object as JSON.
2. The model
One row is one plan of one call. A provider's plan that covers two calls is two rows. Every row has every key below. Prices are in dollars, except pay, which is in the plan's currency. An item is what a row's API counts, like a profile on LinkedIn profiles or an email on Find email. The table of APIs below gives each API's item.
| Key | Type | Meaning |
|---|---|---|
name | text | The sheet's first column gives each row's name. No two rows on the sheet share a name. The name starts with the provider, then the plan's price. Some names: "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". Two plans with the same price also get the plan's name. We drop any words in the plan's name that the price already gives. If two rows share a name after that, we add the call's method and path to each name. When two names still match, we add the plan's units. When they still match after that, we add the call's name. The sheet's own CSV and JSON files have no name column. datacircle.json and datacircle.csv have a name column with the same names as the sheets. |
provider | text | Who sells the endpoint. On the sheet, the provider's name starts each row's API plan. |
api | text | This column names each row's API. Each API has a sheet in the GTM APIs list. Most sheets share the API's name. For the rest, we give the sheet's name after the API. "Employee profile", on the LinkedIn profiles sheet, returns a person's LinkedIn profile. "Employee email", on the Find email sheet, finds a person's work email. "Email validation", on the Validate email sheet, checks whether an email address takes mail. "Employee phone", on the Find phone sheet, finds a person's phone number. "Company profile", on the LinkedIn company profiles sheet, returns a company's LinkedIn page. "Company headcount" counts a company's staff. "Phone validation", on the Validate phone sheet, checks whether a phone number is valid. "Post comments", on the LinkedIn post comments sheet, returns the comments on a LinkedIn post. "Post reactions", on the LinkedIn post reactions sheet, returns the reactions to a LinkedIn post, each with the person who reacted. "Employee lookalikes", on the Similar people sheet, returns people similar to the person you send. "Company lookalikes", on the Similar companies sheet, returns companies similar to the company you send. "Company technologies" returns the tools a company uses. "Company job count" counts the jobs a company has open on LinkedIn. "Employee posts", on the LinkedIn person posts sheet, returns a person's LinkedIn posts. "Company posts", on the LinkedIn company posts sheet, returns a company's LinkedIn posts. "Company funding" returns a company's funding rounds. "Company jobs", on the Company open jobs sheet, returns the jobs a company has open. "Employee search", on the LinkedIn people search sheet, finds people by job title, company and place. "Company search", on the LinkedIn company search sheet, finds companies by industry, size and place. "Job search", on the LinkedIn job search sheet, finds jobs by title, company and place. "Reverse email lookup" finds the person behind an email address. "Post search", on the LinkedIn post search sheet, finds posts by keyword. "Post details", on the LinkedIn post details sheet, returns a post from the post's URL or ID. "Job details", on the LinkedIn job details sheet, returns a job from the job's URL or ID. "Employee comments", on the LinkedIn person comments sheet, returns the comments a person left on posts. "Employee reactions", on the LinkedIn person reactions sheet, returns the posts a person reacted to. "Post reposts", on the LinkedIn post reposts sheet, returns the people who reposted a LinkedIn post. "Employee recommendations", on the LinkedIn person recommendations sheet, returns the recommendations on a person's LinkedIn profile. "Job lookalikes", on the Similar jobs sheet, returns jobs similar to the job you send. "Employee articles", on the LinkedIn person articles sheet, returns a person's LinkedIn articles. "Company enrichment" returns a company's profile from each seller's own database. "People search" finds people in each seller's own database. "Company discovery" finds companies in each seller's own database. "Job postings" finds job postings in each seller's own database. "Job posting details" returns a job posting from the posting's ID. "Person enrichment" returns a person's profile. "Leadership changes" returns the new hires, promotions and departures in a company's senior roles. "Company hierarchy" returns a company's parent companies and subsidiaries. "Web search" returns the web pages that match a query. "SERP" returns a search engine's results page as data. "News search" returns the news articles that match a query. "Image search" returns the images a search engine finds for a query, in the order the engine ranks them. "Video search" returns the videos a search engine finds for a query, in the order the engine ranks them. "Search autocomplete" returns the searches a search engine suggests as you type a query. "Web scraping" returns a page's content from the page's URL. "Keyword research" returns a keyword's search volume, cost per click and competition. "Ranked keywords" returns the keywords a domain ranks for in Google, with the domain's position and traffic for each keyword. "Related keywords" returns keywords like the keyword you send, with the search volume of each. "Backlinks" returns the links that point to a domain. "Domain authority" returns a domain's authority score and the number of links to the domain. "X profile" returns an X (Twitter) account's profile from the account's handle. "X posts" returns an X account's posts. "Instagram profile" returns an Instagram account's profile. "Instagram posts" returns an Instagram account's posts. "TikTok profile" returns a TikTok account's profile. "TikTok videos" returns a TikTok account's videos. "YouTube channel" returns a YouTube channel's name, subscribers and description. "YouTube channel videos" returns a YouTube channel's videos. "Reddit profile" returns a Reddit account's profile. "Reddit posts" returns a Reddit account's posts. "Facebook page" returns a Facebook page's details from the page's URL. "Facebook posts" returns a Facebook page's posts. "Threads profile" returns a Threads account's profile. "Threads posts" returns a Threads account's posts. "Bluesky profile" returns a Bluesky account's profile. "Bluesky posts" returns a Bluesky account's posts. "Telegram channel" returns a Telegram channel's details. "Telegram channel posts" returns a Telegram channel's posts. "Pinterest search" returns the pins Pinterest finds for a query. "Pinterest pin" returns a Pinterest pin's details. "Pinterest board pins" returns the pins on a Pinterest board. "Pinterest user boards" returns a Pinterest account's boards. "Hacker News search" returns the Hacker News stories for a query. "Hacker News story comments" returns the comments on a Hacker News story. "Twitch profile" returns a Twitch channel's profile. "Twitch videos" returns a Twitch channel's videos. "Twitch clip" returns a Twitch clip's details. "Kick clip" returns a Kick clip's details. "Snapchat profile" returns a Snapchat account's profile. "Truth Social profile" returns a Truth Social account's profile. "Truth Social posts" returns a Truth Social account's posts. "GitHub profile" returns a GitHub account's profile. "GitHub repository" returns a GitHub repository's details. "GitHub user repositories" returns a GitHub account's repositories. "Douyin profile" returns a Douyin account's profile. "Douyin user videos" returns a Douyin account's videos. "Douyin video" returns a Douyin video's details. "Weibo profile" returns a Weibo account's profile. "Weibo user posts" returns a Weibo account's posts. "Weibo post" returns a Weibo post's details. "Xiaohongshu profile" returns a Xiaohongshu (RedNote) account's profile. "Xiaohongshu user notes" returns a Xiaohongshu account's notes. "Xiaohongshu note" returns a Xiaohongshu note's details. "Zhihu profile" returns a Zhihu account's profile. "Zhihu question answers" returns the answers to a Zhihu question. "Kuaishou profile" returns a Kuaishou account's profile. "Kuaishou user videos" returns a Kuaishou account's videos. "Kuaishou video" returns a Kuaishou video's details. "Bilibili profile" returns a Bilibili account's profile. "Bilibili user videos" returns a Bilibili account's videos. "Bilibili video" returns a Bilibili video's details. "Facebook ads" returns a company's ads from Meta's Ad Library. "Google ads" returns a company's ads from Google's Ads Transparency Center. "LinkedIn ads" returns a company's ads from LinkedIn's Ad Library. "TikTok ads" returns a company's TikTok ads. "G2 reviews" returns a software product's reviews on G2. "Capterra reviews" returns a software product's reviews on Capterra. "Trustpilot reviews" returns a company's reviews on Trustpilot. "Glassdoor reviews" returns a company's reviews on Glassdoor, written by people who work or worked there. "App Store app" returns an app's listing on the App Store from the app's App Store ID. "App Store reviews" returns an app's reviews on the App Store. "Google Play app" returns an app's listing on Google Play from the app's package name. "Google Play reviews" returns an app's reviews on Google Play. "Amazon product" returns a product's listing on Amazon from the product's ASIN. "Amazon search" returns the products Amazon finds for a query, in the order Amazon ranks them. "Google Shopping product" returns a product's offers on Google Shopping from the product's Google Shopping ID. "Walmart product" returns the Walmart listing for a Walmart ID. "Walmart search" returns the products Walmart finds for a query, in the order Walmart ranks them. "eBay product" returns the eBay listing for a listing ID. "eBay search" returns the listings eBay finds for a query, in the order eBay ranks them. "TikTok Shop product" returns the listing at a TikTok Shop product link. "TikTok Shop search" returns the products TikTok Shop finds for a query, in the order TikTok Shop ranks them. "Facebook Marketplace listing" returns one listing from the listing's link or ID. "Facebook Marketplace search" returns the listings Facebook Marketplace shows for a search term in a city. "Zillow search" returns the homes Zillow lists in a place, in the order Zillow ranks them. "Zillow property" returns a home's Zillow listing from the home's Zillow URL. "Redfin search" returns the homes Redfin lists in a ZIP code, in the order Redfin ranks them. "Redfin property" returns a home's Redfin listing from the home's Redfin URL. "Realtor.com search" returns the homes Realtor.com lists in a place, in the order Realtor.com ranks them. "Realtor.com property" returns a home's Realtor.com listing from the home's Realtor.com ID. "App Store search" returns the apps the App Store finds for a query, in the order the App Store ranks them. "Google Play search" returns the apps Google Play finds for a query, in the order Google Play ranks them. "ChatGPT answer" returns ChatGPT's answer to a prompt. "Perplexity answer" returns Perplexity's answer to a prompt. "Gemini answer" returns Gemini's answer to a prompt. "Bing Copilot answer" returns Bing Copilot's answer to a prompt. "Business verification" looks a company up by legal name in a state's register and returns the register's record of the company. |
category, subcategory, sheet | text | Where the row's API sits in the GTM APIs list on the sheet's left. category is the API's category, like "Contact". subcategory is the API's subcategory, like "Email". sheet is the sheet that holds the API, like "Find email" for the Employee email API. Blank (null in the JSON) for an API the list doesn't hold yet. Only datacircle.json and datacircle.csv have these keys. |
page | text | The address of the plan's own page on datacircle.dev. Only datacircle.json and datacircle.csv have this key. |
website | text | The provider's website. |
pricingPage | text | The page where you buy the plan: the provider's pricing page, or the plan's page on another site, like RapidAPI. Some providers have no pricing page, like a job board with a free public API. For those, this is the page of API docs for the plan. The button on the plan's page links to this page. |
pitch | text | How the provider sells the row's call, quoted from the call's own page. When one page covers all the provider's calls, we quote the provider's own pitch. "[...]" marks a cut. |
strengths | list | The plan's strengths, which we work out from the plan's row. Each strength is a band that many plans of the same API are in. Strengths differ by API. We list and explain them under Strengths on datacircle.dev/fields. Only LinkedIn profiles and Find email have strengths so far. Blank ([] in the JSON) when the plan has none, and then the plan's page leaves Strengths out. Under Filters, you see only the rows with every strength you tick. |
aggregators | list, or empty | Aggregators like treg and Deepline sell the row's call. With one aggregator account, you reach many providers. Each cell gives what a call costs through the aggregator with your own provider key. The cell also gives what 1,000 items 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 result found. We say "paid, no fixed price" when the aggregator publishes no price. When an aggregator charges by the page, we divide a page's price by the most results one page holds. Then we multiply by 1,000. We write "paid, page size not stated" when the aggregator doesn't say how many results a page holds. Some aggregators list the call but don't say whether you pay them or use your own key. For those, we write "listed, how it's sold not stated". An aggregator may sell one of the provider's calls without saying which. Then 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 the aggregator's name. url is the aggregator's 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 the call is sold. callStated is false when the aggregator doesn't say whether the call is this one or another of the provider's. usd is the aggregator's price in dollars for one per, or null when the aggregator sets no price. perThousand is the aggregator's price in dollars for 1,000. per is "call", "result" or "page". resultsPerPage is the most results a page holds, or null. |
waterfall | list, or empty | Some routers, like treg's, try one provider after another until one finds the answer. On a router's call, the Waterfall column lists each provider the router tries, in order. Each provider shows the router's name for the provider's call in brackets. Then we give the provider's price per 1,000 on this plan and how often the provider finds the answer. We add "misses billed" when the provider charges for a miss. When a provider charges by the page, we divide a page's price by the most results one page holds. Then we multiply by 1,000. 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 an answer over all the router's calls. We assume each provider finds answers 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 alone. 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. |
freshness, fieldFreshness | freshness: text, or empty. fieldFreshness: object, or empty. | How old the answer may be, as the provider's pages say. "live": the provider gets the data at the moment you call. The provider reads sources like LinkedIn, company websites, job boards, search results, keyword data or a page you send. Or the provider finds or checks an email or phone number at the moment you call. Some providers keep each answer for an hour or less. They give the same answer to anyone who asks the same question in that time. We call a plan that keeps answers for an hour or less "live" too. Renidly, for example, keeps each answer for 20 minutes. "1 month" or "30 days": the provider answers from a copy and refreshes the copy as often as the value says. "as of 2025-11-13": from a copy last refreshed that day. "stored": from a copy with no date on the provider's pages. Some email or phone checks never ask the mail server or the carrier. They read only the format, the domain's DNS and the provider's own lists. We mark those checks "stored" too. Freshness is blank (null in the JSON) when the provider's pages don't say how fresh the answer is. Freshness is also blank when the pages don't agree with each other. Plans that answer from a copy are on the same sheet as the plans that read live. When the provider's pages give some fields a different freshness from the rest, we list those fields in brackets. fieldFreshness gives the freshness of each field in brackets. Bright Data's LinkedIn profile is "live (current title, jobs, schools: as of 2025-11-13)". LinkedIn put current title, jobs and schools behind a login wall. Bright Data serves those three fields from a copy. |
history | text, or empty | How far back the answers reach, on an API whose answers are dated. A company's funding rounds and open jobs are dated. "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 a value: the closed ones alone. Blank (null in the JSON) when the provider's pages don't say, or when the answers aren't dated. |
countries | list, or empty | On Validate phone, the countries whose numbers the call checks, like "United States". On Business verification, the countries whose companies the call finds, like "France". We take them from the provider's pages. "Worldwide": the call covers any country. "Worldwide" also means the call covers over 100 countries. Blank (null in the JSON) until we read the countries on the provider's pages. Also blank when the provider's pages don't list the countries. Blank on every other API. |
fullFamilyTree | true/false, or empty | On Company hierarchy, this column says whether one call gives the whole family tree. The whole tree runs from the top parent down each branch. "yes" (true in the JSON): one call gives the whole tree, counting every page of results the call returns. "no" (false): one call gives part of the tree, like the parents or one level of subsidiaries. You call again for each company to get the rest. The column is blank (null in the JSON) until we read the provider's website. The column is also blank when the provider's website doesn't say. Always blank on every other API. |
checks | list, or empty | This column lists the checks each call makes, as the provider's pages describe them. You find this column on the Validate email and Validate phone sheets. On Find email, the column lists the checks a finder makes on an address before giving you the address. A finder that asks the mail server takes longer than a finder that doesn't. On an email, "format": the address is well formed. "mail servers": the domain has servers that take mail. "disposable domains": the call spots a domain on a list of throwaway domains. "role addresses": the call spots a shared address, like sales@. "mailbox": the call checks with the mail server that the mailbox exists. On a number, "numbering plan": the number fits the rules of the number's country. "carrier": the call finds the carrier the number is with today. If the owner moved the number to a new carrier, you see the new carrier. "line in service": the call checks with the network that the line is live. "messaging apps": the call checks with a messaging app, like WhatsApp, that the number has an account there. A call without "mailbox" doesn't check the mailbox. Such a call can pass an address that bounces. The column is blank (null in the JSON) until we read the provider's pages. Also blank when the provider's pages don't say. Always blank on every other API. |
searchesIn | text, or empty | This column says where the call looks for posts. We read where the call looks on the provider's pages. You find this column on the LinkedIn post search sheet. "LinkedIn's search": the call runs LinkedIn's own search. "Google's index": the call searches Google for LinkedIn posts. Google sets how many posts the call can find. New posts show up only after Google indexes them. "a search engine's index": the call searches another search engine for LinkedIn posts. We also mark a call "a search engine's index" when the provider's pages don't name the search engine. "the provider's own database": the call searches a copy of LinkedIn posts the provider keeps. We leave the column blank (null in the JSON) when the provider's pages don't say. We leave the column blank for every other API. |
keep | text | How long the provider's terms let you keep the API's answers. "no limit" when the terms set none. "no API terms" when the provider has no API terms. |
use | text | What the provider's terms let you use the API's answers for. Also what the terms ask in return, like a link back or a credit. "any" when the terms limit nothing and ask nothing. "no API terms" when the provider has no API terms. |
plan | text | The plan's name on the provider's pricing page. |
who | text | Who the provider offers the plan to: "anyone", or the condition the provider's pages set, like "anyone with a work email" or "on approval of an application". |
auth | text, or empty | "none" when the call needs no API key and no account with the provider on this plan. For example: a public job board, or a call you pay for each time from a wallet. Null when the call needs an API key or an account. |
billing | text | How you pay. "free": the plan costs nothing. "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, so you ask the provider for one. 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". |
charged | text, or empty | On a pay-as-you-go plan ("on-demand"), when the provider takes the money. "per call": you pay for each call, from a wallet. AnyAPI, Scrappa and Tomba take USDC by x402 or MPP. "monthly": the provider bills you each month for what you used, like Crawlbase and the RapidAPI plans. "at a threshold": the provider bills you each time you owe a set amount, like API Direct at $10. Blank (null in the JSON) on every other plan. The sheet shows Charged in the Pay column. |
topUp | true/false, or empty | true on a top-up. A top-up is a plan you pay for first ("one-time"). You can top up any amount at or above the provider's minimum. The Pay column shows the minimum. All the money you top up pays for calls. AnyAPI's top-up from $10 works this way. false on a pack with a fixed size. Blank (null in the JSON) on every other plan. The CSV says "yes" on a top-up. |
pay | number, or empty | The plan's price, in the plan's currency. On a subscription, the price covers the months in termMonths. In the sheet's CSV, we write the months after the price. Some examples: "$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 the pack's 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 the tier the call is in. 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 the tier. On Mailgun's Foundation plan, you pay $95 a month for up to 5,000 validations. The $95 is the $35 plan plus $60 for the validations. On a pay-as-you-go plan, the sheet's Pay column shows Charged. |
currency, exchangeRate | currency: text. exchangeRate: number. | currency is the currency of the plan's Pay, as an ISO 4217 code: "USD" for dollars, "EUR" for euros. exchangeRate is the dollars one unit of the currency buys: 1 for dollars. |
termMonths | number, or empty | On a subscription: how many months the plan's Pay buys. 1, 3, 6 or 12 on a monthly, quarterly, half-yearly or yearly plan. Some providers give more months for the same price: gtm-api.com's yearly plans run 15 months for the price of 12. Blank (null) on every other plan. |
perMonth | number, or empty | On a subscription: the plan's price for one month in dollars. We divide the plan's Pay by the months the plan buys (termMonths), 12 on most yearly plans. We work out this price for the sheet, to the cent. The sheet's CSV and JSON leave this price out. datacircle.json and datacircle.csv have this price. Blank (null) on every other plan. |
score | number, or empty | 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. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. A plan whose data score is 0 has an Overall score of 0, whatever the plan's other scores. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price. We rank a plan's price per 1,000 against the other scored plans of the same API. We score cost to get started and bundled calls on the plan alone. We give N/A to yearly plans, contact us plans and plans over $500 to start. We also give N/A to plans bought on a marketplace and plans that need your own LinkedIn or X account. We score a free plan only when the provider has no paid plan for that call. The free plan must never end. Any limit on the plan's calls must reset each day or sooner. Other free plans get N/A. A plan we don't score gets no score for any of the five parts, even when we benchmarked the call. 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 in the JSON, datacircle.json and datacircle.csv. The sheet's CSV has no scores. |
priceScore | number, or empty | 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 the same 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 a $ per 1,000. Plans for one call can each charge a different price per call. On the sheet, click or tap the score to see how we worked out the score. |
dataScore | number, or empty | The plan's data score out of 100, from our benchmark of the provider's call. On some APIs, the score measures how complete the call's answer is. On others, the score measures how often the answer is right. We lower the score when we test the call on fewer inputs than the benchmark has. Until we benchmark the call, the score is N/A, and so is the Overall score. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. On the sheet, click or tap the score to see how we scored the plan. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price. |
bundleScore | number, or empty | The plan's score out of 100 for the other calls the plan's price gets you. Also pays for lists those calls. On the sheet, click or tap the score to see why. |
costToGetStartedScore | number, or empty | The plan's score out of 100 for getting your first result. The score weighs who can get the plan, how you pay, and the least you pay to start. On the sheet, click or tap the score to see why. |
performanceScore | number, or empty | The plan's performance score out of 100, from our benchmark of the provider's call. We divide the fastest benchmarked provider's median time by this provider's median time. We compare live calls with live calls, and calls that answer from a copy with each other. 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. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. If the call gave no answer we could time, the Performance score is N/A. The Overall score then counts Performance as 0. The Performance score is N/A when we timed no other call of the same kind in the same benchmark. The Overall score then leaves Performance out. On the sheet, click or tap the score to see how we scored the plan. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price. |
units | number, or empty | What the plan gives for the price, counted in unit. On a usage tier, where the tier starts: "from the 51st call a month". |
from, graduated | from: number, or empty. graduated: true/false, or empty. | On a usage tier, like Crawlbase's pay as you go, from is the monthly item count where the tier's price starts. from counts calls or results, as per says. graduated is true when this tier's price covers only the items from from up. The items below from then cost the lower tiers' prices. graduated is false when every item of the month costs this tier's price. Both are null on every other plan. |
to | number, or empty | On a usage tier: the last call or result the tier's price covers each renews. to is one less than the next tier's from on the same call. Blank (null) on the last tier and on every other plan. Only datacircle.json and datacircle.csv have this key. |
unit | text | The unit the plan charges by. A "credit" is the provider's own credit. A "request" is one call. A "result" is one item a call returns. "usd" is a prepaid balance in dollars. An "execution hour" is an hour the provider's servers run your job. A "linked account" is a LinkedIn account you connect. A "seat" is one user. A "token" is the provider's count of the text a call reads and writes. Some providers count run time in tokens too. A "prompt" is a question the provider asks AI engines for you, every day or on another schedule. We show the plan's unit. If the plan names none, we show the provider's unit. |
renews | text, or empty | When units come back: "day", "month", "quarter", "half-year", "year", or "never". On a monthly plan whose units come back each day, you pay for 30 days of them. A yearly, half-yearly or quarterly plan has "month" when the units come a month at a time. The plan has "year", "half-year" or "quarter" when you get all the units at once. |
expires | text, or empty | 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 the provider's pages don't say. |
calls, monthlyCap | calls: number, or empty. monthlyCap: text or number, or empty. | The number of items you get for the plan's price, counted in per. On a plan that charges by the page, calls and monthlyCap count pages. calls is the number of items the plan's units pay for: "100 calls, once" for a free trial, "1,250 results a month" for an allowance. On a plan that charges by the call, calls is the plan's units divided by the cost of one call. That cost includes the Start fee. A plan can limit calls per day or per month. Then calls is the most calls the limit allows before the units renew. The limit counts each call as one item. On a plan that charges by the page, the limit counts each call as one page. Say a plan allows 10,000 requests a month and 200 calls a day. You get 6,000 calls a month, because 30 days of 200 calls is 6,000. Some providers count each result toward the limit. A list you send in one call counts one result for each row. When a provider counts results, limitsCountedIn says "result", and calls and monthlyCap count results. A limit of 2,000 results a day allows 60,000 results in a month of 30 days. We fill monthlyCap when a call costs 0 units, like a call on a flat fee. monthlyCap is the most items you get a month, or "no limit". On a plan with a daily or monthly limit, monthlyCap is the most calls in 30 days. 3,000 calls a day make 90,000. The Enough for column shows 3,000 calls a day as "90,000 calls a month". Any plan can limit calls per hour, minute or second. calls and monthlyCap also hold the most calls a limit per hour, minute or second allows. A limit of 50 calls an hour allows 36,000 calls in 30 days. We count a call limit in monthlyCap only when each call returns one item or a fixed-size page. On a free trial shorter than 30 days, monthlyCap is the most calls you get over the whole trial. The trial's calls never renew. 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, the provider first takes one month's fee from the plan's units. calls counts the calls left after the fee. 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 items you get. Enough for is also blank on pay as you go plans and on top-ups. Enough for is blank too on subscriptions that charge for each item 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. |
perThousand | number, or empty | The price of 1,000 items on this plan, in dollars. The price is 0 on a free plan. On a plan that charges by the call, each call asks for one item. We add the Start fee to each item's price. On a plan that charges by the page, we divide a page's price by the most results one page holds. Then we multiply by 1,000. We leave the price blank when the provider doesn't say how many results a page holds. On a search that charges by the page, we price the first page of each search, whatever the page holds. On a flat fee, we take the most items the plan allows in one month. We multiply those items by the months the fee covers. We divide the fee by that total. Then we multiply by 1,000. We leave the price blank when the provider doesn't say how many items the plan allows. A plan with no end date and only limits per second, minute, hour or day has no cap on items. A flat fee with no cap on items shows "no limit" on the sheet. We leave the price blank in the CSV and JSON. 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 the price blank when a provider a call can reach has no hit rate or page size. 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 items the remaining units buy. Then we multiply by 1,000. We leave the price blank when the Monthly fee uses up all the plan's units. Some plans limit calls per second, minute, hour, day or month. We divide the price by the items the limit allows, if that is fewer than the items you pay for. Then we multiply by 1,000. We leave the price blank on a top-up, because a top-up buys no fixed number of items. We also leave the price blank when the provider's website doesn't say what an item costs on this plan. We leave the price blank, too, when the website doesn't say how many items the price buys. |
listPerThousand | number, or empty | For a provider that prices in dollars, like an Apify Actor: dollars for 1,000 items at the provider's list price. Apify sells a year of credit at a discount: on Starter, $204 buys $228 of credit, twelve months at $19. So an Actor's yearly plans cost less per 1,000 than the Actor's list price. On a plan that charges by the call, List $ per 1,000 includes the Start fee. On a discounted plan, click or tap the plan's $ per 1,000 on the sheet to see who gives the discount. The plan's page also names who gives the discount, under the price. listPerThousand is blank (null in the JSON) when the provider prices in credits or calls. The key is also blank when the provider's pages don't say what an item costs. |
overagePerThousand | number, or empty | On a subscription: dollars for each 1,000 items you get past the plan's units, when the provider sells extra items. On a plan that charges by the call, Overage includes the Start fee. |
unitsCap | text, or empty | "hard" means calls stop once the plan's units run out. "soft" means calls go on after the plan's units run out. Those calls cost the Overage price when the provider gives one. Blank (null in the JSON) when the provider's pages don't say. |
addons | list, or empty | On an email API's subscription: the packs of units the provider sells on top of the plan. We read them on the pricing page. Each pack has units and pay, in the plan's currency. renews is "month" or "year" when you pay for the pack again with the plan. renews is "never" when you buy the pack once. perThousand is dollars for 1,000 emails at the pack's 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. |
notFoundPerThousand | number, or empty | What you pay for 1,000 items the provider has no answer for. 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. That cost is the sum of the prices of the providers that charge for a miss. |
catchAllPerThousand | number, or empty | 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 such calls 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 found. Blank when the provider's pages don't say. |
bounceRefund | text, or empty | On an email API: the credit or refund the provider gives when a paid address bounces. Also the conditions, in the provider's words, like "the credit, reported from the dashboard or the API and reviewed". "never" when the provider's pages say a bounced address stays charged. Blank when the pages don't say. |
repeatFree | text, or empty | On a call that costs units: how long you can get a paid item again for free. On a flat fee with a call limit, the time before the same item counts toward the limit again. We copy the time from the provider's pages, like "20 minutes". "no limit" means the provider never charges again for an item you paid for once. "never" means the provider charges each time you get the item again. Blank when the provider's pages don't say. |
monthlyFee, monthlyFeePer | monthlyFee: number, or empty. monthlyFeePer: text, or empty. | A monthly fee the call needs. The provider takes the fee 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. |
startPerCall, startPerCallMax | number, or empty | A fee in dollars you pay once for each call, on top of the price per item. An Apify Actor's start fee is one. You pay the same fee for a call of 1,000 items or a call of one item. On a plan that charges by the call, each call asks for one item. On that plan, the $ per 1,000, List $ per 1,000, Overage and Enough for columns all count the Start fee. On a plan that charges by the result or the page, a call can return any number of results. On those plans, the $ per 1,000, List $ per 1,000, Overage and Enough for columns leave the Start fee out. The Start fee is $0.00 on a free plan, and blank when the plan has no start fee. A provider's page can give a range, like "2-3 credits". startPerCall then holds the lowest fee and startPerCallMax holds 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. |
per, resultsPerPage | per: text, or empty. resultsPerPage: number, or empty. | The price counts a "call" or a "result". A call asks for one item. A result is each item a call returns. Some calls return a page of results. "result" means you pay for each result on the page. "page of 50" means you pay for each page of up to 50 results. You pay for a whole page even when the page holds fewer than 50. In the JSON, resultsPerPage is the most results a page holds. resultsPerPage is null when the price isn't per page or the provider doesn't say the page size. "page, size not stated" means the provider doesn't say how many results a page holds. On a search, a call is one search, and a "page of 10" holds up to 10 results. The price is for the first page of each search. Each further page costs the same as the first page. |
costUnits | number, or empty | The plan's units one call costs, counted in unit. 1 for a call at one credit. 0 for a free call, like a call on a flat fee. On a plan that charges by the result or the page, the units one result or page costs, as per says. Null when the provider doesn't list the cost. |
resultsCap | number or text, or empty | For a search API: the most results one search gets 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. On a plan that charges by the page, you pay for each page you ask for. |
extras | list | Fields that cost more than the row's price. Each group of extra fields has fields and perThousand. perThousand is the price you pay on top of the row's price. Some providers charge for each search and also for the extra fields on each result. For those providers, perThousand is the price for 1,000 searches. We assume each search returns the most results the plan allows. |
alsoPaysFor | list, or empty | The other calls you get for the plan's price. The other calls each have a separate 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 the provider's 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 the price buys. |
sharesBudgetWith | list, or empty | The other calls that spend the same credits or limit as this row's call, like gtm-api.com's company and post reads. When more than 40 other calls spend the same credits or limit, we write their count instead, like "300 other calls". We leave out apps and MCP servers, which are not calls. We work out the row's $ per 1,000 as if you make none of these calls. "nothing" when no other call shares the budget. On the sheet, the Also pays for column lists these calls last, after the words "from the same budget". Blank (null in the JSON) until we check which calls share the budget. Also blank when the provider's pages don't say. |
perDay, limitsCountedIn | perDay: number, or empty. limitsCountedIn: text. | The most calls a day. Some providers count each result of a call instead, like each row of a list. limitsCountedIn says what the provider counts: "call", "result" or "page". The provider counts the same unit for this column and for the plan's monthly limit. limitsCountedIn says "call" when the provider's docs don't say. |
perSecond | number, or empty | The most calls a second you can keep up. When the provider counts a limit over a longer window, we divide the limit. We divide a limit per minute by 60, per 5 minutes by 300, per hour by 3,600. When the provider sets several limits, we show the tightest: 25 a second and 40 a minute is 0.67. We round to two decimals. A rate under 0.1 keeps two digits past the zeros: 5 an hour is 0.0014. |
concurrent | number or text, or empty | The most calls running at once, or "no limit". "n/a" when the provider sets no cap on calls at once but limits calls by the second. Then Per second sets your limit. Blank (null) when the provider's pages don't say. |
batch | number or text, or empty | The most items you send in one call on this plan. 1 when the call 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 many. A call that refuses fewer than a set number shows the fewest and the most, like "2,000 to 2,000,000". A call that needs at least 2,000 and has no top limit shows "2,000 or more". A call that needs at least 2,000 shows "at least 2,000" when the provider's pages don't give the top limit. |
minBatch | number, or empty | The fewest items you send in one call on this plan, when the provider refuses fewer. The Batch column shows this number first, like "2,000 to 2,000,000". Null when the provider sets no lowest number. |
answer | text, or empty | 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 the answer is ready in time. If the answer isn't ready, the call returns a job you check later. An Apify Actor returns a job when the run goes 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 | number, or empty | The median time a call takes. For a benchmarked call, we show our benchmark's median. The API's benchmark columns show the same median. From each call's time, we subtract the mean time of three free calls to the same provider, made just before. If that mean is longer than the call, we use the provider's median baseline instead. We cap the baseline at the call's time, so no time is below zero. For a call we didn't benchmark, we show the time from the provider's pages. Or we show a time we measured when we added the row. On a plan without a check or feature of the benchmarked plan, we show the provider's time or our own. We leave the median blank (null) when we have no time. We also leave the median blank when the benchmarked call gave no answer we could time. The JSON and datacircle.csv give the time in milliseconds. The sheet and the sheet's CSV give the time in seconds. |
fields | list | The fields the answer can hold at the row's price, each when the provider has the value. We count the answer that holds the result, a not-found included. We leave out a field that only an error holds. Errors include no credits left, a bad input, a timeout and a rate limit. We also leave out a failed row of a bulk answer. An answer with no result yet, still verifying or queued, is left out too. We count each field once. A list counts once, and so does each field in the list. So jobs, job title and job company are three fields. We count this way for every provider. Under Filters, Must return keeps the rows whose answer can hold every field you tick, at the row's price. |
completeness | number | The share of the API's key fields the answer holds, out of 100, as the plan's page shows the share. The share counts the key fields you pay an extra field for. Key fields, below, lists them. Only datacircle.json and datacircle.csv have this key. |
keyFields | list | The key fields of the row's API that the answer holds at the row's price. The plan's page names them too, like "Experience" or "Skills". A key field the answer holds in part, like only the top skills, is in the list too. Only datacircle.json and datacircle.csv have this key. |
extraKeyFields | list | The key fields of the row's API you get only when you pay for an extra field (extras). Only datacircle.json and datacircle.csv have this key. |
send | text | You send an input like a URL, an email or a keyword. You must send every input listed before "Optional:". In the CSV and JSON downloads, the inputs after a semicolon are optional. |
call | text, or empty | The call's name in the provider's docs, when the provider sells more than one call for the API. LinkFinder AI's lead_full_name_to_email and linkedin_profile_to_email are two such calls, both POST /. Blank (null in the JSON) when the provider sells one. |
method | text | The call's HTTP method. |
path | text | 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 a separate address has a separate path. |
docs | text | The provider's page for the call. |
readFrom | list | 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. |
checked | text | The day we last read every value on those pages, California time. |
Each API below, with its api value, its item and its sheet:
api | Item | category › subcategory › sheet |
|---|---|---|
| Employee profile | profile | People › Profiles › LinkedIn profiles |
| Person enrichment | person | People › Profiles › Person enrichment |
| Employee lookalikes | person | People › Profiles › Similar people |
| Employee recommendations | profile | People › Profiles › LinkedIn person recommendations |
| Employee search | person | People › Search › LinkedIn people search |
| People search | person | People › Search › People search |
| Employee email | Contact › Email › Find email | |
| Email validation | Contact › Email › Validate email | |
| Reverse email lookup | person | Contact › Email › Reverse email lookup |
| Employee phone | phone | Contact › Phone › Find phone |
| Phone validation | phone | Contact › Phone › Validate phone |
| Company profile | company | Companies › Profiles › LinkedIn company profiles |
| Company enrichment | company | Companies › Profiles › Company enrichment |
| Business verification | company | Companies › Profiles › Business verification |
| Company technologies | company | Companies › Profiles › Company technologies |
| Company hierarchy | company | Companies › Profiles › Company hierarchy |
| Company search | company | Companies › Search › LinkedIn company search |
| Company discovery | company | Companies › Search › Company discovery |
| Company lookalikes | company | Companies › Search › Similar companies |
| G2 reviews | review | Companies › Reviews › G2 reviews |
| Capterra reviews | review | Companies › Reviews › Capterra reviews |
| Trustpilot reviews | review | Companies › Reviews › Trustpilot reviews |
| Glassdoor reviews | review | Companies › Reviews › Glassdoor reviews |
| Job search | job | Signals › Hiring › LinkedIn job search |
| Job postings | job | Signals › Hiring › Job postings |
| Job details | job | Signals › Hiring › LinkedIn job details |
| Job posting details | job | Signals › Hiring › Job posting details |
| Job lookalikes | job | Signals › Hiring › Similar jobs |
| Company jobs | job | Signals › Hiring › Company open jobs |
| Company job count | company | Signals › Hiring › Company job count |
| Leadership changes | change | Signals › Hiring › Leadership changes |
| Post search | post | Signals › Engagement › LinkedIn post search |
| Post details | post | Signals › Engagement › LinkedIn post details |
| Employee posts | post | Signals › Engagement › LinkedIn person posts |
| Employee articles | article | Signals › Engagement › LinkedIn person articles |
| Company posts | post | Signals › Engagement › LinkedIn company posts |
| Post comments | comment | Signals › Engagement › LinkedIn post comments |
| Post reactions | reaction | Signals › Engagement › LinkedIn post reactions |
| Post reposts | repost | Signals › Engagement › LinkedIn post reposts |
| Employee comments | comment | Signals › Engagement › LinkedIn person comments |
| Employee reactions | reaction | Signals › Engagement › LinkedIn person reactions |
| Facebook ads | ad | Signals › Ads › Facebook ads |
| Google ads | ad | Signals › Ads › Google ads |
| LinkedIn ads | ad | Signals › Ads › LinkedIn ads |
| TikTok ads | ad | Signals › Ads › TikTok ads |
| Company headcount | company | Signals › Growth › Company headcount |
| Company funding | company | Signals › Growth › Company funding |
| X profile | profile | Social media › Profiles › X profiles |
| Instagram profile | profile | Social media › Profiles › Instagram profiles |
| TikTok profile | profile | Social media › Profiles › TikTok profiles |
| YouTube channel | channel | Social media › Profiles › YouTube channels |
| Reddit profile | profile | Social media › Profiles › Reddit profiles |
| Facebook page | page | Social media › Profiles › Facebook pages |
| Threads profile | profile | Social media › Profiles › Threads profiles |
| Bluesky profile | profile | Social media › Profiles › Bluesky profiles |
| Telegram channel | channel | Social media › Profiles › Telegram channels |
| Twitch profile | profile | Social media › Profiles › Twitch profiles |
| Snapchat profile | profile | Social media › Profiles › Snapchat profiles |
| Truth Social profile | profile | Social media › Profiles › Truth Social profiles |
| GitHub profile | profile | Social media › Profiles › GitHub profiles |
| X posts | post | Social media › Posts › X posts |
| Instagram posts | post | Social media › Posts › Instagram posts |
| TikTok videos | video | Social media › Posts › TikTok videos |
| YouTube channel videos | video | Social media › Posts › YouTube channel videos |
| Reddit posts | post | Social media › Posts › Reddit posts |
| Facebook posts | post | Social media › Posts › Facebook posts |
| Threads posts | post | Social media › Posts › Threads posts |
| Bluesky posts | post | Social media › Posts › Bluesky posts |
| Telegram channel posts | post | Social media › Posts › Telegram channel posts |
| Pinterest pin | pin | Social media › Posts › Pinterest pins |
| Pinterest board pins | pin | Social media › Posts › Pinterest board pins |
| Pinterest user boards | board | Social media › Posts › Pinterest user boards |
| Hacker News story comments | comment | Social media › Posts › Hacker News story comments |
| Twitch videos | video | Social media › Posts › Twitch videos |
| Twitch clip | clip | Social media › Posts › Twitch clips |
| Kick clip | clip | Social media › Posts › Kick clips |
| Truth Social posts | post | Social media › Posts › Truth Social posts |
| Pinterest search | search | Social media › Search › Pinterest search |
| Hacker News search | search | Social media › Search › Hacker News search |
| GitHub repository | repository | Social media › Repositories › GitHub repositories |
| GitHub user repositories | repository | Social media › Repositories › GitHub user repositories |
| Douyin profile | profile | Social media › China › Douyin profiles |
| Douyin user videos | video | Social media › China › Douyin user videos |
| Douyin video | video | Social media › China › Douyin videos |
| Weibo profile | profile | Social media › China › Weibo profiles |
| Weibo user posts | post | Social media › China › Weibo user posts |
| Weibo post | post | Social media › China › Weibo posts |
| Xiaohongshu profile | profile | Social media › China › Xiaohongshu profiles |
| Xiaohongshu user notes | note | Social media › China › Xiaohongshu user notes |
| Xiaohongshu note | note | Social media › China › Xiaohongshu notes |
| Zhihu profile | profile | Social media › China › Zhihu profiles |
| Zhihu question answers | answer | Social media › China › Zhihu question answers |
| Kuaishou profile | profile | Social media › China › Kuaishou profiles |
| Kuaishou user videos | video | Social media › China › Kuaishou user videos |
| Kuaishou video | video | Social media › China › Kuaishou videos |
| Bilibili profile | profile | Social media › China › Bilibili profiles |
| Bilibili user videos | video | Social media › China › Bilibili user videos |
| Bilibili video | video | Social media › China › Bilibili videos |
| Amazon product | product | E-commerce › Products › Amazon products |
| Google Shopping product | product | E-commerce › Products › Google Shopping products |
| Walmart product | product | E-commerce › Products › Walmart products |
| eBay product | product | E-commerce › Products › eBay products |
| Facebook Marketplace listing | listing | E-commerce › Products › Facebook Marketplace listings |
| TikTok Shop product | product | E-commerce › Products › TikTok Shop products |
| Amazon search | search | E-commerce › Search › Amazon search |
| Walmart search | search | E-commerce › Search › Walmart search |
| eBay search | search | E-commerce › Search › eBay search |
| Facebook Marketplace search | search | E-commerce › Search › Facebook Marketplace search |
| TikTok Shop search | search | E-commerce › Search › TikTok Shop search |
| App Store app | app | E-commerce › App stores › App Store apps |
| App Store reviews | review | E-commerce › App stores › App Store reviews |
| App Store search | search | E-commerce › App stores › App Store search |
| Google Play app | app | E-commerce › App stores › Google Play apps |
| Google Play reviews | review | E-commerce › App stores › Google Play reviews |
| Google Play search | search | E-commerce › App stores › Google Play search |
| Zillow property | property | Real estate › Properties › Zillow properties |
| Redfin property | property | Real estate › Properties › Redfin properties |
| Realtor.com property | property | Real estate › Properties › Realtor.com properties |
| Zillow search | search | Real estate › Search › Zillow search |
| Redfin search | search | Real estate › Search › Redfin search |
| Realtor.com search | search | Real estate › Search › Realtor.com search |
| Web search | search | Web › Search › Web search |
| SERP | search | Web › Search › SERP |
| Search autocomplete | query | Web › Search › Search autocomplete |
| News search | search | Web › Search › News search |
| Image search | search | Web › Search › Image search |
| Video search | search | Web › Search › Video search |
| Web scraping | page | Web › Scraping › Web scraping |
| ChatGPT answer | answer | Web › Scraping › ChatGPT answers |
| Perplexity answer | answer | Web › Scraping › Perplexity answers |
| Gemini answer | answer | Web › Scraping › Gemini answers |
| Bing Copilot answer | answer | Web › Scraping › Bing Copilot answers |
| Keyword research | keyword | Web › SEO › Keyword research |
| Ranked keywords | keyword | Web › SEO › Ranked keywords |
| Related keywords | keyword | Web › SEO › Related keywords |
| Backlinks | backlink | Web › SEO › Backlinks |
| Domain authority | domain | Web › SEO › Domain authority |
3. Query it
DuckDB reads the JSON and the CSV as they are, with no setup:
duckdb -c "SELECT provider, plan, billing, pay, currency, perThousand, score, page FROM 'datacircle.json' WHERE api = 'Employee email' AND billing != 'free' AND pay * exchangeRate <= 50 AND perThousand IS NOT NULL ORDER BY perThousand LIMIT 10"
The best scored plans of an API, with each part of the score:
SELECT provider, plan, call, score, priceScore, dataScore, costToGetStartedScore, bundleScore, performanceScore, page
FROM 'datacircle.json' WHERE api = 'Employee profile' AND score IS NOT NULL ORDER BY score DESC LIMIT 10;
Every plan of one provider:
SELECT api, plan, billing, pay, perThousand, page FROM 'datacircle.json' WHERE provider ILIKE '%fetchin%' ORDER BY api, perThousand;
The cheapest paid plan per 1,000 of each API:
SELECT api, arg_min(provider || ', ' || plan, perThousand) AS plan, min(perThousand) AS perThousand
FROM 'datacircle.json' WHERE billing != 'free' AND perThousand IS NOT NULL GROUP BY api ORDER BY api;
Without DuckDB, with jq:
jq '[.[] | select(.api == "Employee email" and .billing != "free" and .pay != null and .pay * .exchangeRate <= 50 and .perThousand != null)] | sort_by(.perThousand) | .[:10] | map({provider, plan, pay, currency, perThousand, score, page})' datacircle.json
Or Python:
import json
rows = json.load(open("datacircle.json"))
found = sorted(
(r for r in rows if r["api"] == "Employee email" and r["billing"] != "free" and r["pay"] is not None and r["pay"] * r["exchangeRate"] <= 50 and r["perThousand"] is not None),
key=lambda r: r["perThousand"],
)[:10]
for r in found:
print(r["provider"], r["plan"], r["pay"], r["currency"], r["perThousand"], r["score"], r["page"])
Each row's page is its plan's page on datacircle.dev, and docs the provider's own page for the call. Give your user those links with what you found. Every key is also explained at https://datacircle.dev/fields, and the docs are at https://datacircle.dev/docs.
Limitations
- Empty (
nullin the JSON) means the provider's pages don't say, or don't agree with each other. It also means the key doesn't apply to the row. - We update the file each time we update the site, so download it again when your copy is more than a day old.
Best GTM APIs
- Best LinkedIn API in 2026
- Best phone API in 2026
- Best email API in 2026
- Best X (Twitter) API in 2026
- Best Instagram API in 2026
- Best Reddit API in 2026
- Best Threads API in 2026
- Best LinkedIn profile API in 2026
- Best email finder API in 2026
- Most accurate email finder API in 2026
- Best email verification API in 2026
- Most accurate email verification API in 2026
- Best phone finder API in 2026
- Most accurate phone finder API in 2026
- Best LinkedIn company data API in 2026
- Best company headcount API in 2026
- Most accurate company headcount API in 2026
- Best phone validation API in 2026
- Most accurate phone validation API in 2026
- Best LinkedIn post comment API in 2026
- Best LinkedIn post reaction API in 2026
- Best similar people API in 2026
- Best similar companies API in 2026
- Best tech stack API in 2026
- Best LinkedIn profile post API in 2026
- Best LinkedIn company post API in 2026
- Best company funding API in 2026
- Best company open jobs API in 2026
- Best LinkedIn people search API in 2026
- Best LinkedIn company search API in 2026
- Best LinkedIn job search API in 2026
- Best reverse email lookup API in 2026
- Most accurate reverse email lookup API in 2026
- Best LinkedIn post search API in 2026
- Best LinkedIn post details API in 2026
- Best LinkedIn job details API in 2026
- Best LinkedIn profile comment API in 2026
- Best LinkedIn profile reaction API in 2026
- Best LinkedIn post repost API in 2026
- Best company enrichment API in 2026
- Best people search API in 2026
- Best company discovery API in 2026
- Best job postings API in 2026
- Best job posting details API in 2026
- Best people enrichment API in 2026
- Best leadership change API in 2026
- Best company hierarchy API in 2026
- Best web search API in 2026
- Best SERP API in 2026
- Best search autocomplete API in 2026
- Best news API in 2026
- Best image search API in 2026
- Best video search API in 2026
- Best web scraping API in 2026
- Best keyword research API in 2026
- Best ranked keywords API in 2026
- Best related keywords API in 2026
- Best backlink API in 2026
- Best domain authority API in 2026
- Best X (Twitter) profile API in 2026
- Best X (Twitter) post API in 2026
- Best Instagram profile API in 2026
- Best Instagram post API in 2026
- Best TikTok profile API in 2026
- Best TikTok video API in 2026
- Best YouTube channel API in 2026
- Best YouTube channel video API in 2026
- Best Reddit profile API in 2026
- Best Reddit post API in 2026
- Best Facebook page API in 2026
- Best Facebook post API in 2026
- Best Threads profile API in 2026
- Best Threads post API in 2026
- Best Bluesky profile API in 2026
- Best Bluesky post API in 2026
- Best Pinterest search API in 2026
- Best Pinterest pin API in 2026
- Best Hacker News comment API in 2026
- Best Twitch profile API in 2026
- Best Twitch video API in 2026
- Best Twitch clip API in 2026
- Best Snapchat profile API in 2026
- Best Truth Social post API in 2026
- Best GitHub profile API in 2026
- Best GitHub repository API in 2026
- Best GitHub user repository API in 2026
- Best Facebook Ad Library API in 2026
- Best G2 review API in 2026
- Best Capterra review API in 2026
- Best Trustpilot review API in 2026
- Best Glassdoor review API in 2026
- Best App Store review API in 2026
- Best Google Play API in 2026
- Best Amazon product API in 2026
- Best Amazon search API in 2026
- Best eBay product API in 2026
- Best TikTok Shop product API in 2026
- Best Facebook Marketplace search API in 2026
- Best Zillow search API in 2026
- Best Realtor.com search API in 2026
- Best Realtor.com property API in 2026
- Best ChatGPT scraper API in 2026
- Best Gemini scraper API in 2026
- Best business verification API in 2026
Need help setting it up?
This page tells you what datacircle does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.