Three platforms that answer, and the ones that do not

What is on the roster

Each platform was probed from production before it shipped. If the public API answered our datacenter address with no credentials, it is here; if it did not, it is not, and the reason is published rather than quietly omitted.

One envelope across all three

Every successful call returns the same outer shape: success, platform, endpoint, request_id, cached and data. List responses put the rows in items with a next_cursor you pass back to page forward. Post-like items carry the same keys on every platform, so code written against Bluesky posts reads Mastodon and Hacker News items without a second branch.

Refusals use the same machine-readable codes as the proxy. A platform that will not answer us is upstream_unavailable with a 502 — our upstream, not your mistake, and the correct response is a retry with backoff.

What is excluded, and why

Reddit is not covered. Its JSON endpoints answer 403 to cloud addresses, which is the same reputation wall that made us withdraw search results, and no amount of rotation among datacenter addresses gets past a rule about datacenter addresses.

X, Instagram, TikTok, LinkedIn and Facebook are not covered either. Their data sits behind credentials, contracts or both. We are not going to build a credential-scraping layer and call it an API, so if your monitoring project needs X or Reddit, this product does not do the job and you should know that on the first page you read rather than the first week you build.

GET /v2/social/platforms is the authoritative version of this section. It lists what serves and what is excluded with the reason attached, and unlike this page it cannot go stale.

Mastodon instances are an allowlist on purpose

Mastodon is federated, so the obvious design takes an instance hostname as a parameter. That design turns the endpoint into a request forwarder pointed anywhere on the internet with our address on the outside, which is an SSRF surface we declined to build.

Instead there is a fixed list of five instances. Adding one is a one-line change and a deploy, so if the community you follow lives elsewhere, email support@roamingproxy.com and ask.

Beta, and metered from day one

The social API is in beta and bundled with the proxy plan at no separate price. It is gated the same way the proxy is — an rp_ key with the proxy scope, a verified email, a live subscription — and every successful call writes a usage record even though nothing is charged for it today.

That is deliberate. The meter runs from the beginning so that when the API is priced, there is real history to price against instead of a guess. If it stays free it stays free; you will not find a retroactive charge for the beta period.

Questions

Can I monitor X or Reddit through this?

No. Reddit blocks cloud addresses outright and X requires credentials and a contract. Neither is a roadmap item we can promise, so treat them as absent rather than pending.

What does beta mean for the price?

It is included with the proxy plan and not separately priced today. Calls are metered so that usage history exists before any pricing decision is made, and nothing from the beta period will be billed retroactively.

Can I use a Mastodon instance that is not on your list?

Not by passing a hostname — that is exactly the SSRF surface the allowlist exists to prevent. Email support@roamingproxy.com with the instance and we will tell you whether we can add it.

Is this a scraper?

No. Every platform here is called through its documented public JSON API, without credentials or cookies, with an identifying User-Agent. Anything that needed scraping to work did not make the roster.

Related