RReachSocial

SOCIAL DATA FOR SOFTWARE AND AGENTS

One stable contract for the public social web.

Call normalized social profile and content services without coupling your application to an upstream provider. Use a private B2B key or pay per request with x402 on Base Sepolia.

Explore the catalogOpen the agent guide
llms.txtOpenAPIAPI catalog
3available services
17reviewed services
8platforms mapped
1.0normalized schema

COVERAGE

Start with verified services. See what comes next.

Full catalog →

Facebook

1 reviewed service

Instagram

4 reviewed services

LinkedIn

1 reviewed service

News

1 reviewed service

Reddit

1 reviewed service

TikTok

3 reviewed services

X

3 reviewed services

YouTube

3 reviewed services

QUICKSTART

Discover, call, normalize.

  1. 1
    Inspect the live catalog

    Use GET /v1/services. Roadmap entries never appear as executable.

  2. 2
    Send one canonical URL

    Call the synchronous execute route or create a durable asynchronous job.

  3. 3
    Consume schema 1.0

    Receive provider-neutral profiles, content items, feeds, and stories.

agent
GET https://reachsocial.dev/v1/services

POST /v1/services/instagram.profile/execute
Idempotency-Key: lookup-001

{"input":{"url":"https://instagram.com/nasa"}}

WHY REACHSOCIAL

Operationally boring—in a good way.

Provider-neutral

Stable service IDs and normalized response shapes isolate clients from provider-specific payload changes.

Agent-discoverable

OpenAPI, llms.txt, agent.md, and an RFC 9727 API catalog expose the same reviewed service definitions.

Bounded by design

Idempotency, concurrency limits, upstream spend caps, durable jobs, and replay protection constrain costly mistakes.

Media-light

ReachSocial returns source URLs and metadata. It does not download or retain requested social-media bytes.