Show HN: Accept-md – One command to make Next.js sites LLM-scraping friendly
Show HN (score: 5)Description
`Accept: text/markdown`
Most websites today are built for humans. When AI agents try to consume them, they get complex HTML instead of clean, structured content.
So I built *accept-md* – a simple open-source package for Next.js that helps solve this.
Getting started is intentionally minimal:
``` npx accept-md init ```
After that, your existing Next.js routes can automatically respond with Markdown whenever an AI agent (or any client) requests it. No redesigns, no CMS changes, and no duplicate pages to maintain.
Right now the project is:
* Focused only on Next.js * Middleware-based and lightweight * Designed to work with existing apps * A small step toward more AI-friendly websites
This is an early experiment, but I think the idea itself matters as AI agents become first-class consumers of the web.
I’ve open-sourced it and would love help with:
* Better markdown extraction * Edge cases across Next.js setups * Performance and caching * Tests and examples * Documentation * Eventually adapters for other frameworks
Would love feedback from the HN community on the approach – and whether `Accept: text/markdown` feels like a pattern worth standardizing for the AI-native web.
More from Show
Show HN: GitClaw – An AI assistant that runs in GitHub Actions
Show HN: GitClaw – An AI assistant that runs in GitHub Actions
Show HN: Buquet – Durable queues and workflows using only S3
Show HN: Buquet – Durable queues and workflows using only S3 buquet (bucket queue) is a queue and workflow orchestration tool using only S3-compatible* object storage. S3 is the control plane making it much simpler than alternatives. This does come with tradeoffs (see docs), but I do believe there is a niche it can serve well.<p><a href="https://horv.co/buquet.html" rel="nofollow">https://horv.co/buquet.html</a> <a href="https://github.com/h0rv/buquet" rel="nofollow">https://github.com/h0rv/buquet</a><p>* see <a href="https://github.com/h0rv/buquet/blob/main/docs/guides/s3-compatibility.md" rel="nofollow">https://github.com/h0rv/buquet/blob/main/docs/guides/s3-comp...</a>
Show HN: Pygantry – Why ship a whole OS when you just need a Python environment?
Show HN: Pygantry – Why ship a whole OS when you just need a Python environment? "Hi Hacker News, I’ve always found Docker to be overkill for simple Python deployments. It's heavy, complex for non-tech users, and often results in 500MB+ images for a 10KB script. That’s why I built Pygantry. It’s a minimalist 'container' engine based on Python venv but made portable and relocatable. Key features: Lightweight: A full 'shipped' app is usually < 20MB. Zero-Config: No daemon, no root, no Dockerfile complexity. Portable: Build once, zip it, and run it anywhere with a Python interpreter. Founder friendly: Built-in licensing and stealth modes for those building a business. I built this to simplify my own VPS deployments. I'd love to get your feedback on the architecture and how you handle 'Docker-fatigue' in your workflow.
Show HN: Teaching AI agents to write better GraphQL
Show HN: Teaching AI agents to write better GraphQL We’ve been seeing more and more developers use AI coding agents directly in their GraphQL workflows. The problem is the agents tend to fall back to generic or outdated GraphQL patterns.<p>After correcting the same issues over and over, we ended up packaging the GraphQL best practices and conventions we actually want agents to follow as reusable “Skills,” and open-sourced them here: <a href="https://github.com/apollographql/skills" rel="nofollow">https://github.com/apollographql/skills</a><p>Install with `npx skills add apollographql/skills` and the agent starts producing named operations with variables, `[Post!]!` list patterns, and more consistent client-side behavior without having to restate those rules in every prompt.<p>We’re hopeful agents can now write GraphQL the way we'd write it ourselves. Try out the repo and let us know what you think.
No other tools from this source yet.