datacircle — Claude Code skill to compare and price GTM APIs
Downloads one file with every GTM API plan from datacircle.dev and hands it to the agent for pricing and comparison.
MIT ★ 50,109 updated 2026-11-06
/plugin marketplace add sickn33/agentic-awesome-skills
/plugin install agentic-awesome-skills@agentic-awesome-skillsWhat datacircle does
The skill pulls datacircle.json from datacircle.dev with curl, a 60-second timeout and a 104857600-byte size cap. One row is one plan for one call. A provider plan that covers two calls gets two rows.
Every row has the same keys: provider, API name, price in dollars, and a pay field in the plan's currency. Each API counts a different item: a LinkedIn profile for LinkedIn profiles, an email address for Find email. JSON and CSV both work; lists and objects inside the CSV are stored as JSON strings.
The API list is wide: LinkedIn people and company search, profile enrichment, email and phone validation, SERP, web scraping, keyword data, backlinks. The skill works as a reference, not as a client to those endpoints — you still call the APIs yourself after picking one. The file lands in a fresh mktemp -d, so it never mixes with other project data.
What it helps with
- compare GTM API plans from one file
- convert a plan price into the provider's currency
- find out what each API counts as its unit
- pick an API for email, LinkedIn, search or scraping
- keep the repo clean — the file is downloaded on the fly
Example prompts for the agent
- Download
datacircle.jsonand list every API Bright Data sells - Compare Find email prices across three providers
- Find LinkedIn company search APIs in the file and show their plans
How to install datacircle
1Plugin marketplace
/plugin marketplace add sickn33/agentic-awesome-skills/plugin install agentic-awesome-skills@agentic-awesome-skillsThis installs the whole agentic-awesome-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill datacircle -a claude-code3Manually: put the files in place
~/.claude/skills/datacircle/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/datacircle/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill datacircle -a codex2Manually: put the files in place
.agents/skills/datacircle/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill datacircle -a cursor2Manually: put the files in place
.cursor/skills/datacircle/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills plugins/agentic-awesome-skills-claude/skills/datacircle2Manually: put the files in place
.github/skills/datacircle/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill datacircle -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path plugins/agentic-awesome-skills-claude/skills/datacircleManually: put the files in place
.devin/skills/datacircle/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about datacircle
How do I install datacircle in Claude Code?
Via the marketplace: run /plugin marketplace add sickn33/agentic-awesome-skills, then /plugin install agentic-awesome-skills@agentic-awesome-skills. Or use npx skills add sickn33/agentic-awesome-skills --skill datacircle -a claude-code — the skill file lands at ~/.claude/skills/datacircle/SKILL.md.
What does datacircle do?
It downloads one JSON file with all GTM API plans from datacircle.dev and gives it to the agent so you can compare and price APIs.
Is there a CSV version?
Yes, the same rows and columns are available at https://datacircle.dev/datacircle.csv. Lists and objects in the CSV are stored as JSON.
Source text
SKILL.md · MIT
---
name: datacircle
description: "Every plan of every GTM API on datacircle.dev, as one file you download and query. Use the file to compare or price a GTM API."
category: data
risk: critical
source: self
source_type: self
date_added: "2026-10-10"
author: datacircle
tags: [b2b-data, linkedin, enrichment, gtm, api-pricing]
tools: [claude, cursor, gemini]
---
# 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
```bash
DATA_DIR="$(mktemp -d)" || exit 1
curl --fail --silent --show-error --location --compressed \
--proto '=https' --proto-redir '=https' --max-time 60 --max-filesize 104857600 \
--output "$DATA_DIR/datacircle.json" https://datacircle.dev/datacircle.json || exit 1
cd "$DATA_DIR" || exit 1
```
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. After each provider, we give in brackets the name the router uses for that provider's call. Then we give the provider's price per 1,000 on this plan and how often the provider finds the answer. For Validate email and Validate phone, we give how often the provider checks what you send. We count a check whether the provider's verdict is right or wrong. We add "misses billed" when the provider charges for a miss. For a provider 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 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 the published rate. We assume this even on calls where the earlier providers found nothing. We leave the Waterfall column blank on calls with a single provider. In the JSON, each provider in the Waterfall is a step with 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 the keys of the same names on a plan's row. `hitRate` is from 0 to 1, or null when the router publishes no rate. `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, Company enrichment, Company discovery, Company hierarchy, Company headcount and Similar companies, the countries of the companies found. On People search, Person enrichment and Find email, the countries whose people the call finds. 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 pl...
© datacircle · MIT · sickn33/agentic-awesome-skills