Local-Eye

See the web as a human does. Residential IPs, GPU screensho

Visit Website
May 25, 2026 I built a DNS for AI agents — and connected it to my other 3 API

There are thousands of AI agents now. Millions coming. But there's no way for them to find each other.

So I built AgentSeek — a registry where agents can discover each other by capability. Search "verify business hours" and get endpoints instantly. Like DNS, but for AI agents.

But discovery is only useful if there's something to discover. So I connected it to the rest of my Agent Suite:

👁️ Local-Eye — Residential IPs, GPU screenshots, and phone verification for agents (posted here yesterday)

📊 Agent Monitor — Trust scores and heartbeat monitoring for agent interactions

🔍 AgentSeek — The discovery layer that ties them all together

The idea: agents shouldn't just find each other — they should verify each other is real (Local-Eye), monitor each other's reliability (Agent Monitor), and discover new capabilities on the fly (AgentSeek).

Free tiers on all three. AgentSeek has a live search demo at agentseek.co.

Built solo with my AI co-developer. RT by day, shipping infrastructure at night.

Comment

May 24, 2026 Phone Verification — Live Demo

I almost didn't ship phone verification.

The code was done. The API worked. Transcripts were coming back clean. But I couldn't honestly say I'd heard it — until tonight, when I called a number I could answer and heard my own AI on the other end asking if the business was open.

Now you can try it yourself: https://api.localeye.co/phone-verify

Enter any business number and a question. The AI calls, asks, and transcribes the answer in real-time.

This is what "shipped" feels like when you can actually hear it work.

Comment

May 24, 2026 I built an API that lets AI agents see the web like humans do

Hey everyone! I'm Ron — an RT (respiratory therapist) by day, solo founder by night.

I kept running into the same problem with my AI agents: they couldn't verify the real world. They'd get blocked by bot detection, see cached/stale data, and had no way to confirm if a business was actually open right now.

No API combined all three capabilities I needed — residential IPs, GPU screenshots, and phone verification — in one place.

So I built Local-Eye.

What it does:

👁️ Residential IPs — Browse without getting blocked. Your agent sees what a human sees.

📸 GPU-rendered screenshots — Full-page captures with JavaScript rendering. No more parsing HTML.

📞 AI phone verification — Call a business and confirm their hours, address, or services. An AI agent that actually picks up the phone.

Pricing: Free tier (5 requests/day), Starter ($9/mo), Pro ($49/mo), Enterprise ($499/mo)

Tech stack: FastAPI + SQLite + Cloudflare tunnels + Vercel. Built mostly by my AI co-developer while I was at the hospital.

What I've learned so far:

• The "scraping" market is crowded but nobody does real-time phone verification

• Free tier users convert faster when they can test without a credit card

• Building with an AI agent is 10x faster but you still need to know what you're building

Would love feedback from anyone building agents or doing web scraping. What's your biggest verification headache?

localeye.co

Comment

About

I'm a respiratory therapist by day. When I started building AI agents, I kept hitting the same wall: they couldn't see the real web. They'd get blocked by bot detection, they couldn't verify if a business was actually op