goog.io | Unoffical Google Search API

```json
{
  "service_type": "platform",
  "base_url": "https://api.goog.io",
  "auth_method": "unknown",
  "auth_config": {
    "note": "Auth method not explicitly documented in provided content; likely API key/token based given typical unofficial search APIs. Requires verification against OpenAPI spec at https://api.goog.io."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No pricing information provided. Likely pay-per-query or subscription tiered; must check goog.io directly."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Google web search via API",
    "Fast response times",
    "Accurate results",
    "No proxy rotation required (claims dedicated clean USA IPs)",
    "OpenAPI V3 documented interface"
  ],
  "raw_analysis": "goog.io (api.goog.io) is an unofficial Google Search API that lets developers programmatically run Google searches and receive structured results. The provided documentation excerpt describes it as 'extremely fast and accurate' and emphasizes that it uses 'zero proxies' and 'clean USA IPs' — implying the vendor operates its own infrastructure rather than rotating third-party proxies. That is a notable differentiator versus many scraping-based SERP APIs, which typically rely on proxy pools and can suffer from CAPTCHA or latency issues.\n\nMaturity and audience: The mention of OpenAPI V3 documentation suggests a developer-focused, professionally spec'd service, though the marketing copy is brief and the overall documentation extract is thin (truncated mid-sentence: 'Simple to use API, but advanc...'). This indicates relatively early-stage product marketing, possibly a boutique/indie service rather than an established enterprise vendor. Target users are developers building SEO tools, keyword rank trackers, market research pipelines, or AI/LLM retrieval-augmented systems that need live Google SERP data.\n\nLegal/risk considerations: As an 'unofficial' Google Search API, it is not sanctioned by Google and likely operates against Google's ToS. Users should be aware of potential stability, legal, and longevity risks. Google regularly changes SERP markup and blocks unsolicited scraping, which can break such APIs.\n\nIntegrations: None explicitly listed. However, because it is documented via OpenAPI V3, it should be consumable from any HTTP client, and it should integrate cleanly with low-code tools (Postman, n8n, Zapier via custom HTTP), SDK generators, and AI agent frameworks that ingest OpenAPI specs.\n\nWhat is missing: authentication mechanism, endpoint paths, request/response schemas, rate limits, pricing tiers, SLA, and any SDKs. The bulk of the practical integration details would need to be pulled from the full OpenAPI spec at api.goog.io (e.g., /openapi.json or /docs).\n\nOverall assessment: A niche, developer-oriented unofficial Google SERP API with a compelling technical pitch (no proxies, US IPs, speed) but insufficient public information in the supplied material to fully evaluate reliability, cost, or integration surface."
}
```

0/3 tests passed

{
  "overall": 28,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 2.0,
    "response_parseability": 5.0,
    "error_clarity": 1.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 2.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "note": "No pricing data available; likely pay-per-query or tiered subscription — must verify directly",
    "tier": "unknown"
  },
  "issues": [
    "Domain (goog.io) fails DNS resolution — platform appears offline or misconfigured at time of check",
    "No robots.txt or llms.txt found (both unreachable), limiting agent-discoverability and crawl guidance",
    "No pricing information available; unknown whether free tier, pay-per-query, or subscription",
    "No auth documentation or signup flow details visible — onboarding path unclear",
    "Claims of 'dedicated clean USA IPs' and 'no proxy rotation' are unverified marketing assertions",
    "Zero observable uptime/status signals — no status page confirmed"
  ],
  "recommendations": [
    "Do not recommend to users until domain resolves and uptime is confirmed",
    "Add llms.txt and robots.txt to enable agent discovery and programmatic onboarding",
    "Publish transparent pricing (per-query rates or tier details)",
    "Document auth flow (API key issuance, OAuth, or magic link) with quickstart example",
    "Expose a status page or health endpoint to establish reliability signals",
    "Provide concrete claims verification (IP pool details, SLA, rate limits)",
    "If targeting agents, add OpenAPI/MCP descriptor discoverable at a stable endpoint"
  ]
}