SimplyRETS

{
  "service_type": "platform",
  "base_url": "https://simplyrets.com",
  "auth_method": "api_key",
  "auth_config": {
    "notes": "SimplyRETS uses HTTP Basic Authentication with an API key as the username and a secret as the password. Credentials are issued per data feed/subscriber.",
    "header_scheme": "Authorization: Basic <base64(api_key:api_secret)>"
  },
  "endpoints": [
    {
      "name": "Listings",
      "path": "/api/v2/listings",
      "method": "GET",
      "description": "Query active/sold/pending property listings with filters (cities, postalCodes, minPrice, maxPrice, minBeds, maxBeds, minBaths, maxBaths, type, status, limit, offset, sort, vendors, etc.)."
    },
    {
      "name": "Listing by ID",
      "path": "/api/v2/listings/{mlsId}",
      "method": "GET",
      "description": "Retrieve a single listing by MLS ID."
    },
    {
      "name": "Open Houses",
      "path": "/api/v2/openhouses",
      "method": "GET",
      "description": "Query upcoming open houses with date range filters."
    },
    {
      "name": "Office/Agent",
      "path": "/api/v2/agents",
      "method": "GET",
      "description": "Query agent and office data associated with listings."
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "Pricing is not publicly listed and is typically arranged per MLS/data feed and usage volume. Contact SimplyRETS sales for a quote. There is generally a free developer/sandbox tier for testing against sample data.",
      "billing": "Usually monthly subscription with usage tiers based on API calls or listing volume."
    }
  },
  "rate_limits": {
    "notes": "Specific rate limits are not publicly documented in detail; SimplyRETS typically enforces per-account request limits that scale with plan. Best practice is to cache responses and paginate with limit/offset."
  },
  "capabilities": [
    "RESO Web API compliant real estate listings",
    "MLS (Multiple Listing Service) data aggregation across many markets",
    "Live sandbox/test environment in documentation",
    "Property listings search and filtering",
    "Listing detail retrieval by MLS ID",
    "Open house data retrieval",
    "Agent and office/brokerage data",
    "Media/photo URLs for listings",
    "IDX (Internet Data Exchange) data feeds for real estate websites",
    "JSON responses with pagination (limit/offset), sorting, and metadata"
  ],
  "raw_analysis": "SimplyRETS is a real estate data platform that exposes MLS (Multiple Listing Service) listing data through a developer-friendly REST API. It is positioned as the easiest way for developers and real estate agents to build applications — such as IDX websites, property search portals, and real estate analytics tools — on top of live MLS data. The core offering is the v2 API at https://api.simplyrets.com (with documentation hosted at simplyrets.com) that returns RESO-aligned JSON for listings, open houses, and agent/office records.\n\nTarget users: real estate developers, agents, brokerages, and prop-tech companies that need standardized access to MLS data without negotiating bespoke feeds with each MLS directly. SimplyRETS abstracts away many of the inconsistencies between different MLS datasets and vendors.\n\nMaturity: Established vendor in the real estate data/API space with a well-known v2 API, a live interactive documentation environment (the docs page 'makes live requests'), and broad support across many MLSs. It is commonly cited as a go-to MLS API for indie developers and startups.\n\nAuthentication: HTTP Basic Auth using an API key/secret pair rather than a bearer token or OAuth flow. Each subscriber receives credentials scoped to their feed.\n\nEndpoints (documented under /api/v2): listings (with extensive query filters plus limit/offset, sorting, and vendor selection), a single listing endpoint by MLS ID, openhouses, and agents/offices. Responses are JSON with standard RESO fields and pagination metadata.\n\nPricing: Subscription-based and not listed publicly; prospective customers contact sales. A sandbox/developer tier is generally available for building and testing against sample data before connecting a production MLS feed. Costs typically scale with data coverage and request volume.\n\nIntegrations: As a REST/JSON API it integrates with virtually any stack. It is a common data source for IDX/website builders, CRM/real estate marketing tools, and analytics dashboards. Because it conforms closely to RESO Web API conventions, it can also be consumed by RESO-compatible clients.\n\nLimitations: Requires a subscription/contract for production MLS access; no OAuth; rate limits not clearly published; data availability depends on which MLS feeds the account subscribes to."
}

2/3 tests passed

{
  "overall": 70,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 6.5,
    "doc_quality": 7.0,
    "auth_simplicity": 5.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "public_pricing": false,
    "free_tier": "developer/sandbox tier with sample data",
    "note": "Pricing is per MLS/data feed and usage volume; requires sales contact. Typically monthly subscription with usage tiers."
  },
  "issues": [
    "No public pricing — users must contact sales, which slows decision-making and is a common friction point for agents recommending spend.",
    "No llms.txt (404) — missing an LLM-friendly entry point that would improve agent discoverability and onboarding.",
    "Auth/onboarding appears gated behind sales for production access; only a sandbox is freely usable, limiting first-try success.",
    "The platform aggregates MLS data, which carries per-market licensing constraints not fully articulated without account context."
  ],
  "recommendations": [
    "Use the live sandbox to prototype instantly, then scope the specific MLS markets you need before contacting sales.",
    "Expect a quote-only model: budget for per-feed/per-volume subscription pricing rather than self-serve checkout.",
    "Rely on the RESO Web API compliance and JSON/pagination/sorting for structured integration — strong fit for agent tooling and IDX sites.",
    "If an LLM-friendly manifest matters, note the absence of llms.txt and fall back to standard docs/robots.txt for discovery."
  ]
}