OMNIGATE — x402 Gateway by ScriptMasterLabs

{
  "service_type": "platform",
  "base_url": "https://mcp-x402.onrender.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "x402 gateway",
    "unmapped endpoints (no public API documentation identified)",
    "auto-registered benchmark URL submission"
  ],
  "raw_analysis": "OMNIGATE is presented as an 'x402 Gateway' by ScriptMasterLabs, hosted at https://mcp-x402.onrender.com. The submission itself is a benchmark auto-registration with no descriptive content, documentation, or endpoint details. 'x402' refers to the HTTP 402-based payment protocol for machine-to-machine payments (often used in AI/agent payment flows), and the 'mcp-' hostname prefix suggests a Model Context Protocol (MCP) server. However, nothing in the provided text confirms API surfaces, authentication, pricing, or maturity. No API endpoints, auth methods, rate limits, or integration details can be derived. The platform should be treated as early-stage/unknown maturity, likely a developer-facing tool for x402 payment gating or MCP interactions. No public REST API is documented in the submission."
}

2/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 7.5,
    "error_clarity": 4.5,
    "doc_quality": 5.5,
    "auth_simplicity": 6.0,
    "latency": 10.0,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "pay-per-request (x402)",
    "price_floor_usdc": 0.001,
    "currency": "USDC",
    "network": "Base (eip155:8453)",
    "subscription_required": false,
    "notes": "Micropayments starting at 0.001 USDC per call. Full price list was not visible in the check results."
  },
  "issues": [
    "No public API documentation was identified. Endpoints are largely unmapped, so agents must rely on llms.txt and the discovery JSON.",
    "The pricing model was not captured in a structured form (type: unknown), and the per-endpoint price list is unclear.",
    "robots.txt returns 404 with an HTML error page (Express 'Cannot GET'). That is a minor hygiene issue and gives crawlers no guidance.",
    "The website uptime and llms.txt responses lack security headers.",
    "Payment requires a crypto wallet funded with USDC on Base. This is a barrier for users without crypto and means agents need wallet or x402 client support.",
    "The scope is broad ('LLM, search, fetch, social, RPC, prices') but the details are unclear, so it is hard to tell what a given endpoint does or guarantees.",
    "llms.txt shows an 'Authority refreshed' date of 2026-11-04, which may be a future date or a typo. It casts some doubt on how fresh the metadata is.",
    "The platform is a small vendor with no visible status page, SLA, or uptime history, so reliability can't be verified."
  ],
  "recommendations": [
    "Publish an OpenAPI spec or a full endpoint catalog with per-endpoint pricing, request/response schemas, and examples.",
    "Add a structured pricing table to the discovery JSON, including per-call costs for each service.",
    "Add a robots.txt, and security headers on all responses.",
    "Document error responses, especially x402 payment-required (402) flows, retry behavior, and rate limits.",
    "Provide a quickstart for agents covering wallet setup, a first paid call, and expected output.",
    "Add a status page and publish uptime figures.",
    "Check the date in the llms.txt metadata and keep it accurate.",
    "Recommend this to users who already operate in the crypto/x402 ecosystem and want cheap pay-per-call agent tools. For others, the setup friction is high."
  ]
}
```