A small validator that says what it skips
The validator implements the common JSON Schema keywords (type, properties, required, items, enum, const, pattern, min/max, oneOf/anyOf/allOf/not and local $ref). Any keyword it does not implement is listed as unsupported instead of being silently treated as a pass. Integers are compared exactly, even beyond 2^53.
Assertions without code
Assertions are declarative rows: a path, an operator (exists, is null, equals, is a QUANTITY, is an address, length ≥ …) and an optional value. There is no script box, so imported or shared assertion sets cannot run code.
Imports are data
OpenAPI 3 and Swagger 2 operations, OpenRPC methods and Postman requests are listed with their parameters. External $refs are not fetched. Postman pre-request and test scripts are counted and flagged as inert and unsupported. Query parameters that look like credentials are flagged. YAML is not supported in this release.
Questions
Can I paste my own JSON Schema?
Yes. Choose "Custom schema". Local "#/..." references resolve; remote references are reported as unsupported.
Why is my Postman test script ignored?
Running imported JavaScript would mean executing untrusted code in this page. Scripts are shown as inert so you know they exist.
What is in the method pack?
Standard eth_, net_ and web3_ read methods with parameter shapes, result types and notes, dated and versioned. Signing and broadcast methods are listed as excluded.