generated: '2026-07-21'
method: derived
source: docs.wax.io + observed Chain API behavior; no OpenAPI captured in repo
notes: >-
  Standards posture for the WAX RPC surface. WAX is an Antelope (EOSIO fork)
  chain; its API conforms to the Antelope Chain API and Hyperion History API
  conventions rather than web-API auth/identity standards. No published
  compliance certifications (SOC 2 / ISO 27001 / PCI / HIPAA / FedRAMP) were
  found, so no Compliance pointer is emitted.
standards:
  - id: antelope-chain-api-v1
    conforms: true
    evidence: /v1/chain/* endpoints served; server_version v5.0.1wax01 (Antelope Spring)
  - id: hyperion-history-api
    conforms: true
    evidence: Hyperion /v1/history + /v2 history endpoints available across public WAX nodes
  - id: json-rpc-over-http
    conforms: true
    evidence: JSON request/response over HTTP POST
  - id: oauth2
    conforms: false
    evidence: reads are unauthenticated; writes use secp256k1 transaction signatures, not OAuth
  - id: openid-connect
    conforms: false
  - id: rfc9457-problem-details
    conforms: false
    evidence: errors use the eosio error envelope, not application/problem+json
  - id: fhir-r4
    conforms: false
  - id: fapi
    conforms: false
  - id: scim2
    conforms: false
  - id: odata
    conforms: false