{"uid":"cap_pyfgYp_oY1w8Q7juz8xhE","slug":"is-ip-vercel-bulk-7c4899d7","name":"is-ip-vercel-bulk","description":"Bulk is ip vercel: 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.","url":"https://ip.intel.rallylive.ca/bulk/ip/is/vercel?utm_source=zero.xyz","method":"GET","headers":{},"bodySchema":{"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"}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.1","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.1/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_6B0kignBvvnbphwMamO2c","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.1","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Checks up to 20 IP addresses in one call to determine if each belongs to Vercel's infrastructure, returning ordered results with per-item error fields and a failure count.","exampleAgentPrompt":"Can you check this batch of IP addresses and tell me which ones belong to Vercel's infrastructure? Here's my list: 76.76.21.21, 64.29.17.1, 198.51.100.5, 203.0.113.10.","exampleUseCases":[{"title":"Filter Vercel bot traffic from logs","prompt":"I have a list of IPs hitting our API — 76.76.21.21, 64.29.17.1, 198.51.100.5, 203.0.113.44, and 192.0.2.8 — can you tell me which ones are coming from Vercel so I can separate bot or deployment traffic from real users?"},{"title":"Security audit of inbound connection sources","prompt":"We're doing a security review and need to know which of these 15 IP addresses are Vercel infrastructure: 76.76.21.21, 64.29.17.1, 198.51.100.50, 203.0.113.7, 192.0.2.1, 198.18.0.5, 10.0.0.1, 172.16.0.1, 8.8.8.8, 1.1.1.1, 76.76.19.61, 64.29.18.55, 198.51.200.3, 203.0.114.9, 192.0.3.2 — please check all of them at once."},{"title":"Enrich IP list before fraud scoring","prompt":"Before I run fraud scoring, I need to tag which of these IPs belong to Vercel's network — here's the list of 10 addresses from today's signups: 76.76.21.21, 64.29.17.1, 198.51.100.5, 203.0.113.10, 192.0.2.8, 198.18.0.5, 172.16.0.1, 8.8.4.4, 1.0.0.1, 76.76.19.61 — can you check them all together?"}],"resultDescription":"An ordered array of results corresponding to each input IP, where each item includes a boolean indicating whether the IP belongs to Vercel's infrastructure, a per-item error field if the lookup failed for that entry, and an overall failure count for the batch.","failureModes":["Invalid or malformed IP address in the list causes a per-item error with the failure count incremented","Batch exceeds 20 IPs resulting in a request rejection or truncation","Network timeout when querying IP classification services upstream","Payment failure via x402 protocol blocking the request","Empty input list returning no results"],"whenToPreferThis":"Use this endpoint when you have a list of 2–20 IP addresses and need to determine Vercel infrastructure membership efficiently in a single API call with concurrent processing, rather than issuing individual single-IP lookups. Prefer this over the single-IP endpoint whenever you hold a batch of IPs to classify, as it reduces latency, API call overhead, and cost per IP. Choose this over generic WHOIS or ASN lookups when you specifically need Vercel detection with structured per-item error handling.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-13T00:40:50.275Z","isFirstParty":false,"canonicalSlug":"is-ip-vercel-bulk-7c4899d7"}