Coming soonWe are adding Reddit endpoints and more updates.Request an endpoint
All use cases

Watch your accounts, your competitors, and the comments under both.

Daily sweeps from cache, live reads when something is going on, and a clear answer when a post disappears.

100 free requests, no card needed.

Today · 5 accounts watched · comments and repliesMentions
2 alertsReview
Tracked termsyourbrandyourbrand refundrivalco+ add term
  • @s.okaforreply to @yourbrand14:03is this the official yourbrand account? got a DM from a lookalikePossible impersonatorLive
  • @mvdbergcomment on @yourbrand · reel13:51yourbrand refund still pending after 9 days, anyone else?Refund mentions · 12 todayLive
  • @lin.uxcomment on @rivalco · video11:20switched from yourbrand to rivalco, half the priceCache · 24h
  • @rivalcopost · DL9ka02pQ1x10:14post mentioning rivalco launch was removedPost deleted · 404Cache · 24h
  • @jbrandtcomment on @yourbrand · reel06:02love the new yourbrand drop, ordered twoCache · 24h
Only comments that mention a tracked term. Routine sweeps from cache, live reads while an alert is open.next sweep 2026-09-03T06:00:00Z

For teams like Stalkr, Brand24, Sprout Social, Agorapulse, and Later.

The problem

Why teams use Openhandle.

Basic scraperWatchlist · competitor post · Tuesday 14:03
CheckResultCodeAlert
14:00 · post2,411 likes200None
14:01 · comments38 new200Spike
14:03 · posterror500None

The post was deleted at 14:02. The scraper returned a generic error, your pipeline retried for an hour, and the takedown went unnoticed.

OpenhandleWatchlist · competitor post · Tuesday 14:03
CheckResultCodeAlert
14:00 · post2,411 likes200None
14:01 · comments38 new200Spike
14:03 · postnot found404Deleted

Same post, same minute. A definitive not-found code turns the deletion into an alert you can act on.

Comment streams with authorsPaginated comments and replies with normalized author profiles. Impersonators and repeat complainers become a query.
Same pipeline for every accountYour accounts, competitor accounts, partner accounts. One schema, one job, one integration.
Cache by default, live when it mattersSweep from the 24-hour cache. Flip the same call to live for the hours an incident is running.
Deletion is an answerA deleted post returns a definitive not-found code, not a mystery error. Disappearance becomes an event you can alert on.

How it works

How a monitoring job works.

  1. 01

    Sweep daily from cache

    Profiles and the comments under recent posts, yours and theirs, once a day from the 24-hour cache.

  2. 02

    Alert on what changed

    New comments, new posts, a spike, or a post that returned not-found. Each one is a normal response you can match on.

  3. 03

    Go live during an incident

    Switch the same calls to live for the hours it matters, then back to cache when it is over.

Live read during an incident
curl "https://api.openhandle.dev/v1/instagram/posts/DAbCdEfGhIj/comments?freshness=live" \
  -H "Authorization: Bearer $OPENHANDLE_API_KEY"
200 OK
{
  "platform": "instagram",
  "resource": "comments",
  "capturedAt": "2026-09-02T14:03:52Z",
  "source": "live",
  "data": [
    {
      "id": "18021499870",
      "text": "is this the official account? got a DM from a lookalike",
      "author": { "handle": "s.okafor", "isVerified": false,  },
      "metrics": { "likes": 12, "replies": 3 }
    },

  ],
  "nextCursor": "eyJvZmZzZXQiOjIwfQ"
}

Read live, right now. The next cursor is opaque and each page is one request, so you read exactly the pages you need.

Trust

Know what changed and when.

Proper invoicing

Card payment, an invoice for every charge. Nothing prepaid, nothing that expires.

A person answers

Chat directly with the people who build Openhandle through Crisp.

Documentation

Read how it works.

Send your agent ahead.

Paste the prompt into your agent and it sets everything up. Or come yourself, it takes five minutes.

For agents