{
  "name": "Super User Gate",
  "outcome": "scope",
  "scope": "superuser",
  "rules": [
    {
      "type": "nft",
      "address": {
        "networkId": 1,
        "contractAddress": "0xbF394748301603f18d953C90F0b087CBEC0E1834"
      },
      "filter": {
        "tokenId": "0x01",
        "amount": 123
      }
    }
  ]
}
name
string

Human-readable name of the gate. This should be something helpful to organize gates.

outcome
enum<string>
Available options:
scope,
siteAccess,
block
scope
string

String for the resulting scope of the gate. If the rules of the gate apply to the user being verified, then this scope will be surfaced in the JWT

rules
object[]

The rules which will be used to evaluate users being verified. If multiple rules are present in a single gate, then all the rules need to apply for the user to gain the scope defined by the gate.