The -r option should not be used if the output will be fed into another JSON parser; only the last jq in the pipeline should use it – otherwise you risk feeding non-JSON data into the second jq instance.

Your last example with .[0].t seems correct and works with jq 1.6.

$ cat json | jq '.tx' | jq -r '.[0].t'
t for a

But this can be simplified to a single jq invocation, first incrementally to:

$ cat json | jq -r '.tx | .[0].t'
t for a

and then finally to:

$ cat json | jq -r '.tx[0].t'
t for a

I think this is fairly easy to achieve for this inner list. The values seem to be all zero's so...

jq  '.[][1]' < yourjsonfile

Just to provide another approach. When working with lists, dicts and other types python is the right tool. To give you an idea on how you could retrieve the values from the list you'd do something lik:

#!/usr/bin/env python

mylist = [[1645128660000,0],[1645128720000,0],[1645128780000,0],[1645128840000,0],[1645128900000,0],[1645128960000,0],[1645129020000,0],[1645129080000,0],[1645129140000,0],[1645129200000,0]]

for k,v in mylist:
    print("Key":,k)
    print("Value":v)

Or using list comprehension

[v for k,v in mylist]

should be sufficient. There is also this awesome page where you can play around with jq: https://jqplay.org/#

You can get pairs by using the to_entries filter. It will transform the dict into an array of items:

$ curl <url> | jq ".rates | to_entries"

[
    {
        "key": "btc",
        "value": {
            "name": "Bitcoin",
            "unit": "BTC",
            "value": 1,
            "type": "crypto"
        }
    },
    {
        "key": "eth",
        "value: {...}
    },
    },
    { ... }
]

Once you have such entries, you can access .key and .value.value of each item to get the pairs you want:

$ curl <url> | jq '.rates | to_entries | .[] | [.key, .value.value]'

["btc", 1]
["eth", 14.376]
[...]

The same for transforming them into a string:

$ curl <url> | jq -r '.rates | to_entries | .[] | "\(.key) \(.value.value)"'
btc 1
eth 14.368
...

Note that the select(.) you had before seems completely redundant...

The command-line tool jq writes to STDOUT and/or STDERR. If you want to write the .AssetId information to STDOUT, then one possibility would be as follows:

jq -r ".[] | .AssetId" input.json

Output:

14462955
114385498
29715011
98253651

A more robust incantation would be: .[] | .AssetId? but your choice will depend on what you want if there is no key named "AssetId".

Enclose the select with a map, as you want to apply the filter to each array item individually while retaining the surrounding array structure.

jq '.items | map(select(.website == "google"))'

[
  {
    "name": "name1",
    "id": "1",
    "website": "google"
  },
  {
    "name": "name1",
    "id": "1",
    "website": "google"
  }
]

Demo

Evidently one of the items in the array is a string. If your jq supports "?", then one possibility would be to use it:

.response[].text?

Another would be to check the type explicitly, e.g.:

.response[] | objects | .text

Yet another possibility:

.response[] | select(type=="object" and has("text")) | .text

If you want to have a placeholder value when there is no "text" field:

 .response[] | if type=="object" and has("text") then .text else null end

So it really depends on your requirements and perhaps the version of jq that you are using.

You can use to_entries, then select the non-null keys and extract the values:

jq 'to_entries | map(select(.key != "null"))[] | (.key, .value.type)' < file2.json

You need to combine filters by means of | operator:

$ jq -r '.[] | .[] | .name' test.json 
rhel6.6
rhel7

The first .[] fetches repositories array. The next .[] fetches all the items of the repositories array. Finally, .name extracts properties from the array items(objects).

Note, the first .[] works on object because it is a documented feature:

.[]
    If you use the .[index] syntax, but omit the index entirely, it
    will return all of the elements of an array...

    You can also use this on an object, and it will return all the
    values of the object.