Machine-readable contract

Response schemas

Every JSON response on this site is self-describing. Each one carries a three-field envelope whose $schema pointer resolves to the JSON Schema document for that shape, so an agent can validate a response before it influences a decision.

The envelope

Three top-level fields appear on every JSON response:

{ "$schema": "https://x402.fuchss.app/schemas/<name>.schema.json", "schemaVersion": "1.0.0", "schemaType": "<name>", ... }

Compatibility rules

same version Additive fields

A new optional field is backward compatible and does not change the version.

major bump Remove / rename / resemantize

Removing or renaming a field, or changing what it means, is a new major version.

documented New enum value

A new recommendation or grade value is a documented version change, because strict buyers may reject unknown values.

Two closed enums are worth pinning: recommendation is one of proceed, caution, avoid, parameterize, unverified, not-payable. grade is one of A, B, C, D, F, or ? for unmeasured.

Data & scoring

11 schemas

Endpoint watches

3 schemas