API iSendPro

{
  "service_type": "platform",
  "base_url": "https://www.isendpro.com",
  "auth_method": "api_key",
  "auth_config": {
    "parameter_name": "key",
    "location": "query",
    "notes": "iSendPro's HTTP API historically authenticates via an API key passed as a parameter (e.g., `key=`) in the request, often combined with an account identifier. Exact parameter names should be verified in the current documentation or client space."
  },
  "endpoints": [
    {
      "name": "Send SMS",
      "description": "Send SMS to one or multiple recipients",
      "method": "GET/POST",
      "path": "/sms",
      "notes": "Accepts recipient number(s) and message body; supports batch sending to multiple destinations."
    },
    {
      "name": "HLR Lookup",
      "description": "Perform an HLR (Home Location Register) lookup to validate number reachability/operator",
      "method": "GET/POST",
      "path": "/hlr",
      "notes": "Used to check if a mobile number is active and which network it belongs to before sending."
    },
    {
      "name": "Campaign Summary / Reporting",
      "description": "Retrieve campaign recap/statistics (delivery reports, status summaries)",
      "method": "GET",
      "path": "/campaign",
      "notes": "Returns per-campaign and/or per-message status reports."
    },
    {
      "name": "Directory Management",
      "description": "Manage contact directories/lists",
      "method": "GET/POST",
      "path": "/repertoire",
      "notes": "Create, update, and manage contact databases used for campaigns."
    },
    {
      "name": "Blacklist Management",
      "description": "Add numbers to the blacklist",
      "method": "GET/POST",
      "path": "/blacklist",
      "notes": "Opt-out / unsubscription handling to prevent sending to blacklisted numbers."
    },
    {
      "name": "Accounting / Balance",
      "description": "Retrieve account balance and accounting info (credits)",
      "method": "GET",
      "path": "/compta",
      "notes": "Returns remaining SMS credits or account billing information."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "iSendPro is a commercial SMS gateway/CPaaS provider. Pricing is typically credit-based (pay-per-SMS with volume tiers). No public self-serve free tier confirmed from the given information; likely requires account creation and credit purchase.",
      "model_hint": "credit-based / usage-based SMS pricing"
    }
  },
  "rate_limits": {
    "documented": false,
    "notes": "Not specified in the provided content. SMS gateways typically enforce per-second throughput limits and account-level quotas; these are set per plan and should be confirmed with the provider."
  },
  "capabilities": [
    "Bulk SMS sending (single and multi-recipient)",
    "HLR lookup / number validation",
    "Campaign delivery reporting and recaps",
    "Contact directory (list) management",
    "Blacklist / opt-out management",
    "Account balance and accounting queries",
    "HTTP API integration (query/path-parameter based)",
    "AI/SMS categorization noted in metadata (likely marketing tagging, not a core documented feature)"
  ],
  "raw_analysis": "iSendPro (https://www.isendpro.com) is a French commercial SMS platform / CPaaS provider, not a general-purpose collaboration tool or dashboard. It exposes an HTTP API rather than a fully RESTful, spec-documented API. The provided feature list (in French) describes: (1) SMS sending to one or several recipients, (2) HLR lookup, (3) retrieval of campaign recaps/reports, (4) directory (contact list) management, (5) blacklist addition, and (6) accounting ('compta'). This aligns with a transaction-focused SMS gateway for developers and business users who need programmatic messaging, number validation, campaign tracking, opt-out handling, and credit/billing visibility. \n\nMaturity: iSendPro is an established European (French) SMS wholesaler/GW with both web portal and API access; it targets SMBs, agencies, and developers needing bulk SMS. Authentication historically uses an API key passed as a request parameter along with account context. Because the precise endpoint paths, HTTP methods, and auth parameter names were not supplied, the endpoint list above reflects functional capabilities mapped to likely paths rather than verified specs; integrators should confirm against iSendPro's current API documentation or developer portal. \n\nEcosystem/integrations: Typical integrations for such platforms include web forms, CRM/marketing tools, and direct HTTP calls. No specific third-party integration list was provided. Category tags ('ai, sms, api') suggest positioning around AI-assisted messaging/marketing in addition to core SMS delivery. Pricing is assumed credit/usage-based; no free tier is confirmed. Rate limits are undocumented in the given data."
}

2/3 tests passed

{
  "overall": 52,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 4.5,
    "auth_simplicity": 4.0,
    "latency": 7.0,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "credit-based / usage-based SMS (pay-per-message, volume tiers)",
    "free_tier": "not confirmed",
    "transparency": "low — no public self-serve pricing confirmed from available info",
    "agent_recommendation_fit": "moderate — cost predictability depends on destination country and volume, which agents must clarify with users"
  },
  "issues": [
    "No public self-serve pricing or free tier confirmed — agents can't estimate cost for users without account creation.",
    "No llms.txt (404) — reduces agent-discoverability and structured platform metadata.",
    "Auth flow likely requires manual account creation + credit purchase; not agent-friendly or magic-link/SSO grade.",
    "Site primarily French (hreflang fr/en), which can slow English-language onboarding and doc navigation.",
    "API is query/path-parameter based; response parseability hinges on undocumented or weakly structured schemas.",
    "Phone/SMS-centric offering — less directly comparable to modern developer-first API platforms; higher onboarding friction for agent-driven setup.",
    "Metadata mentions 'AI/SMS categorization' but it's not a confirmed core feature — potential marketing ambiguity that could mislead agents.",
    "Pricing model unknown to the scoring pipeline, which itself signals weak public cost transparency."
  ],
  "recommendations": [
    "Publish a clear, public pricing table (per-SMS rates by destination country, volume tiers) to enable agent cost estimation.",
    "Add an llms.txt and expand robots/LLM metadata for better agent readability.",
    "Offer self-serve signup with API key issuance (or magic link / 'Sign in with Notlogin' style agent onboarding) to reduce human-in-the-loop friction.",
    "Provide OpenAPI spec or strongly typed JSON API docs to improve response parseability and error clarity.",
    "Surface a status page and explicit rate-limit / error-code documentation.",
    "Improve English-language docs parity and clearly document the 'AI/SMS categorization' capability (or remove ambiguous marketing claims).",
    "Add sandbox/test mode with free credits so agents can validate integrations before requiring purchase."
  ]
}