科技回声

Just change arxiv.org to arxiv-txt.org in the URL to get the paper info in markdownExample:Original URL: <a href="https://arxiv.org/abs/1706.03762" rel="nofollow">https://arxiv.org/abs/1706.03762</a>Change to: <a href="https://arxiv-txt.org/abs/1706.03762" rel="nofollow">https://arxiv-txt.org/abs/1706.03762</a>To fetch the raw text directly, use <a href="https://arxiv-txt.org/raw/abs/1706.03762" rel="nofollow">https://arxiv-txt.org/raw/abs/1706.03762</a>, this will be particularly useful for APIs and agents

If you train an LLM on only formally verified code, it should not be expected to generate formally verified code.Similarly, if you train an LLM on only published ScholarlyArticles ['s abstracts], it should not be expected to generate publishable or true text.Traceability for Retraction would be necessary to prevent lossy feedback.

Really clean API design, I'm a fan!

It just extracts the abstracts?

The example you give doesn't seem to work - the raw txt does not have authors.

This would be awesome wrapped in an MCP server/tool call :)

Was super excited that it was going to be the actual papers, kinda cool but just being abstracts doesn't go very far, good luck getting the papers working thats gonna be pretty cool once working, then to feed it all into a vector db XD

Really clean API design, I'm a fan!

It just extracts the abstracts?

The example you give doesn't seem to work - the raw txt does not have authors.

This would be awesome wrapped in an MCP server/tool call :)

Show HN: ArXiv-txt, LLM-friendly ArXiv papers

6 条评论

Show HN: ArXiv-txt, LLM-friendly ArXiv papers

6 条评论