Hop

{
  "service_type": "platform",
  "base_url": "https://hop.exchange",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "cross-chain token transfers",
    "liquidity bridging between L2s",
    "AMM-based bridging",
    "developer SDK/contracts (monorepo)",
    "on-chain smart contracts",
    "governance (HOP token)"
  ],
  "raw_analysis": "Hop Protocol is a cross-chain bridge platform that enables fast and efficient transfers of tokens between Ethereum L2 rollups (Arbitrum, Optimism, Polygon, zkSync, etc.) and mainnet. It targets both end users (via a web interface at hop.exchange) and developers (via its monorepo, which contains smart contracts, SDK, and tooling). The service is a decentralized protocol rather than a traditional SaaS; interactions occur via smart contracts on supported chains, not a public REST API. There is no centralized authentication; users connect a wallet (MetaMask, WalletConnect, etc.) to sign transactions. The 'Hop Protocol Monorepo' indicates an open-source codebase under active development, with integrations available through npm packages or direct contract calls. Pricing is indirectly associated with gas fees and bridge fees (a small percentage of transfer amount), but no subscription/freemium model applies. Rate limits are enforced by blockchain networks and RPC providers, not by Hop itself. Maturity: launched in 2021, audited, and widely used in the DeFi ecosystem, though not a traditional API service. No public REST endpoints are documented; developers integrate by deploying or calling smart contracts or using the Hop SDK (TypeScript)."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 6.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "No pricing information available; bridging is contract/AMM-based with gas + protocol fees, but no documented fee schedule"
  },
  "issues": [
    "Pricing model unknown — no documented fee schedule for bridging or SDK usage",
    "No llms.txt (404) — agents lack a machine-readable platform summary",
    "robots.txt contains AI content-signal directives that may restrict agent scraping",
    "Website served with lang=\"id\" (Indonesian) on root — locale/content mismatch signals possible geo-routing confusion",
    "Documentation quality for onboarding and error conditions not verifiable from checks",
    "Auth flow not confirmed; no evidence of magic-link/SSO or agent-friendly identity onboarding"
  ],
  "recommendations": [
    "Publish a public pricing/fee schedule to improve token efficiency and recommendation confidence",
    "Add llms.txt describing capabilities, SDK entry points, and pricing for agent consumption",
    "Clarify robots.txt content-signal policy so agents know permitted usage",
    "Document an agent-friendly onboarding path (e.g., verified identity sign-in) to boost first_try_success and auth_simplicity",
    "Provide structured API/status endpoints and a status page to improve consistency scoring",
    "Standardize language/locale handling on the root domain"
  ]
}