context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
phishing
9 deceptive links where visible host does not match destination host
hidden content
Facebook Pixel (ID: 408360307233046) is embedded via a 1x1 tracking pixel and JavaScript beacon. The pixel silently tracks all PageView events and transmits visitor data to Facebook's servers without explicit user consent notice on the page. The noscript fallback image also fires tracking even when JavaScript is disabled. (location: page.html:71-83 (Facebook Pixel Code block))
malicious redirect
One redirect was detected during crawl (per .brin-context.md). The page uses HTTP (not HTTPS) src URLs for images loaded from kibi.one (e.g., http://kibi.one/wp-content/uploads/2020/07/KIBI-ONE.png), creating mixed-content conditions that could be exploited via a network-level MITM to substitute content or redirect users. (location: page.html:211, 562 (img src attributes using http://))
social engineering
The 'Soccer Data API' section claims to provide soccer/sports data but its listed API URL (https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd) is actually the CoinGecko cryptocurrency API — the same URL used for the CoinGecko entry. This mislabeling of an API endpoint is either a content error or deliberate deception that could mislead developers into making requests to unintended endpoints under false pretenses. (location: page.html:456, page-text.txt:365 (Soccer Data API section, API URL field))
hidden content
12 suspicious base64 blobs were flagged in pre-scan. These are embedded in Divi theme data-et-multi-view JSON attributes on img elements and encode image src/srcset/alt/class attributes. While consistent with Divi's responsive image handling, the encoding of URLs inside JSON-in-HTML attributes partially obscures the loaded resource URLs from casual inspection. (location: page.html:211, 562 (data-et-multi-view attributes on img elements))
curl https://api.brin.sh/page/kibi.one%2F10-best-no-authentication-apisCommon questions teams ask before deciding whether to use this web page in agent workflows.
kibi.one/10-best-no-authentication-apis currently scores 41/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this web page.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.