.nh
.TH "GT-GPG-KEY-VERIFY" "1" "Nov 2026" "gitea-cli" "gitea-cli Manual"

.SH NAME
gt-gpg-key-verify - Verify a GPG key with a signed token


.SH SYNOPSIS
\fBgt gpg-key verify <key-id> [<file>] [flags]\fP


.SH DESCRIPTION
Verify a GPG key that Gitea holds as unverified, so that it is trusted for all of your activated
email addresses, not only those it names. Sign the token that gt gpg-key token prints with
the key, as an ASCII-armored detached signature, and pass the signature as a file or on stdin. The key
is named by its GPG key ID, as gt gpg-key list shows it.

.SS JSON FIELDS
.EX
can_certify, can_encrypt_comms, can_encrypt_storage, can_sign, created_at,
emails, expires_at, id, key_id, primary_key_id, public_key, subkeys, verified
.EE


.SH OPTIONS
\fB--dry-run\fP[=false]
	Show the write requests gt would send, without sending them

.PP
\fB-h\fP, \fB--help\fP[=false]
	help for verify


.SH OPTIONS INHERITED FROM PARENT COMMANDS
\fB--csv\fP[=""]
	Output CSV with the specified comma-separated \fBfields\fR, or all fields

.PP
\fB--debug\fP[=false]
	Log the method, URL, status, and duration of each HTTP request to stderr

.PP
\fB--host\fP=""
	Gitea instance \fBURL\fR, including any base path

.PP
\fB--interactive\fP[=false]
	Allow prompts with machine output

.PP
\fB-q\fP, \fB--jq\fP=""
	Filter JSON output using a jq \fBexpression\fR; implies --json

.PP
\fB--json\fP[=""]
	Output JSON with the specified comma-separated \fBfields\fR, or all fields

.PP
\fB--no-input\fP[=false]
	Disable prompts and implicit editor/browser interactions

.PP
\fB--sudo\fP=""
	Perform API requests as this \fBuser\fR (requires an administrator account)

.PP
\fB--template\fP=""
	Format JSON output using a Go \fBtemplate\fR; implies --json (see gt help formatting)

.PP
\fB--user\fP=""
	Account \fBname\fR on the selected instance


.SH EXAMPLE
.EX
$ gt gpg-key token | gpg --armor --detach-sign --default-key 3AA5C34371567BD2 > token.asc
$ gt gpg-key verify 3AA5C34371567BD2 token.asc
.EE


.SH SEE ALSO
\fBgt-gpg-key(1)\fP