77trust / 100
Point In Polygon
by Point in polygon in Other
x402 APIPassing, checked 45 min ago
Test whether a coordinate falls inside a polygon.
POST
https://geospatial.openverbs.com/v1/point-in-polygon- Price
- $0.002
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 565 ms
- 670 ms slowest 5%
- Last check
- Passed
- 45 min ago, next any minute now
Reliability
All checks passedSome failedAll failedNot checked
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://geospatial.openverbs.com/v1/point-in-polygon
Each call costs $0.002 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://geospatial.openverbs.com/v1/point-in-polygon
content-type: application/json
{
"point": {
"lat": 1,
"lon": 1
},
"polygon": [
{
"lat": 1,
"lon": 1
},
{
"lat": 1,
"lon": 1
},
{
"lat": 1,
"lon": 1
}
]
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
point | object | Yes | The coordinate to test. |
polygon | array of object | Yes | Polygon exterior ring as ordered vertices (auto-closed). |
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.002.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://geospatial.openverbs.com/v1/point-in-polygon' \
-H 'content-type: application/json' \
--data-raw '{"point":{"lat":1,"lon":1},"polygon":[{"lat":1,"lon":1},{"lat":1,"lon":1},{"lat":1,"lon":1}]}'
# 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://geospatial.openverbs.com/v1/point-in-polygon' \
-H 'content-type: application/json' \
--data-raw '{"point":{"lat":1,"lon":1},"polygon":[{"lat":1,"lon":1},{"lat":1,"lon":1},{"lat":1,"lon":1}]}' \
| 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fgeospatial.openverbs.com%2Fv1%2Fpoint-in-polygon&method=POST
const res = await pay("https://geospatial.openverbs.com/v1/point-in-polygon", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"point": {
"lat": 1,
"lon": 1
},
"polygon": [
{
"lat": 1,
"lon": 1
},
{
"lat": 1,
"lon": 1
},
{
"lat": 1,
"lon": 1
}
]
}),
});
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://geospatial.openverbs.com/v1/point-in-polygon",
json={
"point": {
"lat": 1,
"lon": 1,
},
"polygon": [
{
"lat": 1,
"lon": 1,
},
{
"lat": 1,
"lon": 1,
},
{
"lat": 1,
"lon": 1,
},
],
},
)
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 |
|---|---|---|---|---|
| 45 min ago | Passed | 402 | 612 ms | $0.002 |
| 6 h ago | Passed | 402 | 621 ms | $0.002 |
| 10 h ago | Passed | 402 | 572 ms | $0.002 |
| 15 h ago | Passed | 402 | 529 ms | $0.002 |
| 20 h ago | Passed | 402 | 579 ms | $0.002 |
Show 10 older checks
| 25 h ago | Passed | 402 | 565 ms | $0.002 |
| 29 h ago | Passed | 402 | 164 ms | $0.002 |
| 33 h ago | Passed | 402 | 581 ms | $0.002 |
| 37 h ago | Passed | 402 | 213 ms | $0.002 |
| 41 h ago | Passed | 402 | 587 ms | $0.002 |
| 45 h ago | Passed | 402 | 600 ms | $0.002 |
| 2 days ago | Passed | 402 | 549 ms | $0.002 |
| 2 days ago | Passed | 402 | 168 ms | $0.002 |
| 2 days ago | Passed | 402 | 532 ms | $0.002 |
| 3 days ago | Passed | 402 | 721 ms | $0.002 |