13trust / 100

India Pincode

by Saylor Innovations Data Desk in Developer tools

x402 APIFailing, checked 15 min ago

India PIN code lookup - district, state, region and the post offices for any 6-digit pincode

GET
https://saylorinnovations.com/api/india/pincode/:pin
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
15 min ago, next in 43 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 15 min ago: Expected HTTP 402, got 404

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

How to call it

GET https://saylorinnovations.com/api/india/pincode/:pin

Each call costs $0.01 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

The listing has no example input.

GET https://saylorinnovations.com/api/india/pincode/:pin

Example response

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

Example response, 28 lines
{
  "circle": "Delhi",
  "count": 21,
  "country": "India",
  "district": "Central Delhi",
  "division": "New Delhi Central",
  "pincode": "110001",
  "post_offices": [
    {
      "delivery": "Non-Delivery",
      "name": "Baroda House",
      "type": "Sub Post Office"
    },
    {
      "delivery": "Non-Delivery",
      "name": "Bengali Market",
      "type": "Sub Post Office"
    },
    {
      "delivery": "Non-Delivery",
      "name": "Bhagat Singh Market",
      "type": "Sub Post Office"
    }
  ],
  "region": "Delhi",
  "source": "India Post via postalpincode.in",
  "state": "Delhi"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/india/pincode/:pin'

# 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://saylorinnovations.com/api/india/pincode/:pin' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Findia%2Fpincode%2F%3Apin
const res = await pay("https://saylorinnovations.com/api/india/pincode/:pin");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://saylorinnovations.com/api/india/pincode/:pin")
    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
15 min agoExpected HTTP 402, got 404404396 ms-
5 h agoExpected HTTP 402, got 404404406 ms-
10 h agoExpected HTTP 402, got 404404232 ms-
14 h agoExpected HTTP 402, got 404404210 ms-