DocsFAQ
FAQ
The questions we field most often during the beta. Every answer describes how the Hub works today, with some indications of future developments.
01How is the Valency Hub different from preprint servers and online publishing sites?
The Hub shares a number of features with preprint servers like arXiv and medRxiv: people can upload their original work to share openly with others in the community. We, like many others, support open science and open research. The Hub is different in a few ways:
- Speed: your submissions are processed automatically. So instead of waiting hours, days, or even months for your work to be published, it goes live within seconds of when you publish it, for other people to read and, shortly after, for agents to find.
- No gatekeeping on AI usage: we’re bullish on the use of AI in science and research, and we don’t think that AI assistance inherently leads to worse results.
- Declare AI contributions openly: attest to the roles AI had in the generation of your work, using CRediT, an internationally recognized taxonomy for assigning credit (see Machine contribution).
- No rate limits on submissions: for vetted authors, we do not limit the rate of submissions. You’re more productive than ever, and where you publish should respect that.
- People and agent friendly: we normalize submissions internally so that agents can quickly read a work’s content and people can see a beautifully rendered paper in the browser or on a mobile device.
- Centralized works from across the research landscape: the Hub accepts and accumulates works from all domains of research, from astronomy to zoology. Aggregating and normalizing data allows agents and people to have a wide search radius when doing deep research.
- Collections: we curate interesting collections of works from different areas of research, to highlight the great work being done with AI assistance.
- Agent submissions (coming soon).
- Agentic reviews for submitted works (coming soon).
02If I publish on the Hub, can I publish my work elsewhere?
Yes. You may publish or post your work elsewhere. You are granting a license for its use, not turning over copyright. If it has already appeared elsewhere, the Published elsewhere step of the submission form is where you point to that record.
03I’m a co-author of a paper. Can I submit it to the Hub?
Yes. In the U.S., under the U.S. Copyright Act (17 U.S.C. § 201(a)), co-authors are considered “joint authors” who hold equal, undivided ownership shares of the entire work by default. Unless your collaboration disallows this, or the work has already been published in a journal that restricts it, a co-author of a paper can unilaterally grant a non-exclusive license (like the Creative Commons licenses the Hub offers) for the work without the permission of the other co-authors, as long as you still hold your share of the copyright: it hasn’t passed to an employer as work made for hire, or been assigned to a publisher. When you submit, list every author of the work; see how co-authors confirm authorship.
04What is a “work”, and how is it different from a paper?
A work is the record the Hub keeps for one piece of research. It is created once, when you finalize your first submission for it — after the parse has finished and you have reviewed what it extracted — and it holds every version you publish afterwards; finalizing a later upload adds a version to that existing work instead of creating a new one. “Paper” is simply what this site calls a work when it shows you one (the pages live under /works), and the API calls the same thing a publication.
A submission made through the submit page is different: it is one upload attempt. It either fails, or is parsed and parked for your review; only when you finalize it does it become a draft version of a work. Status is tracked per version, not per work — each version is unpublished, published, or retracted.
05Who can see my draft before I publish?
Only you. A co-author can’t read a draft, even after confirming (see the next question). A draft is an unpublished version, and the Hub answers everyone else — the public paper page and search included — as if it did not exist.
You read your own draft on the Preview tab of the work’s Manage page, which is the only place on this site an unpublished version can be read; there is no share-by-link for drafts.
06How do co-authors confirm authorship?
Valency doesn’t email your co-authors. After you publish, the work’s Manage page gives you a confirmation link and a message to send them yourself. A co-author opens the link, signs in, picks their name from the newest published version, and confirms or declines. Manage shows you each answer.
Confirming updates their entry with the details they check: their name for citations, affiliation and ORCID. The name printed on the paper stays as you wrote it. Declining takes them off that version’s public author list. Neither changes an earlier version, and neither gives them any rights over the work: they cannot read a draft, publish, or upload a version.
Publishing doesn’t wait for answers: everyone you list is shown by name as soon as you publish. A DOI is different. Valency won’t issue one for a version until every co-author has confirmed or declined, unless Valency waives that.
The submission form requires an email address for everyone you list except yourself. It addresses the message on Manage, and a co-author can confirm from an account with a different address. You can edit the parsed author list until you finalize your first submission, so check it then. When you upload a new version, its author list follows the new PDF, or, if the PDF’s authors can’t be matched with the previous list, starts from the previous version’s list for you to check. People who confirmed keep what they confirmed unless you change it, and then they confirm again. Anyone who declined stays off.
07What does “checked by machines” mean?
Today it means your upload is parsed and validated by machines before it becomes a draft, not that it is judged. For a PDF, the pipeline scans the file for unsafe content (embedded scripts or launch actions fail the upload), validates the format, and transcribes the full text into a structured representation — headings, references, equations, figures. A vision-model transcription is replacing the current PDF parser, but that switch is still pending in the deployed pipeline. A LaTeX project is translated from its source into the same structured representation instead. Before you finalize you review and correct the extracted title, abstract and authors, and choose the work’s subject and keywords yourself; the body itself is edited on the draft’s Preview tab after finalization, before you publish. The pipeline records quality signals about the parse, such as how many citations it could not link, but applies no gate on them and produces no verdicts.
No reference checks, prior-art scans or claim checks report results on your work yet. Finalizing a submission has its own requirements — among them your authorship attestation, the AI-use declaration, a license, a primary subject field, an ancillary data answer, an email for each co-author, and marking which listed author is you — and publishing a draft has five: you are the submitter, there is a draft to publish, it has a license, the Hub has finished preparing the full paper, and any ancillary links have passed their checks. That last is the one machine check among them, and it looks at your links, not your work: none of them is a verdict on the work.
08Which licenses can I choose?
Two: CC BY 4.0 and CC BY-SA 4.0. The license picker offers exactly those, with a link to each license’s terms, and nothing is preselected on a first submission. The license belongs to the version, not the work, and a version cannot be published without one.
When you upload a new version the form is prefilled with the license on the work’s current head version, which may be an unpublished draft; if that head version has no license, nothing is prefilled. Either way you are choosing again: a published version’s grant cannot be revoked, so the only way to correct a license is a new version. Whether the choice should be constrained between versions, and whether a Valency license will be offered, are being decided. Works that reach the Hub from arXiv may carry arXiv’s non-exclusive license.
09How do versions work, and can I upload a new one?
Yes, if you are the work’s submitter. The Manage page has an Upload new version action; it opens the submit page with the work as its target. The upload is reviewed like any submission, and once you finalize it, it becomes the work’s draft (a work has one draft at a time, so finalizing replaces any draft you have not published). Publishing the draft gives it the next number — v1, v2, and so on — and makes it publicly readable.
Earlier published versions stay on the record unless Valency approves a deletion request: for readers, the work’s public permalink resolves to its newest published version, and appending _v1, _v2, … to it addresses a specific one. A removed version’s address answers “not found”. If the newest version has been retracted, the unversioned permalink’s page header falls back to the newest earlier version that is still published, or shows the retracted version when none is, and the full text is not served there either way. The Status panel on the Manage page lists each published or retracted version’s number, date and the note you wrote for it, plus any draft, which has no number until it is published. Text diffs between versions are not computed yet.
10What is the W_ identifier and the permalink, and is there a DOI?
When a work is published for the first time the Hub mints its Valency identifier: W_ followed by eight characters from an alphabet with no look-alikes (no 0, 1, i, l or o). Written vlnc:W_… in citations, it is the work’s permalink on this site, /works/W_…, and it is minted once and never reissued or reused, even if the work is later retracted. Before first publish a work is addressed by its durable work id, the one its Manage page address uses; the Valency identifier is the public handle the Hub promises to keep.
Valency issues DOIs itself, for selected versions. You can’t request one from the Hub yet.
11How permanent is a link, really? Doesn’t it depend on Valency hosting it?
Valency will make its best effort to ensure that works published on the Hub are continuously available. Furthermore, works published on the Hub will be preserved by a third party to ensure their longevity.
12How do I declare AI contributions, and what if none were used?
In the AI contributors step of the submission form, which you can fill in while your upload is still being parsed. Choose each model or tool once, select the CRediT contributor roles it helped with, and add it. Several models can share a role. To check or change the declaration one role at a time, open Review assignments by role. Used several versions of one model? Choose its “multiple versions” entry. The form offers ten roles, by short label, each standing for a CRediT role: Concept (Conceptualization), Data (Data curation), Analysis (Formal Analysis), Investigation, Methods (Methodology), Software, Validation, Figures (Visualization), Drafting (Writing — original draft) and Editing (Writing — review & editing). Every contribution you declare here is recorded as a collaborator, not an author, and is self-declared: the Hub does not verify it.
If nothing you used was AI, check None of my tools were AI. You must do one or the other — the Hub refuses to finalize a submission that neither lists contributors nor affirms there were none. Declaring none is recorded on the version you submit, while each AI contributor you list is recorded on the work itself rather than on one version (for a new version, once that version is published). The paper page lists the work’s AI contributors with their CRediT roles, and its machine contribution statement marks each one as self-declared at submission. When none were listed it says “none listed by the authors”; your “None of my tools were AI” answer itself is not shown there.
13How do I cite a work?
By its Valency identifier. The paper page shows vlnc:W_… beside a control that copies the permalink — this site’s address followed by /works/W_… — which serves the work’s newest published version, unless that version has been retracted (see the versions question above); to pin a citation to one version, use the versioned form, vlnc:W_…_v2.
The Cite controls on the paper page copy a formatted citation and a BibTeX entry (an @misc record keyed on author, year, and title, with the work’s identifier in the eprint field and its permalink in url). Works ingested from elsewhere, such as arXiv, keep those controls disabled until we settle how best to cite them — their canonical citation is the original source’s. A DOI is included only when the work has one (see above).
14What is the Valency MCP (Valency Bond)?
Valency Bond is Valency’s MCP server, an endpoint at mcp.valency.io that research agents connect to in order to search a corpus of scholarly works. It is separate from the Hub: the Hub is where you publish; Bond is where agents read.
If you have Hub access, works published here, yours included, are searchable through Bond shortly after they are published. The Valency MCP page points to Bond’s own documentation.
15What does “beta” mean for the permanence of my work?
A published work’s Valency identifier and permalink are never reassigned or reused, even after a work is removed, and publishing cannot be taken back by you: once a work is public, only Valency can remove it, on your request, and readers may already have read, cited or copied it. A submission that has not been finalized, by contrast, carries no permanence promise at all.
16Can I retract or delete a work?
Before anything is public, yes. The submitter can delete a work that isn’t public yet, or an unpublished draft version, from the Manage page, giving a reason. It is hidden from everyone at once and permanently removed later; the confirmation gives a reference and, once one is set, the date. Until the removal, only Valency support can restore it: email [email protected] with the reference.
Once a work or a version is public, you can’t delete it yourself: request its deletion from the same page, giving a reason, and Valency reviews the request. It stays public until the request is approved; if it is declined, the reviewer’s note appears on the Manage page. Either way, identifiers and version numbers are never reused, a removed address answers “not found”, and co-authors are not notified. A work with a DOI can’t be removed this way, since its DOI has to keep resolving: email support.
Retraction is a request that Valency decides on rather than an action you take. The request form on the Manage page shows what it will ask for, but it is not wired up yet, so reach the team directly if a version needs to come down.
A retracted version stays on the record under its identifier, which is never reused. The design is a retraction notice at the permalink with the retracted text still readable behind it; that notice is not built yet. Today the unversioned permalink stops showing the text once the newest version is retracted, while the retracted version’s own versioned address (W_…_v2, say) still serves it.