13trust / 100

Data Pitfalls

by thepocketoperator.com in Other

x402 APIFailing, checked 8 h ago

One Regelkartan pitfall row by id (GDPR, AI Act, ISO): rule, law, wrong, right; en + sv. Same data is free at thepocketoperator.com/pitfalls.json; you pay for the per-row API

GET
https://thepocketoperator.com/x402-test/data/pitfalls/:id
Price
$0.001
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
8 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 8 h ago: Expected HTTP 402, got 404

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://thepocketoperator.com/x402-test/data/pitfalls/:id

Each call costs $0.001 in USDC on Base Sepolia, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://thepocketoperator.com/x402-test/data/pitfalls/:id

Example response

The provider's example. We can't check it without paying.

{
  "id": "art28-01",
  "law": "GDPR Art 28",
  "license": "CC BY 4.0, Scandinavian Communication AB",
  "paid": true,
  "right_en": "Only tools with a signed data processing agreement (Art 28(3)) are on the approved list.",
  "rule": "art28",
  "source": "https://thepocketoperator.com/pitfalls-examples.html",
  "tag_en": "No processor agreement",
  "wrong_en": "The sales team feeds a CRM export through a free AI summariser with no processor agreement."
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://thepocketoperator.com/x402-test/data/pitfalls/:id'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://thepocketoperator.com/x402-test/data/pitfalls/:id' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fthepocketoperator.com%2Fx402-test%2Fdata%2Fpitfalls%2F%3Aid
const res = await pay("https://thepocketoperator.com/x402-test/data/pitfalls/:id");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://thepocketoperator.com/x402-test/data/pitfalls/:id")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
8 h agoExpected HTTP 402, got 404404214 ms-
16 h agoExpected HTTP 402, got 404404209 ms-
24 h agoExpected HTTP 402, got 404404204 ms-
33 h agoExpected HTTP 402, got 404404200 ms-
41 h agoExpected HTTP 402, got 404404290 ms-
Show 10 older checks
2 days agoExpected HTTP 402, got 404404178 ms-
2 days agoExpected HTTP 402, got 404404178 ms-
3 days agoExpected HTTP 402, got 404404235 ms-
3 days agoExpected HTTP 402, got 404404149 ms-
3 days agoExpected HTTP 402, got 404404176 ms-
4 days agoExpected HTTP 402, got 404404276 ms-
4 days agoExpected HTTP 402, got 404404223 ms-
4 days agoExpected HTTP 402, got 404404142 ms-
4 days agoExpected HTTP 402, got 404404298 ms-
5 days agoExpected HTTP 402, got 404404231 ms-