URL safety check API for phishing links

From $0.01 per successful call · failed calls are never charged · no account needed · Markdown version: /guides/url-safety-check-api.md

Check a URL before an agent opens it: follow redirects, check each host against two phishing blocklists, inspect domain age and trust, and return HTTPS details with named risk signals in one JSON result.

When an agent wants this

URL safety check, scam signals: domain age, redirects and HTTPS $0.01

Check a link before an agent opens or pays it: two phishing blocklists (Phishing.Database, MetaMask) on every host it passes through, where it really leads (each redirect hop, the final URL), the destination domain's age, registrar and trust flags, HTTPS and security headers, and named risk signals (days-old domain, bare IP host, punycode look-alike, user@host trick). Use to vet links in emails, chats and scraped pages, or a payee's website.

Inputs: url (required): The link to check (http or https).

Free first (3 successful calls per caller, no key):

curl "https://glyphcall.com/pack/url-safety?url=http%3A%2F%2Fgithub.com&trial=1"

With a card key from /credits, in a header or, when your client can only fetch a URL, in the URL:

curl -H "Authorization: Bearer adt_…" "https://glyphcall.com/pack/url-safety?url=http%3A%2F%2Fgithub.com"
curl "https://glyphcall.com/pack/url-safety?url=http%3A%2F%2Fgithub.com&api_key=adt_…"

Without a key the same URL answers 402 Payment Required with x402 and MPP terms, so a wallet client pays USDC per call and retries. Over MCP (https://glyphcall.com/mcp) this tool is pack_url_safety.

Example result
{
  "pack": "url-safety",
  "url": "http://github.com/",
  "finalUrl": "https://github.com/",
  "risk": "low",
  "signals": [],
  "blocklist": {
    "listed": false,
    "hosts": [
      {
        "host": "github.com",
        "listed": false,
        "matchedOn": null,
        "sources": [],
        "lookalikeOf": null
      }
    ],
    "listDate": "2026-11-18"
  },
  "redirects": {
    "count": 1,
    "hosts": [
      "github.com"
    ],
    "hops": [
      {
        "url": "http://github.com/",
        "status": 301
      }
    ]
  },
  "domain": {
    "domain": "github.com",
    "trust": "high",
    "ageDays": 6600,
    "registrar": "MarkMonitor Inc."
  },
  "security": {
    "https": true,
    "score": 80,
    "grade": "B"
  },
  "failed": {}
}

Tool page, inputs and limits

Phishing check: is this domain or link safe $0.002

Phishing check: is this domain or link safe? Without opening it, looks the host and its parent domains up in two public phishing blocklists (Phishing.Database active phishing domains, about 390,000; MetaMask eth-phishing-detect, about 120,000 crypto scam domains), flags look-alikes of brands MetaMask watches, and returns block, warn or not_listed with the source and list date. Use before an agent opens, signs or pays at a URL.

Inputs: url (required): The link or domain to check (https://… or example.com); it is never requested.

Free first (3 successful calls per caller, no key):

curl "https://glyphcall.com/phishing/check?url=https%3A%2F%2Fgithub.com&trial=1"

With a card key from /credits, in a header or, when your client can only fetch a URL, in the URL:

curl -H "Authorization: Bearer adt_…" "https://glyphcall.com/phishing/check?url=https%3A%2F%2Fgithub.com"
curl "https://glyphcall.com/phishing/check?url=https%3A%2F%2Fgithub.com&api_key=adt_…"

Without a key the same URL answers 402 Payment Required with x402 and MPP terms, so a wallet client pays USDC per call and retries. Over MCP (https://glyphcall.com/mcp) this tool is phishing_check.

Example result
{
  "url": "https://github.com",
  "domain": "github.com",
  "verdict": "not_listed",
  "listed": false,
  "matchedOn": null,
  "sources": [],
  "lookalikeOf": null,
  "whitelisted": false,
  "listDate": "2026-11-18",
  "listedDomains": {
    "phishingDatabase": 391546,
    "metamask": 119351,
    "total": 510425
  },
  "note": "Not on either list. A list checks known phishing hosts only; use /pack/url-safety to also follow redirects and read the domain's age.",
  "attribution": "Phishing.Database, https://github.com/Phishing-Database/Phishing.Database (MIT); MetaMask eth-phishing-detect, https://github.com/MetaMask/eth-phishing-detect (DBAD public licence)"
}

Tool page, inputs and limits

Questions

Can I pay in USDC on Solana?

Yes. The live unsigned 402 quote currently offers this call for $0.01 USDC on Solana mainnet. The first unpaid request only returns payment terms; check the amount, network and recipient before your wallet client signs.

Does a low risk result guarantee the site is safe?

No. This is a screening aid, not a guarantee. Review the named signals and the failed field; a source that could not be checked leaves uncertainty.

Do I need the full check for a phishing-list lookup?

No. Use the separate phishing check for a blocklist-only lookup; this $0.01 pack also follows redirects and checks domain and HTTPS signals.

What should I check next?

For a payee or merchant, continue with /check/counterparty ($0.01) or /sanctions/check ($0.009) before sending funds; for a repeated link, reuse this answer instead of paying for the same check twice.

How do I pay?

Each successful call costs the tool's price; failed calls are not charged. The first 3 calls are free. Then pay with card credits from $1 (the key goes in an Authorization header or as api_key= in the URL) or per call in USDC over x402 or MPP. No account is needed.