You should not expect to 'see' the key. But you should be able to list it, and the export or send it. For example, I can list the key that I use to sign uploaded software
See the manual for more details.
gpg -k sudodus
pub 2048R/EB0FC2C8 2012-04-08
uid Nio Sudden Wiklund (sudodus) <email@example.com>
sub 2048R/4FC1D9E7 2012-04-08
List all keys from the public keyrings, or just the keys given on the command line. -k
is slightly different from --list-keys in that it allows only for one argument and takes
the second argument as the keyring to search. This is for command line compatibility
with PGP 2 and has been removed in gpg2.
Avoid using the output of this command in scripts or other programs as it is likely to
change as GnuPG changes. See --with-colons for a machine-parseable key listing command
that is appropriate for use in scripts and other programs.
-K List all keys from the secret keyrings, or just the ones given on the command line. A #
after the letters sec means that the secret key is not usable (for example, if it was
created via --export-secret-subkeys).
Either export all keys from all keyrings (default keyrings and those registered via
option --keyring), or if at least one name is given, those of the given name. The new
keyring is written to STDOUT or to the file given with option --output. Use together
with --armor to mail those keys.
--send-keys key IDs
Similar to --export but sends the keys to a keyserver. Fingerprints may be used instead
of key IDs. Option --keyserver must be used to give the name of this keyserver. Don't
send your complete keyring to a keyserver --- select only those keys which are new or
changed by you. If no key IDs are given, gpg does nothing.