Description
Recognize only exact lowercase null, true, and false tokens.
A JSON lexeme is its textual spelling, which differs from the decoded value. Escapes, quotes, raw control characters, and surrounding whitespace must be interpreted in context.
Recognize only exact lowercase null, true, and false tokens.
When to use this tool
Use JSON Literal Case Sensitive Token when you need a narrowly defined JSON string or separator diagnostic.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, kind. Inspect valid before interpreting the associated values.
Recognize only exact lowercase null, true, and false tokens. Return null or boolean for recognized kind, otherwise invalid.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this narrowly scoped condition passes; it is not necessarily full-document validity. | Required. Boolean. |
| kind | Kind | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "TRUE"
},
"output": {
"valid": false,
"kind": "invalid"
}
}Limitations and assumptions
- Surrounding whitespace and alternative case fail this exact-token check even where document-level whitespace could be accepted.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Parse the entire document when validity matters; a local pattern match cannot establish complete JSON syntax.
References
Similar or alternative tools
- JSON Boolean Case Lexeme Check
Recognize only exact true and false lexemes.
- JSON: JSON Scalar Type Tag
Parse valueJson, reject arrays and objects, and return null, boolean, number, or string as the scalar type.