15trust / 100

Spain Cadastre By Coordinates

by Vextorium in Other

x402 APIFailing, checked 24 min ago

Cadastral parcel reference and address at given coordinates in Spain, to then query its data with catastro-inmueble. Official Catastro data.

POST
https://api.vextorium.com/v1/spain-cadastre-by-coordinates
Price
$0.003
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
24 min ago, next in 34 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 24 min ago: Amount "0.003" is not in atomic token units

Status and outage history · Atom feed

How to call it

POST https://api.vextorium.com/v1/spain-cadastre-by-coordinates

Each call costs $0.003 in USDC on Base, 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.

POST https://api.vextorium.com/v1/spain-cadastre-by-coordinates
content-type: application/json

{
  "lat": 40.453,
  "lon": -3.6883
}

Parameters

ParameterTypeRequiredDescription
latnumberYes
lonnumberYes

Example response

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

{
  "address": "AV CONCHA ESPINA 1 MADRID (MADRID)",
  "lat": 40.453,
  "lon": -3.6883,
  "parcel_reference": "1784401VK4718D",
  "source": "Spanish General Directorate of Cadastre"
}

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.003.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/v1/spain-cadastre-by-coordinates' \
  -H 'content-type: application/json' \
  --data-raw '{"lat":40.453,"lon":-3.6883}'

# 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 - -X POST 'https://api.vextorium.com/v1/spain-cadastre-by-coordinates' \
  -H 'content-type: application/json' \
  --data-raw '{"lat":40.453,"lon":-3.6883}' \
  | 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.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
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.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fv1%2Fspain-cadastre-by-coordinates&method=POST
const res = await pay("https://api.vextorium.com/v1/spain-cadastre-by-coordinates", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "lat": 40.453,
    "lon": -3.6883
  }),
});
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.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://api.vextorium.com/v1/spain-cadastre-by-coordinates",
        json={
            "lat": 40.453,
            "lon": -3.6883,
        },
    )
    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
24 min agoAmount "0.003" is not in atomic token units402107 ms$0.003
5 h agoAmount "0.003" is not in atomic token units402100 ms$0.003
10 h agoAmount "0.003" is not in atomic token units402116 ms$0.003
15 h agoAmount "0.003" is not in atomic token units402278 ms$0.003
19 h agoAmount "0.003" is not in atomic token units40282 ms$0.003
Show 10 older checks
24 h agoAmount "0.003" is not in atomic token units402114 ms$0.003
29 h agoAmount "0.003" is not in atomic token units402187 ms$0.003
33 h agoAmount "0.003" is not in atomic token units402210 ms$0.003
38 h agoAmount "0.003" is not in atomic token units40274 ms$0.003
42 h agoAmount "0.003" is not in atomic token units40278 ms$0.003
46 h agoAmount "0.003" is not in atomic token units402118 ms$0.003
2 days agoAmount "0.003" is not in atomic token units402266 ms$0.003
2 days agoAmount "0.003" is not in atomic token units402106 ms$0.003
2 days agoAmount "0.003" is not in atomic token units40298 ms$0.003
3 days agoAmount "0.003" is not in atomic token units402275 ms$0.003