betaFeedback
DocsGetting started
docs / getting started

Getting started

Welcome to Valency Hub, the new home to read, publish, review and discover research, designed for people and their agents. If you’ve been authoring with AI assistance, we think this is the place you’ll love.

Everyone can read what’s on the Hub, logged in or not. If you’re doing research, you can also connect your agents and LLMs, closed-source or open-weight, to Valency Bond, Valency’s MCP server, and search Hub works alongside 50 million more papers. Get started here (it’s free for almost everyone).

During the beta, publishing happens in the browser; there is nothing to install, and the whole process takes only a few minutes.

01Sign in

Reading published works needs no account. To submit, choose Sign in and continue with Google, Microsoft or GitHub. The same flow handles new and existing accounts. Then open Submit.

02Upload your manuscript

On the submit page, drop a file or click to choose one: a PDF, a single .tex file, or a zip or tar archive of a LaTeX project. One file is one upload, and an upload from the browser is currently limited to 10 MB. The other two ways in that the page shows, submitting from a terminal and linking a Google Doc, are not available yet.

The Hub then parses the file: it scans it for unsafe content, validates the format, and transcribes the text into a structured representation of headings, references, equations and figures. The FAQ says exactly what that does and does not check.

03Answer five questions while it parses

Five steps of the submission form need nothing from the parser, so you can fill them in while it runs:

  • License: CC BY 4.0 or CC BY-SA 4.0.
  • Published elsewhere: point to the work’s journal, conference or preprint record, if it has one.
  • Subject & keywords: the work’s primary subject field and the keywords you choose for it.
  • AI contributors: list the models and systems that contributed, or affirm that none did. See Machine contribution.
  • Ancillary data: link the code, data, proofs and workflows behind the work, or say you have nothing to add. After you finalize, we check what’s publicly visible and, where we can, save a SHA-256 hash of it, with the time we checked, on that version of your work. The more you add here, the easier it is for others to understand and reproduce your work.

04Review what the parse extracted

When the parse lands, the remaining four steps unlock: Title & abstract, Authors, Version notes, and Review & submit. Correct the extracted title, abstract and author list here, give an email address for every co-author, and mark which listed author is you. The author list is only applied on a work’s first submission, so check it now; Author guidelines covers what listing a co-author does and does not do.

Finalizing the last step turns the submission into a draft: an unpublished version of a work. Only you can read a draft.

05Preview, then publish

The work’s Manage page is where a draft lives. Its Preview tab is the only place an unpublished version can be read, and it is where you edit the parsed body before anyone else sees it. When the draft is right, publish it. Publishing needs six things: you are the submitter, there is a draft, it has a license, the Hub has finished preparing the full paper, any ancillary links have passed their checks, and your account can publish. A link that fails holds publishing until you fix or remove it on the Manage page. Until the Valency team has verified your identity, the Manage page offers Request publishing instead of letting you publish; your drafts stay private meanwhile.

Publishing is a one-way door. It assigns the version number, makes the version publicly readable and, the first time, mints the work’s permanent identifier. After that only Valency can remove it, on your request, and nothing unpublishes what readers have already seen.

06After publishing

The work has a Valency identifier, written vlnc:W_…, and a permalink at /works/W_…; the Cite controls on its page copy a formatted citation and a BibTeX entry. To revise it, use Upload new version on the Manage page: the upload goes through the same steps and publishes as v2, with v1 kept on the record. The FAQ covers versions, identifiers and citing in detail.