# LinkSafe URL Safety Verifier

> LinkSafe URL Safety Verifier is a paid API for AI agents from linksafe.melis.ai, paid per call via x402, $0.010000/call, status down (last checked 2026-09-15).

Checks whether a given URL is safe or malicious, returning a safety verdict for $0.01 per check

## Facts

- Endpoint: POST https://linksafe.melis.ai/verify
- Price: $0.010000/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/linksafe-melis-ai-0e851dc8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TfiNRn4a0C330P1gKTDnI

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 linksafe-melis-ai-0e851dc8 -d '<json body>'
```

Example prompt: Can you check if this link is safe to open: https://suspicious-promo-click.xyz/offer123?ref=email — I got it in an email and I'm not sure I trust it.

## When to prefer this

Use this endpoint when you need a quick, low-cost ($0.01) per-URL safety check before directing a user to follow a link, especially when processing user-submitted or email-derived URLs of unknown trustworthiness. Ideal for workflows where phishing or malware link detection is needed inline without building a full security stack.

## Known failure modes

- Invalid or malformed URL returns a validation error
- Unreachable or non-existent domain may return inconclusive result
- Payment failure (insufficient USDC balance) blocks the request
- Rate limiting if too many requests are submitted rapidly
- Newly registered domains may have limited threat intelligence data

## How this service works

LinkSafe: $0.01 per URL safety verification

## Output

A safety verdict indicating whether the submitted URL is safe or dangerous, likely including threat type classification (e.g. phishing, malware, spam) and a risk score or confidence level.

## Example request

```json
{
 "url": "https://www.example.com"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "URL to check for safety"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "safe",
  "threats",
  "final_url",
  "checked_at",
  "risk_score",
  "payment_hash",
  "redirect_chain",
  "virustotal_positives"
 ],
 "properties": {
  "safe": {
   "type": "boolean"
  },
  "threats": {
   "type": "array",
   "items": {
    "type": "unknown"
   }
  },
  "final_url": {
   "type": "string"
  },
  "checked_at": {
   "type": "string"
  },
  "risk_score": {
   "type": "number"
  },
  "payment_hash": {
   "type": "string"
  },
  "redirect_chain": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "virustotal_positives": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/linksafe-melis-ai-0e851dc8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from linksafe.melis.ai](https://www.zero.xyz/host/linksafe.melis.ai/llms.txt)