# RelayShield SIM Swap Check

> RelayShield SIM Swap Check is a paid API for AI agents from atq6wtkp6k.execute-api.us-east-1.amazonaws.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-14).

Checks whether a given phone number has recently had its SIM swapped, returning the carrier, swap status, and timestamp of the swap event.

## Facts

- Endpoint: POST https://atq6wtkp6k.execute-api.us-east-1.amazonaws.com/prod/v1/payg/sim-swap
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-sim-swap-check-62704794
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zYtHzbW2ZFvxjkMx97bKH

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-sim-swap-check-62704794 -d '<json body>'
```

Example prompt: Check if the phone number +14155551234 has had a SIM swap recently — I need to know the carrier and when the swap happened before I approve this login.

## When to prefer this

Use this endpoint when you need to detect SIM swap fraud before allowing sensitive actions like SMS-based 2FA logins, high-value financial transactions, or account recovery flows. Prefer this over generic identity checks when the specific risk vector is telecom-based SIM porting or swapping.

## Known failure modes

- Phone number not found or not supported — returns error with no swap data
- Invalid phone number format — returns validation error
- Carrier data unavailable for the given number — partial response or error
- Rate limit exceeded — HTTP 429 response
- Insufficient USDC balance for x402 payment — payment failure before check executes

## How this service works

Check whether a phone number has had a SIM swap or carrier port in the last 24 hours via real-time carrier lookup. A recent swap is a strong signal of an active account-takeover attempt targeting SMS-based 2FA. Call before trusting an SMS OTP from this number.

## Output

Returns a JSON object with the queried phone number, the current carrier (e.g. T-Mobile), a boolean indicating whether a SIM swap was detected, the timestamp when the check was performed, and the timestamp of the most recent SIM swap event if one occurred.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "phone": {
   "type": "string",
   "description": "Phone number in E.164 format"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-sim-swap-check-62704794/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atq6wtkp6k.execute-api.us-east-1.amazonaws.com](https://www.zero.xyz/host/atq6wtkp6k.execute-api.us-east-1.amazonaws.com/llms.txt)