Rebilly REST API

{
  "service_type": "platform",
  "base_url": "https://www.rebilly.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "REBILLY-API-KEY",
    "alternate_header": "Authorization: Bearer <token>",
    "notes": "Rebilly uses API keys created in the dashboard, passed via the REBILLY-API-KEY header. OAuth2/JWT is also supported for some flows."
  },
  "endpoints": [
    {
      "name": "Customers",
      "path": "/customers",
      "methods": ["GET", "POST", "PUT", "PATCH", "DELETE"],
      "description": "Manage customer records"
    },
    {
      "name": "Subscriptions",
      "path": "/subscriptions",
      "methods": ["GET", "POST", "PUT", "PATCH", "DELETE"],
      "description": "Manage recurring billing subscriptions"
    },
    {
      "name": "Transactions",
      "path": "/transactions",
      "methods": ["GET", "POST"],
      "description": "Create and query payment transactions"
    },
    {
      "name": "Invoices",
      "path": "/invoices",
      "methods": ["GET", "POST", "PUT", "PATCH"],
      "description": "Manage invoices and billing documents"
    },
    {
      "name": "Payment Instruments",
      "path": "/payment-instruments",
      "methods": ["GET", "POST", "PATCH", "DELETE"],
      "description": "Store and manage payment methods (cards, bank accounts, PayPal, etc.)"
    },
    {
      "name": "Plans",
      "path": "/plans",
      "methods": ["GET", "POST", "PUT", "PATCH", "DELETE"],
      "description": "Define subscription plans and pricing"
    },
    {
      "name": "Products",
      "path": "/products",
      "methods": ["GET", "POST", "PUT", "PATCH", "DELETE"],
      "description": "Catalog of products/services"
    },
    {
      "name": "Webhooks",
      "path": "/webhooks",
      "methods": ["GET", "POST", "PUT", "DELETE"],
      "description": "Configure event webhooks"
    },
    {
      "name": "Disputes",
      "path": "/disputes",
      "methods": ["GET", "PUT"],
      "description": "Manage chargebacks and disputes"
    },
    {
      "name": "Reports",
      "path": "/reports",
      "methods": ["GET"],
      "description": "Access reporting and analytics endpoints"
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "Rebilly is an enterprise subscription billing and payments platform; pricing is typically custom/quote-based depending on transaction volume and features. Contact sales for details."
    }
  },
  "rate_limits": {
    "notes": "Rebilly enforces rate limits per API key/IP. Specific values are documented in their API reference; responses include rate limit headers."
  },
  "capabilities": [
    "Subscription and recurring billing management",
    "Payment gateway orchestration across 100+ providers",
    "Customer and payment instrument vaulting",
    "Invoicing and dunning",
    "Chargeback and dispute management",
    "RESTful JSON API with predictable resource URLs",
    "Webhooks for real-time event notifications",
    "Reporting and analytics",
    "Fraud prevention and risk management",
    "Multi-currency and global payment support"
  ],
  "raw_analysis": "Rebilly is a subscription billing, payments, and revenue management platform aimed at SaaS and subscription-based businesses. Its REST API is well-documented, HTTP-based, and returns JSON with standard HTTP status codes. Authentication is primarily via API keys (REBILLY-API-KEY header), with OAuth-style tokens also supported. The API covers the full billing lifecycle: customers, subscriptions, plans, products, invoices, transactions, payment instruments, disputes, and webhooks. It integrates with a large number of payment gateways and processors, positioning itself as an orchestration layer. The service is mature (founded 2012) and targets mid-market to enterprise companies. Pricing is quote-based/subscription rather than self-serve. Rate limits exist but specific numbers require checking their developer docs. The provided URL points to a contact page rather than the API base, but the canonical API base is https://api.rebilly.com."
}

2/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 9.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 4.0,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "custom/quote-based",
    "self_serve": false,
    "transparency": "low",
    "notes": "Enterprise subscription billing with contact-sales pricing; no published tiers, requires human sales engagement."
  },
  "issues": [
    "Pricing is quote-based only — no public tiers, forcing a sales conversation before evaluation.",
    "robots.txt returns 404, indicating incomplete web/SEO configuration and no explicit crawling guidance for agents.",
    "No security headers on responses (potential agent/trust concern, though not blocking).",
    "Auth/onboarding appears enterprise-gated rather than self-serve — hard for an agent to spin up a test account independently.",
    "llms.txt exists (good sign) but is mostly marketing blog index, not API-focused agent guidance."
  ],
  "recommendations": [
    "Publish at least indicative pricing tiers or a free sandbox so agents can evaluate without a sales call.",
    "Fix robots.txt (200) and add security headers to improve trust signals.",
    "Enrich llms.txt with API getting-started, auth, and sandbox links rather than blog content.",
    "Offer a self-serve developer signup (ideally magic-link/SSO) so agents can onboard programmatically.",
    "Surface a public status page with uptime history to strengthen consistency scoring."
  ]
}
```