READ API LIVEBuild on /v1 for search, profiles, timelines, audience graph, and tweet context.READ DOCS
xfetch
About / xfetch.io

Current X/Twitter data and account alerts,
built to be self-serve.

xfetch turns current public X/Twitter data into two products on one account. Fetch normalized reads over REST or hosted MCP, or send every new post from watched accounts to Discord and generic signed webhooks in real time.

Explore the docs →
1,000

Free API credits on sign-in

2

Ways into the data API

6

Hosted MCP read tools

2

Monitor delivery lanes

01
Overview

What xfetch is

Read current public data when your workflow asks, or react when a watched account posts.

DATA

REST + hosted MCP

Build new integrations on normalized /v1 reads, migrate supported official-style code through /2, or give an agent six read-only tools over hosted MCP. All three paths use the same API key and credits.

MONITOR

Every new post, delivered

Watch a public account and send every new post to your team's Discord, your generic signed webhook, or both. Stable event IDs and retries make machine workflows easier to operate.

Explore the API reference, connect an agent over MCP, or see account monitors in action.

02
Product jobs

Two ways to put X/Twitter data to work

Read current public data

  • Search & social listening
  • Profiles, timelines & account intelligence
  • Audience & relationship graph
  • Tweet context & conversation analysis
  • REST and hosted-MCP agent workflows

React to new posts

  • Team-visible Discord cards
  • Generic signed tweet.created webhooks
  • Stable event IDs for deduplication
  • Automatic retries with bounded backoff
  • /v1 context reads after each trigger
03
How we design

Principles

  1. 1

    Design from workflows

    Every endpoint maps to a real customer workflow, not to endpoint parity with the official API.

  2. 2

    Stable, opaque contracts

    Stable public contracts and opaque pagination tokens. No upstream provider names or internal implementation details ever leak.

  3. 3

    Pricing that matches the product

    API reads use visible credits. Account monitors are priced per watched account, and deliveries never spend API credits.

  4. 4

    Self-serve from the first useful action

    Start with 1,000 API credits, or watch one account free for 10 days. Both paths begin with Google sign-in.

04
Get in touch

Contact

Talk to the people building xfetch

Questions, feedback, partnerships, or bug reports — one inbox, read by the team that ships xfetch.

hello@xfetch.io →Prefer to read first? Browse the API reference or see account monitors →

Start with data.
Or start with a monitor.

Get 1,000 API credits, or watch one public account free for 10 days. Both paths begin with Google sign-in.