Is there any way to avoid the interpretation of the '@' value, which assumes the subsequent string is a file to read from?

I want to construct a json object with @timestamp as the value like this:

{"key": "@timestamp"}

via

jo key="@timestamp"

but I found no way to escape the '@' such that it does not try to read from the timestamp file which does not exist