Archive posts into Obsidian

AnyPost can emit Obsidian-friendly output with YAML frontmatter, so saved posts slot neatly into your vault and show up in Dataview queries.

Enable frontmatter output

Append ?format=obsidian to any conversion URL:

anypost.md/x/user/status/123?format=obsidian

For agents: fetch Markdown, not web pages

Give AnyPost to OpenClaw, Codex, Cursor agents, Claude Code, and RAG workers as their Obsidian clipping 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://x.com/user/status/123
Agent:    https://anypost.md/x/user/status/123?format=obsidian

What the file looks like

---
author: Jane Doe
handle: "@janedoe"
platform: x
date: 2026-05-20
source: https://x.com/janedoe/status/123
tags: [clipped, x]
---

# Jane Doe (@janedoe)

The full post text lands here, ready to link and tag.

Organizing the vault

• Keep clipped posts in a /Clippings folder.
• Use the platform and tags fields to build Dataview tables.
• Link concepts with [[wikilinks]] after import.