IP Info API
Reverse DNS (PTR) and network ownership for an IP address or a domain.
- Endpoint
POST /v1/ip-info- Price
- $0.002 per call
- Family
- Domain, DNS & network
- Docs
- /docs/ip-info
01When to use it
- A reverse lookup needs the network, and the ownership data is a versioned dataset an agent does not carry. It is what you run over a list of addresses from a log.
When not to use it
- The destination needs more than 5 s to answer: the call ends with upstream_timeout (424).
- The destination is on a private or local network: the network guard refuses it with blocked_target (403).
02Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| ip | string | no | A public IPv4 or IPv6 address to look up; private, loopback and reserved addresses are refused. Give exactly one of ip or domain. |
| domain | string | no | A public fully qualified domain name, resolved to its first address, which is then looked up; the call is refused if the name resolves to any private address. Give exactly one of ip or domain. |
03Limits
| Limit | Value |
|---|---|
| Size cap | 2 MB (2,097,152 bytes) |
| Timeout | 5 s |
04Example
The published example of ip-info, verbatim: the request body and the response it returns.
Request
POST /v1/ip-info
content-type: application/json
payment-signature: <base64 x402 payload>
{
"ip": "8.8.8.8"
}Response
200 OK
payment-response: <base64 settlement receipt>
{
"query": "8.8.8.8",
"ip": "8.8.8.8",
"ptr": "dns.google",
"asn": 15169,
"asn_org": "GOOGLE",
"country": "US"
}This example is illustrative: it shows the exact shape the handler returns, but it was not produced by a reproducible call, because the real answer depends on live network data that changes over time.
| Response field | Type | In the example |
|---|---|---|
| query | string | "8.8.8.8" |
| ip | string | "8.8.8.8" |
| ptr | string | "dns.google" |
| asn | number | 15169 |
| asn_org | string | "GOOGLE" |
| country | string | "US" |
05Call it from code
JavaScript
// ip-info: $0.002 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'
const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)
const body = {
"ip": "8.8.8.8"
}
const res = await fetchWithPayment('https://grist.tools/v1/ip-info', {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)Python
# ip-info: $0.002 per call, paid in USD Coin on eip155:8453 via x402
# Install: pip install "x402[requests,evm]>=2.24,<3"
# The session reads the 402 (payment-required), signs and retries with payment-signature.
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http import decode_payment_response_header
from x402.http.clients.requests import x402_requests
from x402.mechanisms.evm.exact import register_exact_evm_client
from x402.mechanisms.evm.signers import EthAccountSigner
account = Account.from_key(os.environ["EVM_PRIVATE_KEY"])
client = x402ClientSync()
register_exact_evm_client(client, EthAccountSigner(account), networks="eip155:8453")
session = x402_requests(client)
payload = {
"ip": "8.8.8.8"
}
res = session.post("https://grist.tools/v1/ip-info", json=payload)
print(res.status_code, res.json())
settle = res.headers.get("payment-response")
if settle:
print(decode_payment_response_header(settle).transaction)curl
# ip-info: $0.002 per call, paid in USD Coin on eip155:8453 via x402
# 1. Unpaid call: HTTP 402, the requirements in the payment-required header (base64 JSON) and in the body.
curl -i -X POST 'https://grist.tools/v1/ip-info' -H 'content-type: application/json' -d '{"ip":"8.8.8.8"}'
# 2. Same call with the signed payment (an EIP-3009 authorization, EIP-712 signed: it cannot be
# typed by hand). x-payment is accepted as the v1 alternative. HTTP 200 carries payment-response.
curl -i -X POST 'https://grist.tools/v1/ip-info' -H 'content-type: application/json' -H 'payment-signature: <base64 x402 payload>' -d '{"ip":"8.8.8.8"}'06Errors
| Code | HTTP | For this service |
|---|---|---|
| invalid_input | 400 | The body does not match the schema; its fields are ip and domain. |
| blocked_target | 403 | |
| unreachable_target | 424 | |
| upstream_timeout | 424 | |
| internal | 500 |
Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.
When each code is raised, and what it means for payment: /docs/ip-info.
07Questions
- How much does a ip-info call cost?
- $0.002 per call, paid in USDC on Base via x402, with no account and no API key.
- What does ip-info return?
- A JSON object with 6 top-level fields: query, ip, ptr, asn, asn_org and country. The example on this page is illustrative, not a recorded call.
- What happens when a ip-info call fails?
- The tool answers with a typed JSON error from the errors table. Payment is settled only after the tool has produced its result; a call that fails inside the tool is never settled. A 503 upstream_unavailable can follow a settled call; the x402 payments guide covers it, 429, 402 and an uncertain 500.