# RelayShield Session Risk Check

> RelayShield Session Risk Check is a paid API for AI agents from api.relayshield.net, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-10).

Checks whether a given email address is associated with known risky or fraudulent sessions, returning severity and session details

## Facts

- Endpoint: POST https://api.relayshield.net/v1/payg/session-risk?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-session-risk-check-038fafc6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SIub46Gp3BK100hvAhKcA

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-session-risk-check-038fafc6 -d '<json body>'
```

Example prompt: Can you check RelayShield to see if user@example.com has any risky or flagged sessions, and tell me the highest severity level found?

## When to prefer this

Use this endpoint when you need to assess whether a specific email address is tied to known risky or fraudulent sessions before allowing access, onboarding a new user, or investigating a suspicious account. Prefer this over generic reputation checks when session-level risk granularity and severity scoring are needed.

## Known failure modes

- Invalid or malformed email returns a validation error
- Email not found in database returns found:false with empty sessions array and null severity
- Service unavailable or timeout results in a non-200 response
- Payment failure via x402 protocol prevents request from completing
- Rate limiting may occur for high-volume queries

## How this service works

RelayShield Landing Site

## Output

Returns a JSON object with a boolean 'found' flag indicating whether risky sessions exist for the email, an array of session objects, a session count, and the highest severity level detected (or null if none found).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "description": "Email address to check for active session/AiTM exposure"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "email": "user@example.com",
   "found": false,
   "sessions": [],
   "session_count": 0,
   "highest_severity": null
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-session-risk-check-038fafc6/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)
