MyOTP.App Verified

{
  "service_type": "platform",
  "base_url": "https://api.myotp.app",
  "auth_method": "api_key",
  "auth_config": {
    "header": "X-API-Key",
    "key_format": "32 character alphanumeric/underscore/hyphen",
    "location": "header"
  },
  "endpoints": [
    {
      "path": "/v1/generate_otp",
      "method": "POST",
      "description": "Generate and send a one-time passcode to a phone number via SMS, WhatsApp, or Telegram.",
      "request_body": "phone_number (E.164 without leading +), optional channel (sms, whatsapp, telegram), otp_length, otp_validity, template_order, otp_code (custom OTP), force_send, return_otp, brand",
      "response": "message_id, status, message, date_sent, expires_at, cost, optional otp"
    },
    {
      "path": "/v1/verify_otp",
      "method": "POST",
      "description": "Verify a one-time passcode provided by the user.",
      "request_body": "phone_number (optional if message_id present), message_id (optional, scopes the check), otp (required)",
      "response": "status (success, failed, expired), message"
    },
    {
      "path": "/v1/extend_otp",
      "method": "POST",
      "description": "Extend the expiry time of an existing one-time passcode.",
      "request_body": "message_id, duration (seconds 60-14400)",
      "response": "status, message"
    },
    {
      "path": "/v1/check_otp_status",
      "method": "POST",
      "description": "Check the delivery status of a sent OTP message.",
      "request_body": "message_id",
      "response": "delivery status"
    },
    {
      "path": "/v1/agent/register",
      "method": "POST",
      "description": "Automated registration for agents, sends a magic link for email confirmation.",
      "request_body": "email",
      "response": "confirmation status"
    },
    {
      "path": "/v1/topup",
      "method": "POST",
      "description": "Purchase credit packs via card or USDC to top up balance.",
      "request_body": "amount, currency, payment method details",
      "response": "transaction details"
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": "Pay-per-use credits at $0.02 per credit. Free tier of 15 credits upon signup. SMS costs from 1 credit per message in most countries, Telegram flat 1 credit globally. Volume plans starting at $20/month with credit bundles."
  },
  "rate_limits": {},
  "capabilities": [
    "OTP generation and delivery",
    "OTP verification with status check",
    "Multiple delivery channels: SMS, WhatsApp, Telegram",
    "Custom OTP length (4-8 digits) and validity (60-86400 seconds)",
    "Custom OTP code provision (using your own code)",
    "Branding and message template customization",
    "Delivery status webhooks with Standard Webhooks signing",
    "Agent self-registration via API",
    "402 payment top-ups for agents",
    "MCP server integration for AI agents",
    "Webhook retries on failure",
    "Telegram Gateway API integration"
  ],
  "raw_analysis": "MyOTP.App is a specialized OTP delivery and verification platform designed for developers and AI agents needing to send one-time passcodes via SMS, WhatsApp, or Telegram. It positions itself as a simpler, more cost-effective alternative to full identity platforms like Twilio Verify, focusing solely on OTP generation and verification with no TOTP or user management. The service automates code generation, expiry, and verification, allowing developers to keep OTP state server-side. The API is straightforward: two primary endpoints for generate and verify, plus extensions for extending expiry and checking delivery status. It offers agent-friendly features: automated signup via API, 402 payment responses for top-ups via USDC or card, and an MCP server at mcp.myotp.app for AI integration. The platform is relatively new but has listed in the official MCP registry and offers SDKs in JS and Python examples. Pricing is per message in credits ($0.02/credit), with a freemium trial of 15 credits. It lacks a sandbox environment but provides webhooks for production deliveries. Target users include developers integrating phone verification in apps (Supabase, Auth0, etc.) and AI agents that need to autonomously handle OTP challenges. The service is production-ready with OpenAPI spec and webhook support. Integration ecosystem includes MCP, Supabase hooks, Auth0 custom provider, Better Auth, n8n, WordPress, and others, making it a practical choice for modern stack adoption. Security uses API keys and IP allowlisting. Overall, it shows good maturity for focused functionality, though it lacks extensive rate limit documentation and a traditional sandbox."
}

0/4 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 4.5,
    "response_parseability": 8.5,
    "error_clarity": 5.5,
    "doc_quality": 7.0,
    "auth_simplicity": 3.5,
    "latency": 8.0,
    "consistency": 5.0
  },
  "issues": [
    "Website returns 403 Forbidden on main page and signup page - blocks direct browsing",
    "No robots.txt, llms.txt, or other LLM-friendly discoverability files found",
    "Signup flow requires manual credentials (no magic link, SSO, or API-only onboarding path)",
    "Security headers missing across all tested endpoints",
    "Webhook/API endpoints return 403, suggesting potential bot-blocking or geo-restrictions",
    "No public status page or uptime history available to verify consistency claims"
  ],
  "recommendations": [
    "Publish an llms.txt file with capabilities, pricing, and MCP server endpoint details",
    "Open up a public landing page to non-403 status or add allowlisting for common cloud regions",
    "Implement magic-link or API-key-only signup to enable agent-driven onboarding",
    "Add a public status page (e.g., statuspage.io) to demonstrate reliability",
    "Document webhook event schema and retry policy in machine-readable format (OpenAPI/JSON Schema)",
    "Ensure custom OTP codes and delivery channels have clear, tested error messages in docs"
  ]
}
```