OpenAI / GPT Relay Detection

Run 8 Chat Completions protocol checks + usage field fingerprinting to quickly verify whether an OpenAI / GPT relay is genuine.

TokenAPI Scan isn't a single-point speed test — it brings protocol behavior, usage fields, model responses, provider profiles, and risk data into one evidence framework.

Entering detection from toolcode.top profile. This profile has no pre-fillable endpoint yet. Please enter your provider API address manually.
Back to profile
Behavioral / Protocol-Level Verification: This test cannot reliably distinguish a genuine high-end model from a downgraded impersonation. We verify whether the relay endpoint conforms to the OpenAI Chat Completions protocol specification, whether capabilities are complete, and whether the usage fields match the official response shape.

OpenAI-compatible root URL. Use https://api.example.com or https://api.example.com/v1.

Used only for this detection. Not written to reports or persisted.

Chat Completions

Verifies chatcmpl-, chat.completion, choices, finish_reason, usage and other official response structures.

Capability Completeness

Performs tool call and JSON schema probing to detect relay layers that wrap OpenAI protocol into simplified text interfaces.

Field Discrepancy

Records stream/non-stream consistency and usage field structure to identify common wrapper layers and protocol adaptation anomalies.

Frequently Asked Questions

I paid for GPT — how do I know the relay isn't secretly swapping in a cheaper model?

Check for "leaked" fields in the response. OpenAI's official response only contains three token count fields. But if the relay secretly routes your request to a Claude backend and re-wraps it as OpenAI format, Anthropic's fields often leak through. When TokenAPI Scan catches these unexpected fields in the response, it marks them as a "critical issue" and drops the overall rating to yellow.

In short: genuine GPT responds according to OpenAI's own spec — counterfeit wrapper layers often leave traces from the other vendor.

I scored 75 — why is the circle yellow instead of green?

Score is only one dimension. TokenAPI Scan also checks for "critical issues" — even if your score passes the threshold, as long as there is 1 critical issue (like the field leakage mentioned above), the overall conclusion drops to yellow "use with caution".

This usually means: the endpoint works and returns results, but it may not be running the model you think. If you're just chatting or writing everyday text, it might be fine. But for coding or serious tasks, we recommend switching providers.

The test shows "0 GPT models available" — is the relay down?

Most likely the relay isn't broken — this key simply doesn't have GPT model access. Many multi-provider relays sell models grouped by vendor. Some customers buy Claude cards, others buy Gemini cards — if you haven't purchased GPT access, the models won't be available.

Before running detection, TokenAPI Scan quickly checks which models your key can use. If you're on the OpenAI page but see 0 GPT models, the system will automatically prompt: "This key can actually access X Claude models — want to test over there?" Just click through.

Why can't OpenAI detection "guarantee authenticity" like Claude can?

Because OpenAI doesn't include a "mathematical proof"-level anti-counterfeiting code in its responses. Claude has a cryptographic thinking signature that relays cannot forge, so TokenAPI Scan can give very definitive conclusions on Claude.

For OpenAI, we can only judge from indirect clues — "does the behavior look like GPT?", "are the field formats correct?", "are capabilities complete?" — so our stance is behavioral/protocol-level detection. We can tell you "looks normal" or "looks suspicious", but can't provide 100% mathematical proof. For definitive conclusions, we recommend testing the same relay with Claude model detection.

More OpenAI relay questions → /faq#openai · All FAQs

Popular OpenAI / GPT Provider Profiles

Sorted by verified model hit count + pass rate:

API2D

Hit 48 GPT models · Pass rate 100.0%

dall-e-2 · dall-e-3 · davinci-002 …

View Profile

Aihubmix

Hit 6 GPT models · Pass rate 100.0%

gpt-4o-transcribe-diarize · gpt-5.6-luna · gpt-5.6-sol …

View Profile

GPTGod

Hit 2 GPT models · Pass rate 100.0%

batch-get-gpts · chatgpt-4o-latest

View Profile

🔧 Network Environment Check

After verifying relay authenticity, local network variables should also be ruled out. We first read your browser's current public egress IP in-station and use Net.Coffee + ProxyCheck for cleanliness reference. The service host IP is never mistaken for your egress.

AI Egress Cleanliness Reference

Identifying current egress via browser-direct public trace...
Cleanliness --/100
Checking...
Note

This shows public signals and third-party risk references, not equivalent to the official Claude / OpenAI blocklist. For more granular network info (DNS, WebRTC, Ping, etc.), open the in-station toolkit.

🛡️

Current Egress Profile

We first identify the public egress IP seen by your browser, then query third-party public signals and cache them in the local database.

Open IP Lookup

📡

Network Connectivity Check

Use in-station network tools to check latency, status, and browser access paths, reducing third-party redirects.

Open In-Station Tools