@FuatSezer_795Maker
Solo founder building Captapi, a social media data API and MCP server for developers and AI agents.

Commented on Captapi · Nov 3, 2026
Great question, and yes, that's exactly the distinction we care about. Failures come back as a non-2xx response with a small, stable body: { "code": "NOT_FOUND", "message": "What happened and what to do.", "retryable": false } Some codes: NOT_FOUND, CHANNEL_NOT_FOUND, HASHTAG_NOT_FOUND, TWEET_NOT_PUBLIC, UNSUPPORTED_REGION, RATE_LIMITED, UPSTREAM_TIMEOUT, UPSTREAM_UNAVAILABLE. An agent can just branch on "retryable": - true (429/5xx): a Retry-After header says how long to wait. - false (not found, not public, bad input): retrying won't help, move on. None of these cost credits. Private profiles aren't treated as an error. The profile call returns 200 with "isPrivate": true, so the agent knows not to ask for posts. Some endpoints, like Highlights, return an empty list plus isPrivate and a short note explaining why. Where you're right: a genuinely empty 200, like a search or hashtag with zero results, doesn't yet carry a uniform "why it's empty" field on every endpoint. Today you tell it apart from a failure by the status code and the 0-credit charge in the X-Captapi-Credits header, but not always the reason. A consistent empty-reason field is a good idea, and I'm adding it to the list. Thanks for pushing on this!

Commented on Captapi · Oct 29, 2026
Hey DevHunt 👋 I'm Fuat, the solo founder behind Captapi. I kept rebuilding the same scrapers for TikTok, Instagram and YouTube, and every few weeks one of them broke. Captapi is the API I wanted: one key, consistent JSON, and a hosted MCP server so Claude or Cursor can pull real social data without you writing glue code. A few things I care about: failed or empty requests cost 0 credits, every response header shows what the call cost, and there's a free plan to try it. I'd love feedback on two things: which platform or endpoint you'd want next, and whether the MCP setup was smooth for you.