# is-ip-aws-bulk

> is-ip-aws-bulk is a paid API for AI agents from ip.intel.rallylive.ca, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-11).

Bulk-checks up to 20 IP addresses in a single call to determine whether each belongs to Amazon Web Services (AWS) infrastructure, returning results in input order with per-item errors and a failure count.

## Facts

- Endpoint: GET https://ip.intel.rallylive.ca/bulk/ip/is/aws?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/is-ip-aws-bulk-f15ebaf3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vf81aaYb4sVbRCE1VFS0V

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 is-ip-aws-bulk-f15ebaf3
```

Example prompt: I have a list of IP addresses — 198.51.100.1, 203.0.113.45, 54.239.28.85, 52.94.76.1, 172.217.14.1 — can you check all of them at once and tell me which ones are AWS IPs?

## When to prefer this

Use this endpoint when you already hold a list of IP addresses (up to 20) and need to determine AWS membership for all of them efficiently in a single $0.10 call rather than paying per-IP for individual lookups. Prefer this over the single-IP endpoint whenever you have 2 or more IPs to check. Choose this over generic IP geolocation or WHOIS endpoints when the specific question is cloud provider identity for AWS specifically, with concurrent processing and ordered results guaranteed.

## Known failure modes

- Batch exceeds 20 IPs — request rejected or truncated
- Individual IPs that are malformed produce per-item errors without failing the entire batch
- Payment failure (x402) blocks the entire call before processing
- Network timeout from edge to DNS/range-check service causes partial or full failure
- IP ranges may lag actual AWS allocation updates, causing transient false negatives

## How this service works

Bulk is ip aws: up to 20 ips in one call, processed concurrently, results in input order with a per-item error field and a failure count. Same answer per item as the single endpoint. Batch enrichment for agents that hold a list. $0.10 per batch.

## Output

Returns an ordered array of results matching the input IP list, where each item includes a boolean indicating whether the IP belongs to AWS infrastructure, a per-item error field if the individual check failed, and a top-level failure count summarizing how many items encountered errors in the batch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/is-ip-aws-bulk-f15ebaf3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ip.intel.rallylive.ca](https://www.zero.xyz/host/ip.intel.rallylive.ca/llms.txt)
