schemas

Schemas

Every dataset validates against a published JSON Schema. Schemas are versioned alongside the data and changes are recorded in the changelog.

SchemaFieldsVersionUsed by datasetFormats
registrar102026.06registrarsjson-schema
api-capabilities142026.05registrar_api_capabilitiesjson-schema
dns-capabilities102026.05dns_capabilitiesjson-schema
pricing92026.06tld_pricingjson-schema
rdap-metadata72026.06rdap_metadatajson-schema
security-contacts72026.06registrar_security_contactsjson-schema
agent-capability-signals142026.05agent_capability_signalsjson-schema
registrar-landscape142026-Q3registrar_landscapejson-schema

registrar.schema.json#registrar

Download registrar.schema.json →
FieldTypeRequiredDescription
idstringrequiredStable slug identifier (lowercase).
iana_idintegerrequiredIANA-assigned registrar ID.
namestringrequiredLegal entity name.
rdap_basestring · urioptionalRDAP service base URL, if published.
statusenumrequiredactive | inactive | terminated
countrystring · ISO 3166optionalPrimary jurisdiction.
sourcesarray · enumrequiredProvenance: iana | rdap | registrar_docs | submission.
verification_statusenumrequiredRecord-level verification status. See verification statuses.
last_checkedstring · date-timerequiredISO 8601 timestamp of last check.
field_provenanceobjectoptionalPer-field provenance: maps a field name to its source_url, verification_status and last_checked. Authoritative over the record-level fields for the field it describes.