# RelayShield NHI Exposure Scanner

> RelayShield NHI Exposure Scanner is a paid API for AI agents from api.relayshield.net, paid per call via x402, $0.4/call, status unknown (last checked 2026-10-12).

Scans a domain for non-human identity (NHI) credential exposures such as leaked API keys, tokens, or service account secrets

## Facts

- Endpoint: POST https://api.relayshield.net/v1/payg/nhi-exposure?utm_source=zero.xyz
- Price: $0.4/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-nhi-exposure-scanner-9e8cbd24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yVrDjS_LnDPEyvYjl9IuV

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 relayshield-nhi-exposure-scanner-9e8cbd24 -d '<json body>'
```

Example prompt: Can you scan acmecorp.com for any exposed non-human identity credentials — things like leaked API keys, service account tokens, or machine secrets — and tell me what you find and how severe it is?

## When to prefer this

Use this endpoint when you need to programmatically check whether a specific domain has publicly exposed non-human identity credentials such as API keys, tokens, or service account secrets. Prefer this over general vulnerability scanners when your focus is specifically on NHI/machine identity exposure rather than web application vulnerabilities, network misconfigurations, or human credential leaks.

## Known failure modes

- Invalid or unresolvable domain returns an error or zero findings
- Rate limiting may occur with repeated rapid calls to the same domain
- Network timeouts if the target domain is slow to respond
- False negatives possible if exposed credentials are not publicly indexed
- Missing or malformed request body causes a 400-level error

## How this service works

RelayShield Landing Site

## Output

Returns a JSON object indicating whether any NHI credential exposures were found (found: boolean), an array of findings with details, the number of domains checked, and the highest severity level among findings (null if none found).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Your own domain"
  },
  "vendor_domains": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Optional: vendor/supply-chain domains, up to 10"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "found": false,
   "findings": [],
   "domains_checked": 1,
   "highest_severity": null
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-nhi-exposure-scanner-9e8cbd24/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.relayshield.net](https://www.zero.xyz/host/api.relayshield.net/llms.txt)