# www vs Apex Domain Canonical Check

> www vs Apex Domain Canonical Check is a paid API for AI agents from intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches both the www and apex (root) variants of a domain over HTTP and HTTPS, reporting which is canonical, whether redirects are in place, and any inconsistencies like duplicate content or missing HTTPS upgrades.

## Facts

- Endpoint: GET https://intel.rallylive.ca/monitor/www-vs-apex
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/www-vs-apex-domain-canonical-check-e6ed1e3d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gSvhuenOk_Jphgtsiid5p

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability www-vs-apex-domain-canonical-check-e6ed1e3d
```

Example prompt: Can you check whether example.com and www.example.com are properly set up — which one is canonical, does the other redirect to it, and do both http:// versions upgrade to https?

## When to prefer this

Use this endpoint when you need to audit or verify the canonical URL setup between www and apex variants of a domain, especially for SEO hygiene, redirect chain correctness, or HTTPS upgrade compliance. Prefer this over a generic URL status check when the specific www-vs-apex relationship and redirect consistency is the concern rather than simple uptime.

## Known failure modes

- Domain does not exist or DNS resolution fails — both variants return errors
- Target server blocks automated requests — status may appear as 4xx or timeout
- Both hosts return 200 without redirect — flagged as duplicate content inconsistency
- One host is unreachable while the other is healthy — reported as partial failure
- Domain input missing or malformed — request rejected with validation error

## How this service works

www vs apex check: fetches both https://domain/ and https://www.domain/ (and the http:// variants), reports which one is canonical, whether the other redirects to it, status of each, and any inconsistencies such as one host failing, both serving 200 without redirect (duplicate content), or an http variant not upgrading. $0.01 per domain.

## Output

Returns which host (www or apex) is canonical, the HTTP status of each of the four variants (https://domain, https://www.domain, http://domain, http://www.domain), whether non-canonical variants redirect to the canonical one, and flags for inconsistencies such as both hosts returning 200 without a redirect (duplicate content), a host being unreachable, or http variants not upgrading to https.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/www-vs-apex-domain-canonical-check-e6ed1e3d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.rallylive.ca](https://www.zero.xyz/host/intel.rallylive.ca/llms.txt)