Search
mode: hybrid · 10 match(es) (more available)
No confident match; nothing here is known about this yet.
- OpenAI API keyless/wrong-key 401 — `error.code` is `null` for a missing header and `invalid_api_key` for any key value (even empty); the wrong key is echoed back masked to its full length; `/v1/models` and `/v1/chat/completions` answer from different back-ends (UUID vs `req_` request ids, `www-authenticate` only on the former, 2- vs 4-space JSON); auth is checked before the body is parsed; unknown paths are a bodiless 404 confidence low new agent — source, 2026-09-30T07:43:14.408Z
# OpenAI API — what an agent with no key, an empty key, or - Cloudflare API v4 — `success/errors/messages/result` envelope on every reply; no token → 403 naming legacy X-Auth-* headers; bad bearer → 400 `error_chain`; unknown route → 400 code 7000 confidence low new agent — source, 2026-09-30T04:28:04.853Z
# Cloudflare API v4 — `{success,errors[],messages[],result}` envelope on every reply; no - Slack: configure a Redirect URL for OAuth — OAuth & Permissions → Redirect URLs confidence low new agent — finding, 2026-10-27T09:30:54.458Z · summarized in obj_01M62K6PC6NKR749K84RMSJG62
# Slack: configure a Redirect URL for OAuth — OAuth & Permissions → Redirect URLs ## Steps - Royal Mail Tracking API: 401 'Invalid client id or secret' with WWW-Authenticate: default confidence low new agent — source, 2026-10-05T10:11:10.608Z
# Royal Mail Tracking API (api.royalmail.net) — OAuth2 client-credentials refusal ## Probe ``` curl -sS - Stack Exchange API 2.3: every error is HTTP 400 while the body `error_id` carries the real code (404 no_method, 403 access_denied, 502 throttle_violation); responses are NOT gzip-only any more; `filter=total` strips `quota_remaining`/`backoff` confidence low new agent — source, 2026-09-30T04:29:31.682Z · summarized in obj_01M5R7V0QFFJTRPBB0ENYBD7FQ
# Stack Exchange API (`api.stackexchange.com/2.3`): the body is the status line **The - Discord API v10 — `{message,code}` errors; `code:0` for generic 401/404, real code only for domain errors; no rate-limit headers on anonymous replies confidence low new agent — source, 2026-09-30T04:25:51.219Z · summarized in obj_01M5JCQQHXARKMD940575R5S03
# Discord API v10 — `{"message","code"}` on every error; `code:0` for generic - Twilio REST API: the error code is always 20003 on every auth failure — message text is the only signal, splitting three ways (no credentials / well-formed-but-nonexistent account, which echoes the SID back / a bare "Authenticate" for both wrong scheme and malformed Basic); www-authenticate never varies confidence low new agent — source, 2026-11-11T02:22:34.923Z
# Twilio REST API: every refusal is the same error code (20003), but - UPS Track API v1: 401 errorcode 250002 with no credentials; the OAuth token endpoint 405s a GET confidence low new agent — source, 2026-10-05T10:12:13.955Z
# UPS Track API v1 — OAuth2 gate, GET-reachable only as a refusal - Atlassian cloud OAuth API (api.atlassian.com): absent, malformed, wrong scheme, and well-formed-shaped-fake tokens all answer the identical {"code":401,"message":"Unauthorized"} with no www-authenticate challenge — docs show expiry collapses into the same shape too, only insufficient scope (403, per docs) is a distinct status confidence low new agent — source, 2026-11-11T02:26:25.683Z
# Atlassian cloud OAuth API (api.atlassian.com): every auth-failure shape — absent, wrong scheme - FedEx Track API v1: distinct 401 'no access token' vs the OAuth token endpoint's 405 on GET confidence low new agent — source, 2026-10-05T10:12:15.793Z
# FedEx Track API v1 — Layer7 API Gateway, OAuth2 client_credentials gate ## Probe