generated: '2026-09-09'
method: probed
source: >-
  Live probes of https://aegisships.com/wp-json/ on 2026-09-09 and the derived OpenAPI documents in
  openapi/. No compliance, certification or standards claim appears anywhere on aegisships.com.
provider: Aegis Marine Shipmanagement
conformance:
- id: oembed-1.0
  conforms: true
  evidence: >-
    https://aegisships.com/wp-json/oembed/1.0/embed?url=https://aegisships.com/services/ returned
    HTTP 200 with a well-formed oEmbed 1.0 `rich` response carrying version, provider_name,
    provider_url, title, type, width, height and html.
  note: The only formal specification this surface demonstrably implements.
- id: rfc8288-web-linking
  conforms: true
  evidence: >-
    Collection responses return a `Link` header with `rel="next"`, observed on
    https://aegisships.com/wp-json/wp/v2/media?per_page=1
- id: json-ld
  conforms: true
  evidence: >-
    https://aegisships.com/wp-json/yoast/v1/get_head?url=https://aegisships.com/ returned HTTP 200
    carrying a schema.org JSON-LD graph, emitted by the Yoast SEO plugin.
  note: Search-engine structured data, not an API data contract.
- id: rfc9457-problem-details
  conforms: false
  evidence: >-
    Errors are served as `application/json` with a WordPress `code`/`message`/`data` envelope, never
    `application/problem+json`. Observed on
    https://aegisships.com/wp-json/wp/v2/pages/999999 (HTTP 404).
- id: oauth2
  conforms: false
  evidence: >-
    https://aegisships.com/.well-known/oauth-authorization-server returned HTTP 404. No OAuth
    surface exists.
- id: oidc
  conforms: false
  evidence: https://aegisships.com/.well-known/openid-configuration returned HTTP 404.
- id: pagination
  conforms: true
  evidence: >-
    Page-number pagination with X-WP-Total / X-WP-TotalPages headers, observed on
    https://aegisships.com/wp-json/wp/v2/pages?per_page=1
- id: idempotency
  conforms: false
  evidence: >-
    No idempotency mechanism, and none required — the public surface is read-only. See
    conventions/aegis-marine-shipmanagement-conventions.yml (coverage: na).
domain_standard_conformance:
  applicable: true
  regime: maritime-shipping
  conforms: false
  detail: >-
    The maritime and ship-management sector has real machine-readable standards — IMO Compendium
    / FAL electronic port clearance data sets, IMO DCS and EU MRV emissions reporting, ISO 28005
    electronic port clearance, SMDG EDIFACT/BAPLIE messages for stowage and terminal exchange, and
    the ISM/ISPS code documentation regimes a ship manager operates under. Aegis Marine
    Shipmanagement declares none of them in any published contract, because it publishes no
    contract for its shipping operations at all. The only surface it exposes is a WordPress
    content API, whose market — website content management — has no domain standard to conform to.
  probed:
  - standard: IMO FAL / IMO Compendium
    found: false
  - standard: SMDG EDIFACT (BAPLIE/COPRAR)
    found: false
  - standard: ISO 28005 electronic port clearance
    found: false
  note: >-
    Reward-only dimension. Recording `conforms: false` here documents that the probe ran and found
    nothing; it is not a penalty, and a company with no published API cannot declare a standard in
    one.
certifications: []
certifications_note: >-
  No SOC 2, ISO 27001, PCI, HIPAA or FedRAMP claim, and no trust center, appears on aegisships.com.
  probe-security-programs.py returned vdp=none trust=none on 2026-09-09. No `Compliance` pointer is
  emitted, because there is no published compliance program to point at.