Paste an identifier — a DOI, an arXiv id, a Zenodo record — and ask the
live graph one of five questions about it. Every answer says which tier each edge came
from: a named researcher who signed it, or the open-metadata sweep that inferred it. The
two are never blended. No account and no key; anonymous asking runs at ten a minute.
Ground
What does the graph say about a paper?
Have a key?
A key raises your limits; a signing key also opens minting below. Connect once and
it is saved in this browser — you will not have to paste it again on this machine. It travels only
as a header on your own requests, never as a cookie, so no other site can spend it.
Treat it like a password: anyone holding your key can use your limits as you.
Leaked, lost, or just cautious? Generate a fresh one in your account —
that instantly revokes the old one.
Mint
Draft candidate edges from a paper’s reference list, or write one
by hand. Signing happens server-side under your asserter identity.
Minting is permanent. Each signed edge is public, CC0, and appended
to the chained log — retraction is itself a public, signed event.
By hand
The five questions
edges about — every recorded claim touching this work, in both directions.
what supports and what refutes — typed claims, where someone has recorded
that one work supports or refutes another. A recorded refutation is a claim with a name on
it, not a verdict about who is right.
what cites — works recorded as citing this one.
references of — works this one is recorded as citing.
signed only narrows any of them to human-signed claims, dropping the
machine-inferred tier entirely.
A sparse answer is not a claim that nothing cites the work. It means
the sweeps have not reached its citers yet, or nobody has signed a claim from it. Coverage
grows daily, and a well-cited work has thousands of edges, so an answer arrives a page at a
time. Nothing here is a verdict about whether a claim is correct: it is a record of who
stands behind it.
Linkable answers
https://citestamp.com/ask?id=10.1007/s12225-019-9804-7&tool=what_cites
prefills the form and runs it, so an answer can be sent to someone, bookmarked, or handed
back by an assistant. Add &signed=1 for the signed tier only.
Calling it from code or an agent? The same five questions are the
MCP tools and the REST endpoints. Grounding a citation is the short
version; for AI agents is the full integration guide.