pleamo

developers

Build on pleamo.

Call pleamo's scam and phishing detection straight from your code, or wire it into an AI agent over MCP. One API key, two ways in. Verdicts in a few hundred milliseconds.

create an API key

1 · Get an API key

Sign in, open API keys on your dashboard, and create one. It looks like pk_live_… and is shown once, so copy it. Keys are revocable and draw from your account's shared quota.

2 · Check a URL

Send the URL you want judged as a Bearer token request. We only ever read the domain and path, never query strings.

curl -X POST https://dash.pleamo.app/api/check \
  -H "authorization: Bearer pk_live_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://paypa1-secure-login.tk/verify"}'

Response:

{
  "verdict": "dangerous",      // safe | suspicious | dangerous | unknown
  "severity": 92,              // 0-100
  "reason": "Looks like a fake 'paypal' address (typosquat).",
  "source": "heuristics",      // allowlist | cache | ourdb | safebrowsing | heuristics | ai
  "cached": false,
  "smartLeft": 149             // AI checks left in your daily quota
}

3 · Or use MCP

pleamo speaks the Model Context Protocol, so agents (Claude, and other MCP clients) can call it as a tool. There are two ways:

Remote endpoint

A stateless Streamable-HTTP endpoint. Point any remote-MCP client at it with your key as the bearer:

POST https://dash.pleamo.app/api/mcp
authorization: Bearer pk_live_YOUR_KEY

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

Tools: check_url (judge a URL) and report_false_positive (flag a wrongly-blocked domain).

Local server (Claude Desktop)

Run the stdio MCP server and add it to your client's config with your key:

{
  "mcpServers": {
    "pleamo": {
      "command": "npx",
      "args": ["-y", "pleamo-mcp"],
      "env": { "PLEAMO_API_KEY": "pk_live_YOUR_KEY" }
    }
  }
}

Limits & fair use

create an API key →