Geo Convert
by Sift Web Tools in Documents & files
Convert and reproject map files (GeoJSON, shapefile, CSV, GPX, KML). Spatial file in, spatial file out: reads GeoJSON, zipped shapefile, CSV, GPX or KML and writes GeoJSON, CSV, WKT or zipped shapefile in any EPSG/PROJ/WKT system. Always longitude/easting first, reports the transformation and its accuracy in metres, and refuses data outside the target's area of use (spotting swapped lat/lon).
https://sift.srv1996466.hstgr.cloud/v1/geo/convert- Price
- $0.02
- per call in USDC
- Uptime
- 96.2%
- last 30 days
- Response time
- 148 ms
- 280 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://sift.srv1996466.hstgr.cloud/v1/geo/convert
Each call costs $0.02 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.
GET https://sift.srv1996466.hstgr.cloud/v1/geo/convert?target_crs=EPSG%3A3857&to=geojson&url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fpoints.geojsonParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
source_crs | string | No | Override the source system |
target_crs | string | Yes | Target system, e.g. EPSG:27700 |
to | string | Yes | geojson, csv, wkt or shapefile |
url | string | Yes | Spatial file URL |
Example response
The listing has no example response.
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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://sift.srv1996466.hstgr.cloud/v1/geo/convert?target_crs=EPSG%3A3857&to=geojson&url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fpoints.geojson'
# 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://sift.srv1996466.hstgr.cloud/v1/geo/convert?target_crs=EPSG%3A3857&to=geojson&url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fpoints.geojson' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fv1%2Fgeo%2Fconvert
const res = await pay("https://sift.srv1996466.hstgr.cloud/v1/geo/convert?target_crs=EPSG%3A3857&to=geojson&url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fpoints.geojson");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://sift.srv1996466.hstgr.cloud/v1/geo/convert?target_crs=EPSG%3A3857&to=geojson&url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fpoints.geojson")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 45 ms | $0.02 |
| 8 h ago | Passed | 402 | 145 ms | $0.02 |
| 12 h ago | Passed | 402 | 149 ms | $0.02 |
| 16 h ago | Passed | 402 | 141 ms | $0.02 |
| 21 h ago | Passed | 402 | 280 ms | $0.02 |
Show 10 older checks
| 25 h ago | Passed | 402 | 220 ms | $0.02 |
| 29 h ago | Passed | 402 | 148 ms | $0.02 |
| 33 h ago | Passed | 402 | 145 ms | $0.02 |
| 37 h ago | Passed | 402 | 156 ms | $0.02 |
| 41 h ago | Passed | 402 | 162 ms | $0.02 |
| 45 h ago | Passed | 402 | 191 ms | $0.02 |
| 2 days ago | Passed | 402 | 137 ms | $0.02 |
| 2 days ago | Passed | 402 | 168 ms | $0.02 |
| 2 days ago | Passed | 402 | 221 ms | $0.02 |
| 3 days ago | Passed | 402 | 146 ms | $0.02 |