Hi team,

First off — love the product. I'm a Pro subscriber and have been integrating the screenshot API into my AI agent workflow. Works great for regular tweets.

However, I've run into a limitation with X Articles (long-form posts). When I pass an Article tweet ID to GET /api/v1/screenshot/:statusId, the API only returns a minimal card showing the article link — not the full rendered article content with title, body text, and inline images.

Interestingly, your web UI handles this perfectly. When I paste the same tweet URL on twittershots.com, the full article renders beautifully with all content blocks and images, and I can export it as a long-form screenshot. So the rendering capability clearly exists — it's just not exposed through the public API.

Example tweet: https://x.com/servasyy_ai/status/2042951017462169812

• Web UI result: Full article with title, body paragraphs, and embedded images

• API result: Just a card with a truncated x.com/i/article/2042… link

I can see from the network requests that the web UI fetches article data via /api/v2/tweet-details/ (which includes the full contentState with all Draft.js blocks), then renders it client-side. It would be incredibly useful if the v1 screenshot API could also render the full article server-side.

My use case: I'm building an AI agent that processes X/Twitter content. For Article-type posts, the current API output is essentially unusable — a simple card with a link has no informational value. The whole reason I subscribed to Pro (300 API calls/month) is to programmatically generate these screenshots.

Suggested approach (just a thought):

• A query parameter like renderArticle=true on the existing endpoint, or

• A dedicated /api/v1/screenshot/article/:articleId endpoint

Would love to hear if this is on the roadmap or if there's a workaround I'm missing. Happy to hop on a quick call if that helps.

Thanks for building a great tool!

Best, Leon