63trust / 100
Screen Ip
by PayPerScreen in Security & trust
x402 APIPassing, checked 44 min ago
IP risk check (beta)
GET https://api.payperscreen.com/screen-ip
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 50.0%
- Response time
- 176 ms typical, 336 ms slowest 5%
- Last check
- 44 min ago
- Next check
- any minute now
How to call it
# See the payment challenge (nothing is charged)
curl -i -X GET "https://api.payperscreen.com/screen-ip?ip=1.2.3.4"import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.payperscreen.com%2Fscreen-ip
const res = await pay("https://api.payperscreen.com/screen-ip?ip=1.2.3.4");
console.log(await res.json());Example input
{
"ip": "1.2.3.4"
}Example output
{
"flagCount": 0,
"ip": "1.2.3.4",
"redFlag": false,
"riskLevel": "low",
"signals": []
}Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 44 min ago | Passed | 402 | 336 ms | $0.01 |
| 5 h ago | Expected HTTP 402, got 404 | 404 | 490 ms | - |
| 10 h ago | Expected HTTP 402, got 404 | 404 | 401 ms | - |
| 13 h ago | Expected HTTP 402, got 404 | 404 | 742 ms | - |
| 16 h ago | Expected HTTP 402, got 404 | 404 | 510 ms | - |
| 20 h ago | Passed | 402 | 476 ms | $0.01 |
| 23 h ago | Passed | 402 | 176 ms | $0.01 |
| 27 h ago | Passed | 402 | 176 ms | $0.01 |