discordApiUsersMeEntitlements

Seen 3 time(s) in 3 run(s).

What it sent and what came back (the newest 3 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder, step 2: snapshot: 200, 382 ms

Sent:

{
  "query": {
    "with_sku": "false",
    "with_application": "false",
    "entitlement_type": "11",
    "exclude_ended": "true"
  },
  "body": null
}

Answered:

[]

runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 200, 391 ms

Sent:

{
  "query": {
    "with_sku": "false",
    "with_application": "false",
    "entitlement_type": "11",
    "exclude_ended": "true"
  },
  "body": null
}

Answered:

[]

runs/inspect/20261028T062914_sourcedandsoldtothehighestbidder, step 5: click e40: 200, 314 ms

Sent:

{
  "query": {
    "with_sku": "false",
    "with_application": "false",
    "entitlement_type": "11",
    "exclude_ended": "true"
  },
  "body": null
}

Answered:

[]

What it does

Lists everything the account is entitled to (gifts, Nitro, items).

What our machine does with it

Nothing in log-cli waits for it or reads it. It is part of what Discord's client loads around the page; a watch or a send never depends on it.

What can go wrong

The account carries on whatever it answers; a failure here changes nothing for our steps.