# Five agent-facing products whose public docs would stop a cold agent

Every link below was fetched on 2026-09-15; statuses and quotes verified that day. No invented URLs or quotes. Each product was first seen in the MCP registry this past month.

## 1. AgentMesh

- Site: https://agentmesh.ai
- Docs: https://agentmesh.ai/for-agents.txt
- Quote: "you get nine tools"
- Failure: The join instructions define the connector as nine tools and name them, but the full tool table those same instructions link (https://dev.agentmesh.ai/mcp.html) lists seventeen, adding read_feed, platform_news, open_calls, list_jobs, show_job, quote_change, ask_for_change and copy_job, so an agent that plans from the join file never learns the hiring board or the job tools exist; the two pages also send its human to different sign-in hosts (app.agentmesh.ai versus personal.agentmesh.ai).

## 2. Inside Ads

- Site: https://inside.ad
- Docs: https://inside.ad/.well-known/api-catalog
- Quote: `service-desc" type="application/openapi+json" href="/v2/openapi.json"` (in the page source, the homepage's own API-description declaration).
- Failure: That declared service description returns 404 (checked twice), so an agent doing standard spec-first discovery from the site's own link dead-ends; the working spec is at https://app.inside.ad/api/v2/openapi.json, which the catalog lists but the homepage never names.

## 3. AssetLog

- Site: https://assetlog.ai
- Docs: https://assetlog.ai/llms.txt
- Quote: "POST https://api.assetlog.ai/v1/ai/submit"
- Failure: Every `/v1/...` endpoint the file gives answers a 301 to `/api/v1/...`; harmless for the GETs, but the submission path is a POST and a strict client that converts POST to GET on a 301 fails as a 405 instead of submitting, while the same file's MCP token path already uses `/api/v1/mcp/tokens`, so the canonical base is knowable but inconsistent.

## 4. Aether Wealth

- Site: https://aetherwealth.ai/mcp
- Docs: https://aetherwealth.ai/mcp
- Quote: "Tool schemas: https://aetherwealth.ai/mcp-tools.json"
- Failure: The linked file contains no schemas: all 49 entries carry only name, group and auth (some a limit), so required inputs for calls like connect_broker or propose_trade are defined nowhere an agent can read before connecting.

## 5. AskMiles

- Site: https://askmiles.ai
- Docs: https://askmiles.ai/docs/getting-started/mcp
- Quote: "Forty-six tools over your cards, valuations, balances, credits, certificates, gift cards, elite status and watchlist"
- Failure: The tools reference this page links ("Every MCP tool Miles exposes, grouped by domain, on one page") lists 52 tools across nine groups, so an agent that budgets or checks availability against the stated count is working from a number its own reference contradicts.