generated: '2026-09-17'
method: derived
source: openapi/_original/linode-api-v4-official-openapi.json and https://techdocs.akamai.com/linode-api/reference/get-started,
  https://techdocs.akamai.com/linode-api/reference/pagination, https://techdocs.akamai.com/linode-api/reference/errors
provider: Linode (Akamai Cloud)
providerId: linode
note: Reward-only. Cloud infrastructure has no cross-vendor contract standard of its own, so no domain_standard
  is claimed for compute, networking or DNS. The one real interoperability commitment Linode makes is S3 API compatibility
  for Object Storage, which is recorded below with the caveat that the S3-compatible surface is NOT described by
  this OpenAPI — the Linode API manages buckets and keys, and the object operations themselves are spoken to a separate
  S3 endpoint with AWS SigV4.
conformance:
- id: oauth2
  conforms: true
  evidence: https://techdocs.akamai.com/linode-api/reference/get-started#oauth — authorization code flow, authorizationUrl
    https://login.linode.com/oauth/authorize, tokenUrl https://login.linode.com/oauth/token, declared as an oauth2
    securityScheme in the OpenAPI with 28 scopes.
- id: rfc6749
  conforms: true
  evidence: https://techdocs.akamai.com/linode-api/reference/get-started — the documentation cites RFC 6749 by name
    and maps login.linode.com to the authorization server and api.linode.com to the resource server.
- id: oidc
  conforms: false
  evidence: https://login.linode.com/.well-known/openid-configuration returned 404 on 2026-09-17; no id_token, no
    OIDC discovery document, no openid scope in the securityScheme.
- id: bearer-token
  conforms: true
  evidence: components.securitySchemes.personalAccessToken — type http, scheme bearer.
- id: pagination
  conforms: true
  evidence: https://techdocs.akamai.com/linode-api/reference/pagination — page/page_size request parameters, data/page/pages/results
    response envelope, documented defaults and bounds.
- id: rfc9457
  conforms: false
  evidence: No application/problem+json media type appears anywhere in the 4.229.1 contract; errors use a vendor
    `errors[]` envelope.
- id: idempotency
  conforms: false
  evidence: No Idempotency-Key header and no idempotency language in the contract or documentation across 271 write
    operations.
- id: rfc8594-sunset
  conforms: false
  evidence: 'No Sunset or Deprecation response header is declared on any of the 16 operations marked deprecated:
    true.'
- id: rfc9727-api-catalog
  conforms: true
  evidence: https://techdocs.akamai.com/linode-api/.well-known/api-catalog returned 200 application/linkset+json
    on 2026-09-17 with 62 service-desc entries pointing at first-party OpenAPI documents.
- id: llms-txt
  conforms: true
  evidence: https://techdocs.akamai.com/linode-api/llms.txt returned 200 text/plain on 2026-09-17, and every documentation
    page answers to a .md suffix.
- id: s3-api-compatible
  conforms: true
  evidence: Linode Object Storage is published as S3-compatible; the Linode API exposes bucket, key, endpoint and
    quota management (get-object-storage-endpoints, post-object-storage-keys) while object-level access is spoken
    over the S3 protocol to the returned S3 hostname. Not described by this OpenAPI.
  caveat: Compatibility is claimed by the provider; no conformance suite result is published, so this records the
    claim and where the seam is, not a verified pass.
- id: mcp
  conforms: true
  evidence: https://github.com/akamai-developers/akamai-cloud-mcp — official read-only MCP server, 37 tools, stdio
    and self-hosted streamable-http. See mcp/linode-mcp.yml.
- id: a2a
  conforms: false
  evidence: No agent card at /.well-known/agent-card.json or /.well-known/agent.json on api.linode.com, login.linode.com
    or techdocs.akamai.com. techdocs answers 200 with an HTML SPA shell, which is not a card.
- id: asyncapi
  conforms: false
  evidence: 'No event, webhook or streaming surface: the 4.229.1 contract declares no `webhooks` object, and change
    notification is a polling API (get-events, 90-day retention) rather than a push surface.'
domain_standard:
  claimed: null
  note: Infrastructure-as-a-service has no buyer-facing domain contract standard; none is invented to fill the slot.