Article API
An article is more than a block of text. It has a title, an audience, a source trail, a publication state, and a destination.
Explore this guide ↗Turning permitted website material into an article workflow requires more than copying visible text. Navigation, repeated footers, outdated pages, and embedded instructions can all interfere with a clean source record. The starting point is a reliable account of what the original page actually says.

Use owned, licensed, or otherwise appropriately reusable source material. Preserve the source URL, retrieval context, title, and relevant excerpt boundaries so a reviewer can trace a claim back to its origin.
Distinguish the main article from menus, comments, promotional modules, and repeated boilerplate. Keep meaningful tables and captions associated with the correct section.
Capture the URL, document title, and evidence excerpts separately from the draft. Mark missing dates or unclear authorship as unknown.
Use the source to support a new editorial purpose. Compare the finished draft with the evidence rather than treating extraction as verification.
A page being publicly readable does not automatically make all reuse unrestricted. Do not publish copied articles as original work.
No. Source text is material to analyze. It should not gain permission to change the workflow, reveal credentials, or approve publication.
Continue with build an ai-assisted editorial review that does not approve itself for a complete explanation, practical decisions, and a source-backed reference. To compare the neighboring parts of the process, explore the full article workflow library.