Neuralab CheckerAI access & network readiness

AI Readiness Checker

Instantly see your current IP, network, andbrowser environment, plus a readiness estimate for major AI services: Anthropic Claude, Google Gemini, Google AI Studio / Gemini API, NotebookLM, and OpenAI ChatGPT / API.

No account, no API keys, no payment. The check runs automatically when the page loads, or start it manually below.

Ready to run. Your check has not started yet.

Your IP & network facts

These are server-observed facts about how your request reaches our backend. They are not a promise of access to any AI provider account.

Network facts will appear here after the check runs.

Your browser facts

Collected in your browser and shown transparently. We only read the non-invasive signals needed to estimate readiness.

Browser facts will appear here after the check runs.

Provider readiness scorecards

Each provider gets its own scorecard with a score, verdict, confidence, reason codes, risk factors, and remediation hints. Verified facts and heuristic conclusions are labeled separately.

Anthropic / Claude

web service

Not checked yet

Readiness signals for claude.ai and Anthropic's public web surface, based on host reachability and browser environment.

Google Gemini Web

web service

Not checked yet

Reachability and environment signals for the Gemini web app at gemini.google.com.

Google AI Studio / Gemini API

hybrid service

Not checked yet

Signals for Google AI Studio and the Gemini API endpoints, covering both web and API surfaces.

NotebookLM

web service

Not checked yet

Reachability signals for NotebookLM, which typically redirects to Google authentication.

OpenAI / ChatGPT / API

hybrid service

Not checked yet

Signals for ChatGPT's web app and the OpenAI API, covering both surfaces in a single scorecard.

This checker estimates readiness from anonymous reachability and browser signals. It does not send credentials and cannot guarantee access to any AI service, especially authenticated web apps and APIs.

How the readiness check works

1. Server-observed network facts

Our lightweight Go API records the IP it sees for your request, the protocol family, and best-effort reverse DNS. These are verified facts about your connection to us.

2. Browser environment facts

Your browser reports language, timezone, viewport, and cookie / localStorage support. Many AI web apps rely on these, so they inform the readiness estimate.

3. Bounded provider probes

We run short, credential-free reachability probes toward each provider's public hosts with strict timeouts, then classify the outcome without overclaiming.

4. Transparent scoring

A deterministic scoring engine combines the evidence into a per-provider score, verdict, and confidence, always separating verified facts from heuristics.

Who is this for?

Anyone troubleshooting access to AI services: developers checking API reachability, users behind restrictive networks or VPNs, and teams verifying whether Claude, Gemini, ChatGPT, or NotebookLM are reachable from a given connection. The checker is a fast diagnostic, not a guarantee of account access.

Frequently asked questions

What does this AI readiness checker actually check?
It inspects your current IP and network facts observed by our server, collects non-invasive browser facts in your browser, and runs bounded reachability probes toward the public hosts of major AI services. It then estimates readiness per provider.
Does it guarantee I can access Claude, Gemini, ChatGPT, or NotebookLM?
No. The checker estimates readiness from anonymous reachability and browser signals. It cannot guarantee access to any AI service, especially authenticated web apps and APIs that depend on your account, region, and billing status.
Do I need to log in or provide API keys?
No. The MVP never asks for accounts, passwords, billing details, or provider API keys. Provider probes run without credentials and unauthenticated responses are treated only as host-reachability evidence.
What is the difference between a verified fact and a heuristic?
A verified fact is something we directly observed, such as your server-observed IP or a browser capability. A heuristic is an inference from indirect evidence, such as guessing likely web-app readiness from host reachability. The results label both clearly.
Why does a provider show blocked or unknown?
Some AI hosts return 403 to automated probes or hide the real cause behind CORS and bot protection. That is reachability evidence, not proof of failure. Unknown or blocked simply means we could not confirm readiness, and the reasons explain why.
Is my IP or browser data stored?
The backend does not persist your IP or browser check history by default and requires no database. The checker is a stateless utility focused on giving you an immediate, transparent readout.