AnyPost vs tweet.md: Which X-to-Markdown Tool Fits Your Agent?

If you build agents that read X (Twitter), you have probably seen the domain swap pattern: replace x.com with a converter host and get LLM-ready Markdown instead of HTML embeds. tweet.md and AnyPost both use that trick for X—but they target different scopes. This guide compares them so you pick the right default for your stack.

TL;DR — same trick, different scope

• Both: public X status URL → swap domain → clean Markdown for agents.
• tweet.md: X/Twitter only—posts, threads, profiles, and long-form articles via status URLs.
• AnyPost: same swap for X plus LinkedIn, Reddit, Bluesky, Mastodon, Hacker News, YouTube, Substack, and more under one API key.
• Rule of thumb: stay on tweet.md for X-only pipelines (especially Obsidian export); choose AnyPost when feeds mix platforms or you want one billing account.

For generic any URL → Markdown (docs sites, not social posts), see AnyPost vs Context.dev and Microlink.

The domain swap pattern

Same tweet, two hosts:

Step	tweet.md	AnyPost
Original	https://x.com/NousResearch/status/2060085673848193127	same
Swapped	https://tweet.md/NousResearch/status/2060085673848193127	https://anypost.md/x/NousResearch/status/2060085673848193127

AnyPost adds a platform prefix (/x/) because one domain covers many networks. tweet.md uses a flat path because X is the only source.

Both x.com and twitter.com links work with AnyPost. Open the swapped URL in a browser or fetch it from an agent—the response is Markdown, not a rendered timeline.

Feature comparison

Feature	tweet.md	AnyPost
Platforms	X only	14+ social sources
Domain swap	tweet.md/…	anypost.md/x/…
Thread unroll	?thread=full	?thread=full (+ API key)
Obsidian export	?format=obsidian	Standard Markdown (no Obsidian param)
X profiles	Paid (tweet.md/handle)	Post URLs (no profile parity)
X long-form articles	Via status URL	Pro+ detection, 10 credits
Agent skill	skills.sh tweet skill	anypost-md skill
API	/i/api/convert?url= + Bearer key	/api/convert + swapped URL
Guest free tier	5 posts/IP/month (their docs)	10 posts/day/IP (Starter platforms)

API and agent workflows

tweet.md — paste a key after checkout (twmd_key_… per their docs), then call their convert endpoint or rely on the swapped URL in browser workflows.

curl -s "https://tweet.md/i/api/convert?url=https://x.com/user/status/123" \
  -H "Authorization: Bearer twmd_key_YOUR_KEY"

AnyPost — apk_ keys after credit purchase; domain swap works without a key for basic free-tier posts.

curl -s "https://anypost.md/api/convert?url=https://x.com/user/status/123" \
  -H "Authorization: Bearer apk_YOUR_KEY"

AnyPost also registers WebMCP tools (convert_post, list_supported_platforms) on the preview site for browser-based agents.

One skill for mixed social feeds

Agents that only see X links can use either product. When the same agent must read LinkedIn posts, Reddit threads, and Bluesky skeets, AnyPost’s anypost-md skill rewrites every supported host to anypost.md/{platform}/… with one key and one credit ledger.

Output quality on X

Both products target LLM context, not marketing embeds: post body, handle, timestamps, and links—not nav bars or scripts.

tweet.md emphasizes its path through official X API semantics (see their docs for details). AnyPost focuses on thread order, optional author metadata, and guest-visible comments when you use a paid key—without asking the agent to parse HTML.

Compare outputs on the live preview or the full X conversion guide.

Pricing (high level)

tweet.md: paid API access after checkout; see their pricing page for current packs and profile pricing.

AnyPost: credit packs from Starter ($5 / 500 credits) through Agency ($99 / 20,000). A typical single post costs one credit; each thread segment or comment adds credits per pricing. Pro+ plans unlock Instagram, LinkedIn, Threads, and several other networks.

When tweet.md is enough

• Your pipeline is X-only and already ships the tweet.md agent skill in production.
• You need Obsidian frontmatter via ?format=obsidian.
• Profile Markdown (tweet.md/handle) is a first-class requirement (paid on tweet.md).

Respect tweet.md as a focused X specialist—there is no need to migrate if your scope never leaves Twitter.

When AnyPost is worth adding or switching

• Agents ingest X and other networks in one session.
• You want one API key and credit balance for research across LinkedIn, Reddit, HN, and Bluesky.
• You prefer the /x/ prefix pattern and WebMCP hooks alongside the anypost-md skill.

Start with the X converter, then explore all platforms.

FAQ highlights

Can I use both? Yes—different URLs for different jobs.

Free tier? tweet.md: five guest posts per IP per month (their public docs). AnyPost: ten single-post conversions per day on Starter platforms (per IP).

Threads? Both support ?thread=full; AnyPost bills per post in the chain with a paid key.

Related reading

• Convert X posts to Markdown — deep X guide
• AnyPost vs Context.dev and Microlink — generic web URL tools
• Save LLM tokens with URL to Markdown
• API documentation
• Install the agent skill

---

Last updated: June 2, 2026