xbird

xbird — Twitter/X for AI Agents

Agent skills that give AI agents 35 Twitter/X tools — reading, searching, posting, engagement, media upload — across 3 integration protocols.

No Twitter developer account, no API keys, no OAuth.

Skills

Skill	Protocol	Best For
xbird	MCP (stdio)	Claude Code, Cursor, Windsurf — local MCP tools
xbird-rest-api	REST + x402	Backend services, autonomous agents, any HTTP client
xbird-acp	ACP (Virtuals)	Agent-to-agent commerce on Virtuals Protocol marketplace

Which skill to use?

Running in Claude Code / Cursor / Windsurf?
  → xbird (MCP)

Building a backend service or autonomous agent?
  → xbird-rest-api (x402 micropayments, USDC on Base)

Operating on Virtuals Protocol marketplace?
  → xbird-acp (E2E encrypted credentials, ECDH + AES-256-GCM)

Quick Install

Claude Code Plugin

/plugin install checkra1neth/xbird-skill

Agent Skill (works with 35+ agents)

npx skills add checkra1neth/xbird-skill

MCP Server Only

Bun (recommended) — auto-detects browser cookies:

claude mcp add xbird -- bunx @checkra1n/xbird

Node.js — requires one-time login:

claude mcp add xbird -- npx @checkra1n/xbird
npx @checkra1n/xbird login  # paste auth_token + ct0 from x.com DevTools

A payment wallet is generated automatically on first run.

	Bun (bunx)	Node.js (npx)
Browser cookies	Auto-detected	Manual login required
Setup	Install Bun, done	One-time login command
Startup	Faster	Slower (npm registry check)

CLI

# Save Twitter credentials locally
npx @checkra1n/xbird login

How It Works

MCP (Local)

AI Agent (Claude Code / Cursor / Windsurf)
  |  MCP stdio
@checkra1n/xbird (local process)
  |-- Auto-detect Twitter cookies from browser
  |-- Pay x402 --> xbird server (payment only)
  '-- Execute --> Twitter API (your residential IP)

The xbird server only verifies payments. All Twitter API calls happen locally from your machine.

REST API (Stateless)

Your Backend / Agent
  |-- npx @checkra1n/xbird login  -->  generates stateless token locally
  |-- GET /api/search + token     -->  xbird server
  |<-- 402 Payment Required       <--  (challenge)
  |-- x-payment header (signed)   -->  (auto via @x402/fetch)
  |<-- 200 { data, cursor }       <--  (result)

Fully stateless server — no database, no stored credentials. The token is self-contained (xbird_sk_<key>.<ciphertext>.<iv>), decrypted per-request then discarded.

ACP (Virtuals Protocol)

Buyer Agent
  |-- ECDH key exchange  -->  xbird TEE (attestation)
  |-- Encrypted credentials + job  -->  Virtuals relay (claw-api)
  |-- Job lifecycle: REQUEST → NEGOTIATION → TRANSACTION → COMPLETED
  |<-- Deliverable with results

End-to-end encrypted credentials (ECDH P-256 + AES-256-GCM). The Virtuals relay transports only opaque ciphertext.

Pricing

Tier	Price	Examples
Read	$0.001	get_tweet, get_user, get_home_timeline
Search	$0.005	search_tweets, get_mentions
Bulk/Write	$0.01	get_user_tweets, post_tweet, like_tweet
Media	$0.05	upload_media

Comparison with X API

Example agent session — 9 API calls:

Call	xbird	X API
search_tweets	$0.005	$0.100
get_tweet ×3	$0.003	$0.015
get_user	$0.001	$0.010
get_replies	$0.001	$0.100
post_tweet	$0.010	$0.010
like_tweet	$0.010	$0.015
upload_media	$0.050	$0.010
Total	$0.080	$0.260

3.2x cheaper. X API charges per resource fetched — a search returning 20 tweets costs 20x the per-tweet price. xbird charges a flat fee per call.

Security

Protocol	Credential Protection
MCP	Auto-detected from browser, never leave your machine
REST x402	Fully stateless — encrypted in self-contained token, server stores nothing
ACP	ECDH P-256 + AES-256-GCM end-to-end encryption (relay-blind)

Skill Structure