Chaingateway.io

{
  "service_type": "platform",
  "base_url": "https://chaingateway.io",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization",
    "scheme": "Bearer",
    "notes": "API key / project credentials required. Users must register at chaingateway.io to obtain API access credentials."
  },
  "endpoints": [
    {
      "path": "/api/v1/ethereum/transaction",
      "method": "POST",
      "description": "Send an Ethereum transaction (native ETH or ERC-20 token transfer) to the network."
    },
    {
      "path": "/api/v1/ethereum/transaction/{txid}",
      "method": "GET",
      "description": "Retrieve details/status of a previously submitted Ethereum transaction by transaction ID."
    },
    {
      "path": "/api/v1/ethereum/address/{address}/balance",
      "method": "GET",
      "description": "Query the ETH balance for a given Ethereum address."
    },
    {
      "path": "/api/v1/ethereum/address/{address}/nonce",
      "method": "GET",
      "description": "Retrieve the current transaction nonce for a given Ethereum address."
    },
    {
      "path": "/api/v1/ethereum/block/{blockNumber}",
      "method": "GET",
      "description": "Fetch Ethereum block information by block number or hash."
    },
    {
      "path": "/api/v1/ethereum/gas/price",
      "method": "GET",
      "description": "Get current recommended gas price estimates for the Ethereum network."
    },
    {
      "path": "/api/v1/ethereum/contract/{address}",
      "method": "GET",
      "description": "Read data from an Ethereum smart contract at a specified address (ABI-based calls)."
    },
    {
      "path": "/api/v1/ethereum/contract/{address}/call",
      "method": "POST",
      "description": "Execute a read or write smart contract function call via the gateway."
    },
    {
      "path": "/api/v1/ethereum/erc20/{contractAddress}/balance/{address}",
      "method": "GET",
      "description": "Get the ERC-20 token balance for a specified wallet address."
    },
    {
      "path": "/api/v1/ethereum/webhook",
      "method": "POST",
      "description": "Create a webhook subscription to receive notifications for incoming transactions or contract events."
    },
    {
      "path": "/api/v1/ethereum/wallet",
      "method": "POST",
      "description": "Create and manage Ethereum wallets via the gateway (non-custodial / custodial depending on plan)."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Pricing information is not specified in the provided description. Chaingateway.io typically offers tiered subscription plans (free/dev, startup, business, enterprise) based on API request volume and features. Refer to the official website for current pricing."
    }
  },
  "rate_limits": {
    "notes": "Not documented in the provided description. Likely plan-dependent with per-second or per-month request caps. Consult chaingateway.io documentation for specifics."
  },
  "capabilities": [
    "Ethereum blockchain interaction via REST API",
    "Send and track ETH / ERC-20 token transactions",
    "Query wallet balances and account nonces",
    "Read and write Ethereum smart contract functions",
    "Broadcast raw signed transactions",
    "Webhook/event notifications for on-chain activity",
    "Gas price estimation and transaction status polling",
    "Wallet creation and management",
    "Abstracts away node infrastructure (Infura/Alchemy-style gateway)"
  ],
  "raw_analysis": "Chaingateway.io is a blockchain infrastructure platform that exposes a REST API for interacting with the Ethereum network, positioning itself as 'the bridge between Ethereum and the real world.' It is a developer-facing service (category: ai, api) that abstracts the complexity of running and maintaining an Ethereum node, offering hosted endpoints for common blockchain operations: sending transactions, checking balances, querying blocks, calling smart contracts, and managing ERC-20 tokens. Authentication is via API key / project credentials obtained after registration. The platform targets crypto startups, fintech developers, and businesses needing to integrate Ethereum functionality (payments, tokenization, DeFi) without running their own infrastructure. It is comparable to Alchemy/Infura-style gateway services but with an emphasis on payment/bridge use cases. Maturity is moderate — it has a presence on Postman's API network and its own marketing site, but public detail on pricing, SLAs, and rate limits is limited in the provided source. No public documentation URL, OpenAPI spec, or SDK list was included in the prompt. Integration surface is primarily REST over HTTPS with JSON payloads, plus webhooks for real-time events. Key caveats for assessment: verify current pricing tiers, supported networks (Ethereum mainnet vs. testnets vs. other chains), custodianship model for wallets, and whether the API requires users to sign transactions client-side or can broadcast on their behalf."
}

2/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 8.5,
    "error_clarity": 5.5,
    "doc_quality": 6.5,
    "auth_simplicity": 7.0,
    "latency": 9.7,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "tiered_subscription",
    "notes": "Pricing not published in the provided description; typically tiered by API request volume. No per-call cost surfaced."
  },
  "issues": [
    "Pricing model not documented in available materials — agents can't reliably quote cost to users",
    "No llms.txt (404) — suboptimal for AI agent discovery and capability summarization",
    "Error/limitation documentation not evidenced (rate limits, chain support matrix, nonce handling edge cases unclear)",
    "Auth flow details unspecified — unclear if API key signup is frictionless or gated by human verification"
  ],
  "recommendations": [
    "Publish a public pricing page with per-tier request limits and overage costs",
    "Add llms.txt exposing endpoints, auth scheme, and chain support for agent consumption",
    "Document rate limits, error codes, and known limitations explicitly",
    "Provide a one-command quickstart (API key issuance + first request) to reduce time-to-first-call",
    "Ensure OpenAPI/Swagger spec is linked for structured tool integration"
  ]
}