specification: API Commons Conformance
specificationVersion: '0.1'
provider: Campbell's
providerId: campbells
generated: '2026-09-05'
method: probed
source: >-
  Live observation of https://www.campbells.com/wp-json/ responses and of the
  JSON-LD embedded in https://www.campbells.com/recipes/creamy-lemon-chicken/,
  2026-09-05. Campbell's makes no conformance or compliance claim anywhere this
  pipeline could find, so every entry below is asserted from what was measured.
description: >-
  Cross-cutting standards conformance for the Campbell's content and search
  APIs. The API layer conforms to almost nothing by way of published standards —
  it is WordPress core convention. The one real standards signature Campbell's
  does carry is schema.org, and it sits on the web pages rather than in the API.
conformance:
  - id: schema.org
    conforms: true
    evidence: >-
      Every recipe page embeds a schema.org Recipe node in JSON-LD
      (@context https://schema.org) carrying name, description, image, author,
      recipeIngredient, recipeInstructions, recipeCategory, recipeYield and
      ISO-8601 prepTime/cookTime/totalTime, plus a NutritionInformation node
      with calories, fat, saturatedFat, transFat, cholesterol, sodium,
      carbohydrate, fiber, sugar and protein content. Verified at
      https://www.campbells.com/recipes/creamy-lemon-chicken/ (HTTP 200).
    scope: web pages, not the API
    note: >-
      This is the domain-standard signature for the recipe/food market and it is
      genuine and machine-readable — but it is served in page markup, not in the
      API contract or in any API response. An agent gets structured Recipe and
      NutritionInformation by parsing the HTML, not by calling /wp-json.
  - id: schema.org-org
    conforms: true
    evidence: >-
      Organization, WebSite, WebPage, BreadcrumbList, SearchAction and
      ReadAction nodes are published in the same JSON-LD graph via Yoast SEO.
  - id: llms.txt
    conforms: true
    evidence: >-
      https://www.campbells.com/llms.txt returns HTTP 200, 2428 bytes, generated
      by Yoast SEO v28.2 — an index of pages, products, recipes and recipe
      collections. Saved verbatim to llms/campbells-llms.txt.
  - id: pagination
    conforms: true
    evidence: >-
      page / per_page / offset query parameters with X-WP-Total,
      X-WP-TotalPages and RFC 8288 Link rel="next" response headers, all named
      in access-control-expose-headers. Observed on GET /wp/v2/recipe.
  - id: rfc9457
    conforms: false
    evidence: >-
      Errors use the WordPress {code, message, data.status} envelope with
      Content-Type application/json; charset=UTF-8. No type URI, no
      application/problem+json. See errors/campbells-problem-types.yml.
  - id: idempotency
    conforms: false
    evidence: No Idempotency-Key or equivalent mechanism on any mutating route.
  - id: oauth2
    conforms: false
    evidence: >-
      No oauth2 scheme registered; /.well-known/oauth-authorization-server 404s
      on every host.
  - id: oidc
    conforms: false
    evidence: /.well-known/openid-configuration returns 404 on every host.
  - id: rfc9116
    conforms: false
    evidence: /.well-known/security.txt returns 404 on every host.
  - id: rfc8594
    conforms: false
    evidence: No Sunset or Deprecation header returned on any response.
  - id: openapi
    conforms: false
    evidence: >-
      No OpenAPI or Swagger document is served on any host. See
      discovery/campbells-discovery.yml for the full probe list.
  - id: json-schema
    conforms: true
    evidence: >-
      WordPress serves a JSON Schema document per resource on an OPTIONS
      request; four were harvested verbatim into json-schema/.
    note: >-
      Platform behaviour adopted by Campbell's, not a schema Campbell's authored
      or publishes as a developer artifact.
domain_standard:
  market: food / consumer packaged goods / recipe content
  standard: schema.org Recipe + NutritionInformation
  declared_in_contract: false
  declared_in_pages: true
  note: >-
    The Kin Score regulatory-regime map carries no regime for food or consumer
    packaged goods, so there is no sector standards[] shortlist to probe against
    here. schema.org Recipe is the de-facto interchange standard for this market
    and Campbell's does publish it — but on the page, not in the API, so it is
    recorded without a contract-level conformance claim.
compliance:
  certifications_published: []
  note: >-
    No trust centre, no SOC 2 / ISO 27001 / PCI / HIPAA / FedRAMP claim, and no
    security or compliance page was found on either domain. No Compliance
    pointer is emitted.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com