Interzoid Convert Currency Rate API

{
  "service_type": "platform",
  "base_url": "https://api.interzoid.com",
  "auth_method": "api_key",
  "auth_config": {
    "api_key_parameter": "key",
    "alternative_auth": "x402",
    "x402_details": {
      "payment_currency": "USDC",
      "payment_network": "Base",
      "flow": "Call endpoint without API key to receive HTTP 402 with payment requirements, pay via x402 client, retry with payment signature"
    }
  },
  "endpoints": [
    {
      "name": "Convert Currency Rate API",
      "description": "Convert an amount of one currency into another using current foreign exchange rates",
      "method": "GET",
      "base_url": "https://api.interzoid.com",
      "path": "see OpenAPI spec",
      "openapi_spec": "https://api.interzoid.com/openapi.json"
    },
    {
      "name": "Batch Match API",
      "description": "Match an entire CSV or TSV file of records and append SimKey similarity keys",
      "method": "GET",
      "base_url": "https://match.interzoid.com",
      "path": "/match",
      "openapi_spec": "https://match.interzoid.com/openapi.json"
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "traditional_access": "Subscription/API-key based pricing per https://www.interzoid.com/services/api-pricing",
      "x402_pay_per_call": "Pay-per-call in USDC on Base; batch match priced per record in submitted file",
      "pricing_page": "https://www.interzoid.com/services/api-pricing"
    }
  },
  "rate_limits": {
    "details": "Not specified in provided content; consult API pricing/terms pages"
  },
  "capabilities": [
    "Foreign exchange / currency conversion",
    "Company/organization name matching",
    "Individual name matching",
    "US street address matching and standardization",
    "Batch CSV/TSV data matching and deduplication",
    "Data standardization (canonicalization)",
    "Similarity keys (SimKey) for entity resolution",
    "Match confidence scoring",
    "Data enrichment (company, email, property, phone, location)",
    "AI-customizable structured data enrichment",
    "No-code data matching and enrichment wizards",
    "OpenAPI specifications for machine/agent consumption",
    "x402 pay-per-call API access (USDC on Base)"
  ],
  "raw_analysis": "Interzoid is a mature data quality platform offering cloud APIs, batch tools, and no-code applications focused on AI-powered data quality, data matching, entity resolution, data standardization, and structured data enrichment. It targets developers, data engineers, autonomous agents, data pipelines, analytics workflows, CRM systems, and enterprise data operations.\n\nThe platform exposes REST-style APIs documented via OpenAPI 3 specifications: a broad single-call API surface at https://api.interzoid.com (covering matching, standardization, validation, enrichment, and the Convert Currency Rate API for FX conversion) and a batch file-matching endpoint at https://match.interzoid.com/match that takes a public CSV/TSV URL plus column mappings and streams back enriched output with SimKey similarity keys.\n\nAuthentication supports two paths: traditional API-key access and a modern x402 payment scheme. With x402, agents can call endpoints without an API key to receive an HTTP 402 Payment Required challenge, pay in USDC on Base, and retry with a payment signature — enabling pay-per-call use without pre-registration. Batch matching is priced per record. Traditional subscription/API-key pricing is documented separately.\n\nIntegration support includes GitHub code examples, an interactive API tester (try.interzoid.com), no-code wizards for matching and enrichment, and detailed docs at docs.interzoid.com. The company appears well-established with case studies, customer references, partner programs, and support/sales channels. Suggested agent behavior guidance is embedded, indicating the platform is being deliberately positioned for autonomous agent consumption.\n\nMaturity: High for the data-quality/entity-resolution domain; broad API catalog with machine-readable specs. Notable uncertainty: exact rate limits, precise per-call subscription pricing tiers, and the specific endpoint path/parameters for the Convert Currency Rate API are not enumerated in the supplied content and should be resolved from the OpenAPI spec."
}

1/3 tests passed

{
  "overall": 74,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.5,
    "response_parseability": 9.0,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 8.5,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "subscription + pay-per-call (x402 USDC)",
    "notes": "Two paths: traditional API-key subscription pricing (quote-based, no public price shown) and x402 pay-per-call in USDC on Base. x402 is highly agent-friendly (no login, pay per use). Subscription pricing is opaque without visiting pricing page.",
    "agent_friendliness": "x402 path is machine-native; subscription path requires human account setup"
  },
  "issues": [
    "No llms.txt — agents can't discover platform capabilities in a machine-readable summary",
    "No robots.txt (404) — minor, may signal incomplete bot/crawler guidance",
    "Missing security headers on main website response — reduces trust signals for agent-mediated purchases",
    "Subscription pricing page required to understand costs; no inline/structured pricing in API or metadata",
    "Batch match priced per record in submitted file — token/record cost scaling not clearly documented in-band"
  ],
  "recommendations": [
    "Publish an llms.txt describing capabilities, endpoints, auth modes, and x402 payment flow for agent discovery",
    "Add structured pricing metadata (JSON endpoint or OpenAPI extension) exposing per-call and per-record rates",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to the marketing site to boost trust signals",
    "Expose a robots.txt guidance file and a machine-readable capability manifest alongside OpenAPI specs",
    "Document error codes and rate-limit headers explicitly in OpenAPI to improve error_clarity for agents",
    "Highlight x402 pay-per-call as the primary agent onboarding path — it eliminates signup friction"
  ]
}