# Jarvis Domain Verification

> Jarvis Domain Verification is a paid API for AI agents from jarvis-problem-intake.naijunyu.chatgpt.site, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Verifies whether a candidate public domain matches a given company name, returning a confidence-scored verdict with evidence for downstream enrichment.

## Facts

- Endpoint: POST https://jarvis-problem-intake.naijunyu.chatgpt.site/b2b/domain-verify
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jarvis-domain-verification-de96307d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FBlIjGiZVLGRkodv45x24

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 jarvis-domain-verification-de96307d -d '<json body>'
```

Example prompt: Can you verify whether 'runwayml.com' is actually the official domain for the company Runway — I want to confirm the canonical domain before we enrich our CRM records with it.

## When to prefer this

Use this endpoint when you need a high-confidence, evidence-backed determination that a specific domain belongs to a specific company — especially before using that domain in automated enrichment, outreach, or deal-scoring pipelines. Prefer this over generic WHOIS lookups or simple Google searches when you need a structured verdict with redirect resolution, signal provenance, and a machine-readable safe-for-enrichment flag.

## Known failure modes

- Company name too ambiguous — multiple companies share the name, resulting in low confidence or UNCERTAIN verdict
- Candidate domain is unreachable or returns non-200 status — evidence array may be sparse
- Redirect loops or misconfigured DNS prevent canonical domain resolution
- No public web signals link the domain to the company, resulting in NO_MATCH with low confidence
- Context field omitted for niche industries, reducing accuracy of matching heuristics

## How this service works

AI UGC, AI Ads, and short-form deal execution gated on verified gross profit.

## Output

A JSON object containing a MATCH/NO_MATCH/UNCERTAIN verdict, a confidence score (0–1), the canonical domain after redirect resolution, the domain redirected from (if applicable), an array of evidence signals each with a URL, value, signal polarity, and source, a timestamp, and a boolean flag indicating whether the domain is safe for downstream enrichment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "context": {
   "type": "string",
   "maxLength": 500,
   "description": "Optional industry or identity context"
  },
  "company_name": {
   "type": "string",
   "maxLength": 160,
   "minLength": 2,
   "description": "Target company name"
  },
  "candidate_domain": {
   "type": "string",
   "description": "Candidate public domain to verify"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "verdict": "MATCH",
  "evidence": [
   {
    "url": "https://runwayml.com/",
    "value": "301 → runway.com",
    "signal": "POSITIVE",
    "source": "redirect"
   }
  ],
  "checked_at": "2026-08-29T00:00:00.000Z",
  "confidence": 0.98,
  "redirected_from": "runwayml.com",
  "canonical_domain": "runway.com",
  "safe_for_downstream_enrichment": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jarvis-domain-verification-de96307d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jarvis-problem-intake.naijunyu.chatgpt.site](https://www.zero.xyz/host/jarvis-problem-intake.naijunyu.chatgpt.site/llms.txt)