# Sna4an BIN/IP Lookup API

> Sna4an BIN/IP Lookup API is a paid API for AI agents from sna4an-misc.vercel.app, paid per call via x402, $0.175/call, status unknown (last checked 2026-10-23).

Looks up bank identification number (BIN) and/or IP address intelligence data via a RapidAPI-backed sub-endpoint

## Facts

- Endpoint: POST https://sna4an-misc.vercel.app/api/bin-ip?utm_source=zero.xyz
- Price: $0.175/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sna4an-bin-ip-lookup-api-7c5207ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LwrXqUpn4cYVlyL2u4tX9

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability sna4an-bin-ip-lookup-api-7c5207ab -d '<json body>'
```

Example prompt: Can you look up the BIN 424242 for me and tell me what bank issued it, what card network it belongs to, and whether it's a debit or credit card?

## When to prefer this

Use this endpoint when you need quick BIN or IP intelligence lookups and are already working within an x402 micropayment context. It is a good fit for fraud detection pipelines, payment form validation, or IP-based user segmentation. Prefer alternatives if you need bulk batch processing or require SLA guarantees from a dedicated provider.

## Known failure modes

- Invalid BIN or IP address returns an error or empty result
- Unknown or unrecognized sub-endpoint path causes routing failure
- Payment not processed correctly results in 402 response
- RapidAPI upstream timeout or rate limit causes 5xx error
- Malformed query parameters return validation errors

## How this service works

News, AI, SEO, e-commerce, and utility APIs

## Output

Returns a JSON object with card issuer details (bank name, card brand, card type, country of issuance) for BIN lookups, or geolocation and ISP details for IP address lookups, depending on the sub-endpoint path used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "path": {
   "type": "string",
   "description": "RapidAPI sub-endpoint path"
  },
  "params": {
   "type": "object",
   "description": "Query parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sna4an-bin-ip-lookup-api-7c5207ab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-misc.vercel.app](https://www.zero.xyz/host/sna4an-misc.vercel.app/llms.txt)