URL Phishing Reputation

security

Serving

Check a URL for phishing signs without fetching it: raw IP hosts, punycode, user@host, credential words in the host, very long hosts and deep subdomains. The verdict is suspicious or unknown, never clean, because no threat database is consulted; the response says what ran. POST /v1/reputation with {url}. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/url-phishing-reputation/v1/reputation
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/url-phishing-reputation/v1/reputation \
  -H 'content-type: application/json' \
  -d '{"url":"string"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods URL Phishing Reputation accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/reputation`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "The body of POST /v1/reputation.",
  "properties": {
    "url": {
      "type": "string",
      "description": "The URL to check (http or https). It is not fetched."
    }
  },
  "required": [
    "url"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/reputation, a JSON object with url, host, verdict (malicious, suspicious, clean or unknown), heuristics, threat_matches, checked_sources (each source and whether it ran) and verdict_scope. A bad request answers 400 with an `error` string."
}