SERPHouse vs You.com APIs

SERPHouse 23

Read for a closed service, with its repositories read as code. No changelog or dated API change was found. The newest release is MCP server 1.1.0 on 6 July 2026, 123 days before 6 November, and the last commit in its repository was on 22 July (10). No release or dated change in the 90 days from 8 August; the about page's 2026 entry (Forums, Place Details and Scraper APIs) is undated (0). No changelog; support by email. Issues weren't read, since the GitHub API refused us for its rate limit (5 of 25). Not in the official MCP registry, though the repository's server.json names io.github.SERPHouse/serphouse-mcp. Node.js SDK last changed 24 June 2026, PHP SDK 10 May 2024, and no Python SDK repository was found under the SERPHouse organisation (5 of 15). The MCP repository has an npm publish workflow and no tests (3 of 10). 10 + 0 + 5 + 5 + 3 = 23.

You.com APIs 85

@youdotcom-oss/mcp 4.0.7 tagged on 2026-10-28 and an API changelog entry on 26 October for the Inference Router (30). MCP 4.0.5, 4.0.6 and 4.0.7 between 19 and 28 October, all version-bump publishes, and API changelog entries on 4, 5 and 11 August, 2 and 23 September and 5, 7, 9 and 26 October (20). A dated public API changelog, support at api@you.com and a support page, and the MCP repo merges changes weekly. We didn't read the open issues (11). Listed in the official MCP registry as io.github.youdotcom-oss/mcp at 4.0.7, with a current Python SDK (3.6.0, 14 October). The TypeScript SDK is deprecated (15). CI, Semgrep and conventional commits on the MCP repo (9).

SERPHouse 11

One key per account, one account per user, no scopes or rotation found (10). The REST API documents api_token in the query string and the hosted MCP server takes the key only in its URL path, less 10 (0 of 30). Searches only read, with no read-only or restricted key (8 of 20). Results are third-party snippets and AI Overview text, with no prompt-injection guidance (0). An account tool shows plan and credit usage; no per-call log was found (3 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). 0 + 8 + 0 + 3 + 0 = 11.

You.com APIs 59

Several keys per organisation in the X-API-Key header, revoked immediately on delete, rotation by create-then-delete, and roles where developers see only their own keys. The hosted MCP takes OAuth 2.1. No per-key scopes documented. No secret in a URL (22). Tool allow-lists on the MCP, a two-tool free profile and no tool that writes or deletes. Since 5 October a key can carry a spending cap per billing period, and a capped key answers 429 spend_cap_exceeded when it's reached, which bounds what a leaked or runaway key can spend, as kagi-search's per-key cap does (18). Search and Contents return untrusted page text. The only content control we found is safesearch, and no prompt-injection guidance (2). The key list shows a last-used date and each capped key's spend, and the troubleshooting page says Platform Logs list recent requests with error messages, response details and a request ID. No retention period, logs API or audit log of key actions was found, so 9, between numeral's 8 for a dashboard Logs tab and deepgram-stt's 10 for console and API logs (9). trust.you.com, a Vanta trust centre, links a vulnerability disclosure page and a subprocessor list but rendered only with JavaScript on 1 November, security.txt returned 404 on you.com, and the MCP repo runs Semgrep in CI (8).

SERPHouse 40

No x402, MPP or L402 (0). Per-1,000 prices for SERP, autocomplete and top-100 requests published without login (20). Free trial of 4,000 credits for 7 days, 'No Credit Card Required' (20). A person signs up in a browser and confirms an email (0). 0 + 20 + 20 + 0 = 40.

You.com APIs 88

x402 (USDC on Base or Solana) and MPP (USDC on Tempo) on GET /v1/search, /v1/agents/search and POST /v1/finance_research. On 1 November an unpaid GET https://api.you.com/v1/search returned 402 with an x402 v2 PAYMENT-REQUIRED challenge for 5,000 base units of USDC on Base and on Solana and an MPP WWW-Authenticate: Payment challenge on Tempo, and an unpaid POST /v1/finance_research returned the same pair, with x402 at 110,000 base units. Contents, Answer and Research still need a key (28). Per-call and per-page prices published without a login (20). The pricing FAQ now says $10 of API credit on sign-up and $90 more on verifying the account, no card, with sign-up credits valid 60 days. The Web Search card on the same page says '$10 free credit' (20). The MCP free profile needs no key (100 queries a day), and x402 or MPP needs no account (20).

