Convert Threads posts to Markdown

Whole conversations captured as one document. Swap the domain for anypost.md and get clean, LLM-ready Markdown back. No scraping, no copy-paste.

Turn a public Threads URL into clean, portable Markdown for LLMs, notes, research, and archives. This guide follows the same domain-swap workflow as the X guide, adapted for Threads.

Want to test the form first? Use the Threads converter or start from the all-platform preview.

Why use AnyPost for Threads?

Whole conversations captured as one document. Instead of pasting a live URL and hoping an AI tool can read it, AnyPost returns the post as a stable Markdown document with attribution.

Approach	What you get
Paste the original link	Preview cards, login walls, or incomplete context
anypost.md	Clean Markdown with source URL and platform context

01: Cleaner context
Markdown removes navigation, overlays, embeds, and tracking parameters so models see the post content first.

02: Better archives
The output is plain text, easy to diff, store in Obsidian, add to a CMS, or keep in a research folder.

03: Predictable automation
The browser URL swap and the JSON API share the same conversion pipeline, so scripts and manual workflows produce the same style of output.

Step-by-step workflow

01: Copy the Threads URL
Use the public permalink for the post, article, story, video, pin, or thread you want to preserve.

02: Swap the domain to anypost.md
Open the AnyPost URL in your browser. The platform prefix keeps routing explicit.

Before: https://threads.net/@zuck/post/DFNf8bvpP2I
After:  https://anypost.md/threads/@zuck/post/DFNf8bvpP2I

03: Add paid options when needed
Threads requires Pro, Scale, or Agency plus an apk_ key because it is a Pro-tier source with higher fetch cost.

04: Copy the Markdown output
Use the result in a prompt, archive, markdown editor, CMS, or API workflow.

What you get

• Whole conversations captured as one document
• Reply chains kept in order
• Author handle and post text normalized to Markdown
• Available on Pro and above

# Example Threads post

Clean post text appears here, with line breaks preserved and noisy page chrome removed.

- Source platform: Threads
- Original URL: https://threads.net/@zuck/post/DFNf8bvpP2I
- Markdown URL: https://anypost.md/threads/@zuck/post/DFNf8bvpP2I

---
2026-06-01 · Threads · [Original post](https://threads.net/@zuck/post/DFNf8bvpP2I)

Good for

• Feeding exact Threads context into ChatGPT, Claude, Gemini, Cursor, or another AI assistant.
• Saving source posts in Obsidian, Notion, a research database, or a static-site content folder.
• Quoting public posts with the original URL and platform timestamp kept together.
• Building lightweight review, monitoring, or archive scripts around a stable Markdown response.

For agents: fetch Markdown, not web pages

Give AnyPost to OpenClaw, Codex, Cursor agents, Claude Code, and RAG workers as their Threads fetch layer. Instead of driving the original site, the agent should rewrite the URL to anypost.md or call /api/convert, then read the clean Markdown response.

That keeps agents out of brittle DOM scraping, rate-limit loops, login walls, and browser automation noise.

Agent setup

• Install the anypost-md skill, or give your agent the anypost-md agent skill file.
• Store an apk_ key from Login for Agents and send it as Authorization: Bearer apk_live_xxx for paid options.
• Use the domain-swap URL when the agent wants a plain Markdown document; use /api/convert when it needs JSON fields such as markdown, credits, or structured errors.

Original: https://threads.net/@zuck/post/DFNf8bvpP2I
Agent:    https://anypost.md/threads/@zuck/post/DFNf8bvpP2I

Paid options and API usage

Threads is Pro+ only. After buying credits, Login with Google to redeem checkout, create an apk_ key, and pass it with the conversion request:

curl -sS -H "Authorization: Bearer apk_live_xxx" \
  "https://anypost.md/threads/@zuck/post/DFNf8bvpP2I"

When your app needs JSON fields such as markdown, credits, or structured errors, call /api/convert with the original URL:

curl -sS -H "Authorization: Bearer apk_live_xxx" \
  "https://anypost.md/api/convert?url=https%3A%2F%2Fthreads.net%2F%40zuck%2Fpost%2FDFNf8bvpP2I"

Entry point	Response	Best for
/threads/... domain swap	text/plain Markdown	Browser, curl pipes, agents that want a document
/api/convert?url=...	JSON with markdown	Apps that need metadata and structured errors

See Documentation for query parameters, credit costs, and authentication.

Threads FAQ

Which Threads URLs are supported?

Both threads.net and threads.com post links work. Swap the domain for anypost.md and add the /threads/ prefix is handled automatically.

Why does Threads need a Pro plan?

Threads is a Pro-tier source, included alongside Substack and long-form X articles.

Is Threads available on the free tier?

No. Threads requires Pro, Scale, or Agency plus an apk_ key. Starter covers X tweets, Reddit, Bluesky, Mastodon, Hacker News, YouTube, and Medium.

Can agents use AnyPost instead of scraping Threads?

Yes. Give OpenClaw, Codex, Cursor agents, Claude Code, or your RAG worker the anypost-md skill at /i/skill.md and an apk_ key from Login for Agents. The agent should call AnyPost for Threads URLs and read Markdown instead of scraping the original page, which avoids brittle selectors, rate limits, and login walls.

Next

• Try the Threads converter with a real URL.
• Convert any post to Markdown, the multi-platform overview.
• Feed context to AI models, prompt patterns for using Markdown output.
• Archive posts into Obsidian, frontmatter and vault organization.