Fetch public Instagram profiles, post feeds, Reels and post comments as structured JSON by handle.
Also known as HasData/instagram-mcp, instagram-mcp, @hasdata/instagram-mcp, hasdata-instagram-mcp
- Stars
- 12
- Tools
- 3
- Downloads, 30 days
- 424
- Latest version
- 1.0.8
- Last commit
- Nov 9, 2026
- License
- MIT
What is HasData Instagram MCP?
HasData Instagram fetches public Instagram profiles, post feeds, Reels and post comments as structured JSON by handle. It exposes 3 tools, such as handle, limit, url.
Summary generated from the project's README
About HasData Instagram MCP server
Extracting public Instagram data into structured JSON for analysis is what this remote MCP server enables. It allows developers using clients like Claude, Cursor, Windsurf, or Cline to retrieve information from public profiles, post feeds, Reels, and comments without needing to connect a personal account. Because it is a hosted service, users can connect via a streamable HTTP URL using a HasData API key or use local launchers via npm or PyPI for stdio-based clients.
The server provides specific tools to fetch profile details such as follower counts and biographies, walk through post feeds, and access the Reels tab. It also includes a tool to read comments on specific posts or reels. Users can start with 1,000 free credits every month, which covers approximately 100 Instagram calls. The data returned is highly structured, providing parsed arrays for hashtags and mentions directly within the post objects, making it easy for AI agents to perform research tasks.
What you can do with it
- 1Analyze public profile metricsRetrieve a specific handle's follower count, verification status, and biography details.
- 2Audit recent post contentScan the latest posts from an account to identify frequently used hashtags and mentioned users.
- 3Evaluate video engagementRank recent Reels based on their play counts, likes, and comment totals.
- 4Monitor post discussionsFetch and read all comments left on a specific public post or reel.
Written from the project's README. Every use case is checked against a quote from it.
How to install HasData Instagram MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall HasData Instagram MCP in Claude Code
$ claude mcp add --env 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' instagram-mcp -- npx -y @hasdata/instagram-mcpInstall HasData Instagram MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"instagram-mcp": {
"command": "npx",
"args": [
"-y",
"@hasdata/instagram-mcp"
],
"env": {
"HASDATA_API_KEY": "<YOUR_HASDATA_API_KEY>"
}
}
}
}Install HasData Instagram MCP in VS Code
.vscode/mcp.json
{
"servers": {
"instagram-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hasdata/instagram-mcp"
],
"env": {
"HASDATA_API_KEY": "<YOUR_HASDATA_API_KEY>"
}
}
}
}Install HasData Instagram MCP in VS Code CLI
$ code --add-mcp '{"name":"instagram-mcp","type":"stdio","command":"npx","args":["-y","@hasdata/instagram-mcp"],"env":{"HASDATA_API_KEY":"<YOUR_HASDATA_API_KEY>"}}'Install HasData Instagram MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"instagram-mcp": {
"command": "npx",
"args": [
"-y",
"@hasdata/instagram-mcp"
],
"env": {
"HASDATA_API_KEY": "<YOUR_HASDATA_API_KEY>"
}
}
}
}Install HasData Instagram MCP in Codex
$ codex mcp add instagram-mcp --env 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' --env 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' -- npx -y @hasdata/instagram-mcpInstall HasData Instagram MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.instagram-mcp] command = "npx" args = ["-y", "@hasdata/instagram-mcp"] [mcp_servers.instagram-mcp.env] HASDATA_API_KEY = "<YOUR_HASDATA_API_KEY>"
Install HasData Instagram MCP in Gemini CLI
$ gemini mcp add -s user -e 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' -e 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' instagram-mcp npx -- -y @hasdata/instagram-mcpInstall HasData Instagram MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"instagram-mcp": {
"command": "npx",
"args": [
"-y",
"@hasdata/instagram-mcp"
],
"env": {
"HASDATA_API_KEY": "<YOUR_HASDATA_API_KEY>"
}
}
}
}Needs a key before it starts
Started on 16 Nov 2026 with no keys, it stopped and asked for one, so a client sees no tools until you set the variables above.
HasData Instagram MCP tools 3
Detected from the READMEhandlelimiturl
| handle | — | |
| limit | — | |
| url | — |
Configuration
HASDATA_API_KEYRequiredSecretHasData API key, created at app.hasdata.com. 1,000 free credits every month, no card.
HASDATA_API_KEYRequiredSecretHasData API key, created at app.hasdata.com. 1,000 free credits every month, no card.
| Name | Description | |
|---|---|---|
| HASDATA_API_KEY | HasData API key, created at app.hasdata.com. 1,000 free credits every month, no card. | RequiredSecret |
| HASDATA_API_KEY | HasData API key, created at app.hasdata.com. 1,000 free credits every month, no card. | RequiredSecret |
Automated checks
Ran Nov 11, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubInstagram MCP Server
A hosted Instagram MCP server that gives Claude, Cursor, Windsurf and any other MCP client read-only Instagram tools. Look up a public profile by handle, walk its public post feed and Reels tab, and read the comments on a public post or reel, as structured JSON.
It reads public data about accounts. It does not act as an account. There is nothing to connect and no account of yours involved anywhere in the flow.
1,000 free credits every month, no card required, which is 100 Instagram calls.
https://mcp.hasdata.com/mcp?apis=instagram
Contents
- What you need
- Quick start
- Example prompts
- Tools
- Errors and failure paths
- Pricing, free tier and limits
- Tool selection
- How it compares
- FAQ
- HasData links
- Development
- Contributing
- License
What you need
An MCP client that speaks streamable HTTP with custom headers. A HasData API key from the dashboard, free to create with no card, and the free tier covers 100 calls a month. Nothing else. This is a remote server, so the simplest path is a URL and a header, with no container to run. A stdio-only client can use the @hasdata/instagram-mcp (npm) or hasdata-instagram-mcp (PyPI) launcher instead.
Quick start
| URL | https://mcp.hasdata.com/mcp?apis=instagram |
| Transport | HTTP, streamable |
| Auth header | x-api-key: HASDATA_API_KEY |
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
claude mcp add --transport http instagram "https://mcp.hasdata.com/mcp?apis=instagram" \
--header "x-api-key: HASDATA_API_KEY"
Claude Desktop loads only local (stdio) servers from its config file, so it reaches a remote server through a stdio launcher. The @hasdata/instagram-mcp package is that launcher, and it reads the key from the environment.
claude_desktop_config.json:
{
"mcpServers": {
"instagram": {
"command": "npx",
"args": ["-y", "@hasdata/instagram-mcp"],
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
}
}
}
Python instead of Node? Swap the launcher for the PyPI package, which uvx runs without a manual install:
{
"mcpServers": {
"instagram": {
"command": "uvx",
"args": ["hasdata-instagram-mcp"],
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
}
}
}
A client with OAuth support can instead add the URL as a custom connector and skip the launcher.
.cursor/mcp.json:
{
"mcpServers": {
"instagram": {
"url": "https://mcp.hasdata.com/mcp?apis=instagram",
"headers": { "x-api-key": "HASDATA_API_KEY" }
}
}
}
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"instagram": {
"serverUrl": "https://mcp.hasdata.com/mcp?apis=instagram",
"headers": { "x-api-key": "HASDATA_API_KEY" }
}
}
}
{
"mcpServers": {
"instagram": {
"url": "https://mcp.hasdata.com/mcp?apis=instagram",
"type": "streamableHttp",
"headers": { "x-api-key": "HASDATA_API_KEY" },
"disabled": false
}
}
}
.vscode/mcp.json:
{
"servers": {
"instagram": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=instagram",
"headers": { "x-api-key": "HASDATA_API_KEY" }
}
}
}
~/.gemini/settings.json:
{
"mcpServers": {
"instagram": {
"httpUrl": "https://mcp.hasdata.com/mcp?apis=instagram",
"headers": { "x-api-key": "HASDATA_API_KEY" }
}
}
}
Example prompts
Each of these is one tool call unless the count says otherwise.
Pull the profile for
@nasaand tell me the follower count, whether it is verified, and every link in the bio.
One call, 10 credits. For a public account the profile response already carries the twelve most recent posts, so a follow-up about recent activity needs no second call.
Compare
@nasa,@natgeoand@bbcearthon followers, accounts followed and whether each is verified.
Three calls, 30 credits. One per handle.
Walk the last fifty posts from
@nasaand list every hashtag with how often it appears.
Five calls, 50 credits. Twelve posts arrive per call, and fifty takes five pages.
For the last twelve posts on
@natgeo, list the accounts mentioned in each caption and the type of each post.
One call, 10 credits. Mentions and hashtags arrive parsed out of the caption in the post objects.
Rank the twelve most recent reels on
@natgeoby plays and show likes and comments next to each.
One call, 10 credits. Plays, likes and comments arrive together on every reel.
Two things make these work. Hashtags and mentions arrive as arrays parsed out of the caption, and an agent counts them instead of running a regex over prose. And a profile lookup returns the recent feed in the same response. That is why so many research questions land in a single call.
Tools
| Tool | What it returns |
|---|---|
hasdata_instagram_comments_getInstagramComments |
Fetches the comments on a public post or reel by its URL and returns the post itself with its caption, media, likesCount, commentsCount and timestamp, then each comment with its text, like count, timestamp and author. 10 credits a call |
hasdata_instagram_posts_getInstagramPosts |
Fetches the latest posts of a public Instagram account by username (handle) and returns each post with its id, shortcode, caption, type, productType, permalink, media URLs and pixel size, like and comment counts, the posting time, plus hashtags, mentions, tagged users and carousel members. 10 credits a call |
hasdata_instagram_profile_getInstagramProfile |
Fetches a public Instagram profile by username (handle) and returns id, full name, biography, bio links, profile picture URL, followers and following counts, the verified flag and the twelve most recent posts. 10 credits a call |
hasdata_instagram_reels_getInstagramReels |
Fetches the Reels tab of a public Instagram account by username (handle), newest first with collab reels included, and returns each reel with play, like and comment counts, caption, hashtags, mentions, cover image, video URL, owner, tagged users and timestamp. 10 credits a call |
All of them are read-only. The comments tool takes the URL of a single post, and the others take a public account handle. Samples below are trimmed from real calls, and the numbers in them move as accounts post. Read them as shapes. A tool name links to its endpoint reference where the docs publish one.
The samples are the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.
Get an Instagram profile
hasdata_instagram_profile_getInstagramProfile
One public profile by handle.
| Parameter | Type | Required | Notes |
|---|---|---|---|
handle |
string | yes | Username without the @, as it appears in the profile URL |
Returns id, username, fullName, biography, verified, the counters followersCount and followsCount, profilePicUrl, the internal fbid, the bioLinks array and latestPosts.
What is guaranteed and what is not, measured across twenty accounts: id, username, followersCount, followsCount, profilePicUrl and fbid came back every time. fullName, biography, verified, bioLinks and latestPosts came back for every public account and are the ones to read with a default.
A private account answers with
private: trueand little else. No bio, no counters beyond the follower numbers, no posts. Branch on that flag before you touch the rest of the payload.
bioLinksis an array of objects, not strings. Each entry carriesurl,title, Instagram's ownredirectUrlwrapper andlinkType. Read.urlwhen you want the destination.
{
"id": "528817151",
"username": "nasa",
"fullName": "NASA",
"biography": "Making the seemingly impossible, possible. ✨",
"verified": true,
"followersCount": 104345698,
"followsCount": 91,
"profilePicUrl": "https://scontent.cdninstagram.com/v/t51.2885-19/…",
"fbid": "17841401474538262",
"bioLinks": [
{
"url": "https://www.nasa.gov",
"title": "NASA.gov Homepage",
"redirectUrl": "https://l.instagram.com/?u=https%3A%2F%2Fwww.nasa.gov%2F&e=…",
"linkType": "external"
}
],
"latestPosts": [ "…the most recent posts, same shape as the posts tool…" ]
}
Get Instagram posts
hasdata_instagram_posts_getInstagramPosts
The public post feed for one handle, page by page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
handle |
string | yes | Username without the @ |
limit |
number | Approximate ceiling on posts in one response. Twelve is the real maximum, and larger values do not fetch more | |
nextPageToken |
string | The pagination.nextPageToken from the previous response |
limitis a rough cap rather than an exact count. Twelve posts is one Instagram page and the hard ceiling for a single call, andlimit: 50returns twelve. Below the ceiling the count lands near the number you asked for without always matching it, and how near depends on the account. Measured on@nasa, a limit of 2 returned 4 posts, 6 returned 6, 11 returned 10 and 13 returned 12. Treat it as "no more than roughly this many" and read the array length rather than assuming it.
The response carries posts and pagination, and nothing else. Earlier versions repeated the account's identity fields alongside the feed, so code written against that shape needs a profile call for the name and avatar.
Each post carries id, shortcode, caption, type, productType, url, ownerUsername, ownerId, displayUrl and images, the pixel size as dimensionsWidth and dimensionsHeight, and hasdataLink, a ready-made link to the comments endpoint for that post. hashtags and mentions appear only when the caption has them. A carousel carries its members in childPosts, and taggedUsers lists the accounts tagged in the media.
Engagement counters arrive with the feed. Each post carries
likesCountandcommentsCount, and the posting time twice:timestampas a full ISO instant andpublishDateas the calendar day. Ranking a feed by popularity or filtering it by date needs no second call. This changed on 2026-10-07; earlier versions of the payload carried none of the four.
{
"posts": [
{
"id": "3983374110243288826",
"shortcode": "DdHyaYAifb6",
"caption": "Cementing their names in history.\n\nThe Artemis III crew is leaving their mark […] @NASAKennedy",
"type": "Carousel",
"productType": "carousel_container",
"mentions": ["@NASAKennedy", "@EuropeanSpaceAgency", "@Astro_Luca"],
"url": "https://www.instagram.com/p/DdHyaYAifb6/",
"hasdataLink": "https://api.hasdata.com/scrape/instagram/comments?url=…",
"commentsCount": 1053,
"likesCount": 121490,
"dimensionsWidth": 1440,
"dimensionsHeight": 1800,
"displayUrl": "https://scontent.cdninstagram.com/v/t51.…",
"images": ["https://scontent.cdninstagram.com/v/t51.…"],
"timestamp": "2026-09-10T21:20:24.000Z",
"publishDate": "2026-09-10",
"ownerUsername": "nasa",
"ownerId": "528817151",
"taggedUsers": [{ "id": "549403870", "username": "nasakennedy", "fullName": "NASA's Kennedy Space Center" }],
"childPosts": [{ "id": "3983374043612570267", "type": "Image", "productType": "carousel_item" }]
}
],
"pagination": {
"morePostsAvailable": true,
"nextPageToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…",
"hasdataLink": "https://api.hasdata.com/scrape/instagram/posts?handle=nasa&nextPageToken=…"
}
}
Hashtags and mentions keep their # and @ prefixes, which matters if you are joining them against a list you built yourself. morePostsAvailable is the flag to branch on when paging, and hasdataLink is the same next page expressed as a REST URL, useful when you want to reproduce an agent's call by hand.
Get an account's reels
hasdata_instagram_reels_getInstagramReels
The Reels tab of one handle, newest first, page by page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
handle |
string | yes | Username without the @ |
limit |
number | Reels in one response, up to 12. Defaults to 12 | |
nextPageToken |
string | The pagination.nextPageToken from the previous response |
The response carries reels and pagination. A reel has the same shape as a post from the feed and adds playsCount and videoUrl, so plays, likes and comments arrive together and ranking an account's reels by reach takes no second call. Each reel carries hasdataLink to its comment thread.
Collab reels are part of the tab. A reel the account co-posted with someone else shows up in its Reels, and
ownerUsernameandownerIdthen name the account that published it, not the handle you asked for. Filter onownerUsernamewhen only the account's own reels count. In a call for@nasaon 2026-11-09, both reels returned were collabs published by other accounts.
{
"reels": [
{
"id": "4026005540840053099",
"shortcode": "DffPrVthplr",
"caption": "Talk about a view! 🪂🇺🇸 Looking down on the historic Shuttle Landing Facility as the Army Golden Knights jump in to kick off Day 2 of MAX POWER! 🚀✈️",
"type": "Video",
"productType": "clips",
"url": "https://www.instagram.com/p/DffPrVthplr/",
"hasdataLink": "https://api.hasdata.com/scrape/instagram/comments?url=…",
"commentsCount": 473,
"likesCount": 30199,
"playsCount": 3468416,
"dimensionsWidth": 1080,
"dimensionsHeight": 1920,
"displayUrl": "https://instagram.fmex31-1.fna.fbcdn.net/v/t51.…",
"images": ["https://instagram.fmex31-1.fna.fbcdn.net/v/t51.…"],
"videoUrl": "https://instagram.fmex36-1.fna.fbcdn.net/o1/v/t2/f2/m86/….mp4",
"timestamp": "2026-11-08T17:02:53.000Z",
"publishDate": "2026-11-08",
"ownerUsername": "airdotshow",
"ownerId": "27179220808",
"taggedUsers": [{ "id": "528817151", "username": "nasa", "fullName": "NASA", "isVerified": true, "profilePicUrl": "https://…" }]
}
],
"pagination": {
"moreReelsAvailable": true,
"nextPageToken": "AQHTZHNas4CpVqvVxNpO1eBpm4iB…",
"hasdataLink": "https://api.hasdata.com/scrape/instagram/reels?handle=nasa&limit=2&nextPageToken=…"
}
}
videoUrl and the image links are signed CDN addresses that expire, so download the file you need soon after the call rather than storing the link. moreReelsAvailable is the flag to branch on when paging.
Get the comments on a post
hasdata_instagram_comments_getInstagramComments
The comment thread under one post or reel, and the post itself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
url |
string | yes | A /p/, /reel/ or /tv/ link, with or without the username segment |
nextPageToken |
string | Token from the previous response | |
includeMusic |
boolean | Also return the sound of a reel in post.music, for licensed tracks and original audio alike |
Use this when the comment thread itself is the point. The post object repeats the engagement figures the feed already carries, so ranking or dating a feed does not need this call, and spending one request per post to collect numbers that arrived with the feed is waste.
Returns post, comments and pagination. A comment carries id, text, timestamp, likesCount and an owner with id, username and profilePicUrl. pagination reports moreCommentsAvailable beside nextPageToken, so a walk can stop without spending a request to discover the end.
{
"post": {
"shortcode": "DdHyaYAifb6",
"type": "Carousel",
"productType": "carousel_container",
"ownerUsername": "nasa",
"timestamp": "2026-09-10T21:20:24.000Z",
"likesCount": 120648,
"commentsCount": 1020
},
"comments": [
{
"id": "18188486875408374",
"text": "I like to become a astronomer",
"timestamp": "2026-10-05T07:38:17.000Z",
"likesCount": 0,
"owner": { "id": "40744210101", "username": "nisha_karippolil" }
}
],
"pagination": { "moreCommentsAvailable": true, "nextPageToken": "…" }
}
Prompts and resources
The server ships one prompt, a ready-made workflow a client can offer instead of making the user compose a tool call.
| Prompt | What it does |
|---|---|
instagram_profile |
Look up a public Instagram profile. |
The list is served without an API key, so a client can read it before a user has signed up.
Errors and failure paths
Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with isError set to true and the reason as text. The agent reads a message where you might expect a status line.
A wrong key surfaces as tool output, not as a failed connection. Listing tools accepts any non-empty key, and the client completes its handshake and shows green. The first tool call then comes back with isError: true and the text HasData API error: 401 Unauthorized. Watch for that string, because nothing earlier in the flow reports the problem.
A missing key is the one real HTTP error. Authorization runs before any tool, and the connection itself fails with 401.
An argument that breaks the schema is rejected before it becomes a request. The server answers with isError: true and the text MCP error -32602: Input validation error, naming the field. Nothing is fetched and nothing is charged.
A handle that does not resolve is a clean error, not empty data. It returns isError: true with HasData API error: 400 Bad Request and requestMetadata.status set to error. This is the good case, because the failure is unambiguous. Test the flag rather than the array length.
An account whose data is not public returns no post feed. The tools cover public accounts, and there is nothing to read on one that is not. Treat a missing latestPosts as out of scope and not as an empty feed.
Results that carry data also carry a requestMetadata.id worth quoting in support, plus html and json links to the stored artifact of that exact call.
Pricing, free tier and limits
Every Instagram tool costs 10 credits per successful call. Response size does not change the price. A profile with twelve posts attached costs the same as one with none.
The free tier is 1,000 credits every month with no card, or 100 Instagram calls. It renews with the billing cycle, so a low-volume agent runs on the free tier indefinitely.
Paid plans start at $59 a month for 200,000 credits, or 20,000 calls. The unit price falls with volume, from $2.95 per 1,000 calls on the entry plan to $1.19 on Basic and $0.83 across the Growth tiers. Current figures live on the pricing page.
Your plan also sets concurrency. The free tier allows 5 requests at a time, Startup 5, Basic 15, and the Growth tiers run from 50 to 500. Handle the overflow case defensively in anything unattended, because an agent that fans out across handles will reach the ceiling before you do.
Paging costs a call each time. A prompt that walks a hundred posts across two accounts is eighteen calls and 180 credits. The free tier goes further on profile comparisons than on deep feed crawls.
Tool selection
?apis=instagram exposes exactly these tools. The parameter takes a list, and ?apis=instagram,tiktok,youtube gives your agent three social platforms at once. Drop the parameter and you get every tool HasData exposes.
A narrow list is usually the better default. A model choosing among a few tools picks correctly more often than one choosing among the whole catalog, and the tool descriptions themselves cost context on every turn.
Cross-platform comparison is the usual reason to widen the list. Ask the same question of an Instagram handle and a TikTok handle and it is one prompt once both are exposed.
HasData Instagram MCP questions
How do I add HasData Instagram MCP to Claude Code?
Run claude mcp add --env 'HASDATA_API_KEY=<YOUR_HASDATA_API_KEY>' instagram-mcp -- npx -y @hasdata/instagram-mcp in your terminal. Add --scope user to make it available in every project.
How do I add HasData Instagram MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does HasData Instagram MCP provide?
It exposes 3 tools, including handle, limit, url.
How do I authenticate to the HasData Instagram MCP server?
Send your HasData API key in an x-api-key header, or use OAuth from a client that supports it. The key is free to create and no account is connected.
Can it read private Instagram accounts?
No. A private account returns a flag with little data, so check that field before reading the rest.
What Instagram data can it return?
It returns public profiles, post feeds, the Reels tab and comments on a public post, including hashtags and mentions parsed from captions.
How many posts come back in one posts call?
Twelve posts is the maximum per call regardless of the limit value, and you page with nextPageToken.
Is there a free tier?
Yes, 1,000 free credits per month without a card, which works out to 100 Instagram calls.