SERPHouse 40

Read with the hosted lines. No status page is linked from the site or docs, and status.serphouse.com did not answer on 6 November 2026 (0). No readable incident history (5). Rate limits published, 60 requests a minute and 60 concurrent on every self-serve plan (15). 429 is documented as 'slow down', and a 200 can carry "status": "error" with 'Please try again', with no Retry-After or backoff guidance. Failed requests aren't charged (5 of 15). The pricing page lists a 99.99% uptime SLA on Basic and Regular and the docs a 99.95% one, but no SLA terms or credits were found in the terms (5 of 10). Generally available (10). 0 + 5 + 15 + 5 + 5 + 10 = 40.

You.com APIs 80

Rootly status page at status.you.com with Search/Index, Live News and AI Search API components (20). Its robots.txt loaded on 1 November, but incident pages still answered with a Cloudflare challenge, so we read the history RSS feed as before. In the 90 days to 1 November it lists one incident, an 'Authentication Outage' on the AI Search API component posted on 5 October, and nothing after it. The feed gives no duration, so we couldn't establish the outage as a major. Minor only (20). 10 requests a second per API and 5 for Finance Research on self-serve accounts, re-read on 1 November (15). 429 carries Retry-After, the docs give exponential backoff capped at 60 seconds, and X-RateLimit-* headers allow client-side throttling (15). No SLA found for the search APIs. The pricing page banner claims an uptime SLA of at least 99.9% for the new Inference Router, but we found no SLA document (0). GA (10).

SERPHouse 66

No OpenAPI or similar contract for the REST API. The MCP server's tools carry typed Zod schemas, published in the source and a static server card (18 of 25). llms.txt at the site and the docs, and every docs page as Markdown (10). MCP tool descriptions say which tool to use for what, such as serphouse_google_web when device or num_result is needed, while the docs pages lead with marketing lines such as 'Unlock captivating Google video content' (12 of 20). Enums for device, SERP type, engine and video duration, defaults and 37 described parameters (11 of 15). A status code table and request examples per engine, with a generic error body (12 of 15). No changelog or API versioning; only the MCP server has tags (3 of 15). 18 + 10 + 12 + 11 + 12 + 3 = 66.

You.com APIs 92

Public OpenAPI, one specification per API from the index at you.com/docs/openapi.json (25). llms.txt with Markdown twins of every page (10). A 'Choose the right API' page and MCP docs say which endpoint fits which job, and the MCP docs say there is no you-answer tool (15). Typed parameters in the OpenAPI, and the MCP rejects conflicting domain filters, such as include_domains with exclude_domains (12). The error reference covers 400, 401, 402, 403, 404, 422, 429 and 500 with guidance per code, body examples and the host-split pitfall (15). Versioned paths (/v1) and a dated public API changelog at you.com/docs/changelog, linked from llms.txt, with entries from 15 July to 26 October 2026 (15).

SERPHouse 64

23 MCP tools with no toolsets or filtering (15 of 25). num_result, max_pages, paging, device, location, language, date and video filters (16 of 20). Status codes are tabulated, but a 200 can also mean an error and the body carries only 'Please try again' (10 of 20). Searches only read and failed requests aren't charged, but the MCP tools carry no readOnlyHint or other annotations (10 of 20). serphouse_search needs only q and defaults to the US; most other tools need loc or loc_id. Official Node.js, PHP and Python SDKs are documented (13 of 15). 15 + 16 + 10 + 10 + 13 = 64.

You.com APIs 83

Six MCP tools per the docs, which state there is no you-answer tool, with ?tools= or X-Allowed-Tools to load a subset, a default allow-list of four, and a free profile that exposes two. Web Search returns up to 100 results with extraction opt-in (25). Result count, domain include, exclude and boost lists, safesearch, and since 9 October a total_max_tokens budget of 1,024 to 8,192 on highlights, which the changelog says brings a 10-result response under 1,000 tokens (20). Each error code says what to do next, and 402 says whether to add credits or pay the challenge (20). Search is read-only and a 402 can be retried once paid. We couldn't see MCP annotations, since the hosted server's source isn't public (8). Few required parameters, but Web Search and Contents live on ydc-index.io while Answer and Research run only on api.you.com, and the only current SDK is Python. The TypeScript @youdotcom-oss/sdk has been deprecated on npm since 3 March 2026 in favour of the MCP package (10 of 15).