73trust / 100

Reverse Geocode

by address.agentic-jp.com in Weather & location

x402 APIPassing, checked 2 h ago

Reverse-geocode WGS84 lat/lng coordinates within Japan to a normalized Japanese (JP) address with structured components. Use to label a GPS fix, a map pin, or a photo location with a human-readable address.

POST https://address.agentic-jp.com/reverse-geocode

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
960 ms typical, 1.0 s slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://address.agentic-jp.com/reverse-geocode

Each call costs $0.005 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://address.agentic-jp.com/reverse-geocode
content-type: application/json

{
  "lat": 35.6739,
  "lng": 139.7449
}

Parameters

ParameterTypeRequiredDescription
latnumberYesLatitude within Japan (20–46)
lngnumberYesLongitude within Japan (122–154)

Example response

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

{
  "address": "東京都千代田区永田町1-7-1",
  "confidence": 0.92
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://address.agentic-jp.com/reverse-geocode' \
  -H 'content-type: application/json' \
  --data-raw '{"lat":35.6739,"lng":139.7449}'

# 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://address.agentic-jp.com/reverse-geocode' \
  -H 'content-type: application/json' \
  --data-raw '{"lat":35.6739,"lng":139.7449}' \
  | 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Faddress.agentic-jp.com%2Freverse-geocode&method=POST
const res = await pay("https://address.agentic-jp.com/reverse-geocode", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "lat": 35.6739,
    "lng": 139.7449
  }),
});
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://address.agentic-jp.com/reverse-geocode",
        json={
            "lat": 35.6739,
            "lng": 139.7449,
        },
    )
    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
2 h agoPassed4021.0 s$0.005
6 h agoPassed402999 ms$0.005
10 h agoPassed402956 ms$0.005
14 h agoPassed402902 ms$0.005
18 h agoPassed402973 ms$0.005
22 h agoPassed402875 ms$0.005
25 h agoPassed402968 ms$0.005
29 h agoPassed402938 ms$0.005
33 h agoPassed402969 ms$0.005
37 h agoPassed402960 ms$0.005
40 h agoPassed402950 ms$0.005
44 h agoPassed402912 ms$0.005
47 h agoPassed4021.1 s$0.005
2 days agoPassed4021.0 s$0.005
2 days agoPassed402945 ms$0.005