# Supplier Risk API

> Supplier Risk API is a paid API for AI agents from supplier-risk-api-production.up.railway.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-16).

Returns a 0-100 stability score, risk tier, and named risk flags for any company domain by analyzing WHOIS, TLS, DNS health, and 30-day news sentiment.

## Facts

- Endpoint: GET https://supplier-risk-api-production.up.railway.app/supplier-risk
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/supplier-risk-api-229ff4ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KEd5lYc7Qjn2OJNfzRLBf

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 supplier-risk-api-229ff4ad
```

Example prompt: Can you run a supplier risk check on stripe.com? I want to see their stability score, risk tier, and any red flags around their domain age, TLS cert, DNS setup, and recent news sentiment before we start paying them.

## When to prefer this

Use this endpoint when you need a fast, multi-signal risk snapshot of an unfamiliar vendor or counterparty domain before a financial transaction, integration, or supplier onboarding — especially when you want WHOIS, TLS, DNS, and news sentiment combined into a single scored result without building your own data pipeline.

## Known failure modes

- Invalid or nonexistent domain returns an error or empty signals
- Domain with no WHOIS record may lack age/expiry subsignal
- Payment not completed (x402) results in 402 response before data is returned
- Newly registered domains may have incomplete DNS/WHOIS data
- News sentiment may be unavailable for obscure or low-profile domains

## How this service works

Supplier and vendor risk score for any company domain. Returns a 0-100 stability score, risk tier, and named risk flags, with subsignals: domain age/expiry (WHOIS), TLS certificate status, DNS health (A/MX/SPF/DMARC), and 30-day news sentiment. Use for supplier due diligence and third-party domain screening before purchasing from, integrating with, or paying an unfamiliar vendor or counterparty. Call GET /supplier-risk?domain=acme.com. JSON response, no API key, $0.15 USDC per request via x402.

## Output

A JSON object with a 0-100 stability score (higher = more stable), a risk tier (low/medium/high/critical), an array of named risk flag strings, and a signals object with per-subsignal detail covering WHOIS (domain age/expiry), SSL/TLS certificate status, DNS health (A/MX/SPF/DMARC records), and 30-day news sentiment.

## 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",
     "required": [
      "domain"
     ],
     "properties": {
      "domain": {
       "type": "string",
       "description": "Company domain to assess (e.g. acme.com)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "flags": {
       "type": "array",
       "items": {
        "type": "string"
       }
      },
      "domain": {
       "type": "string"
      },
      "signals": {
       "type": "object",
       "description": "Per-signal detail: whois, ssl, dns, news"
      },
      "riskTier": {
       "enum": [
        "low",
        "medium",
        "high",
        "critical"
       ],
       "type": "string"
      },
      "riskScore": {
       "type": "number",
       "description": "0-100; higher = more stable"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "meta": {
   "network": "eip155:8453",
   "version": "1.3.7",
   "generatedAt": "2026-07-13T00:00:00.000Z"
  },
  "flags": [
   "domain_under_1_year",
   "no_dmarc_record"
  ],
  "domain": "example-vendor.com",
  "signals": {
   "dns": {
    "data": {
     "hasMx": true,
     "hasSpf": true,
     "hasDmarc": false,
     "resolvesA": true,
     "healthScore": 3
    },
    "status": "ok"
   },
   "ssl": {
    "data": {
     "sslStatus": "valid",
     "hasCertificate": true,
     "daysUntilExpiry": 88
    },
    "status": "ok"
   },
   "news": {
    "data": {
     "articleCount": 4,
     "sentimentLabel": "neutral",
     "sentimentScore": 0.1
    },
    "status": "ok"
   },
   "whois": {
    "data": {
     "ageInDays": 214,
     "expiryRisk": "low",
     "daysUntilExpiry": 151,
     "newlyRegistered": false
    },
    "status": "ok"
   }
  },
  "riskTier": "medium",
  "riskScore": 62
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/supplier-risk-api-229ff4ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from supplier-risk-api-production.up.railway.app](https://www.zero.xyz/host/supplier-risk-api-production.up.railway.app/llms.txt)