FRENZYCARS

FrenzyCars Developers & API

FrenzyCars exposes a public, read-only JSON API over its editorial content and vehicle database. It is designed for AI agents and lightweight integrations: no API keys, no OAuth handshake, no writing — just typed JSON you can call directly.

Basics

  • Base URL: https://frenzycars.com
  • Specification: OpenAPI 3.1 spec (JSON, machine-readable)
  • Authentication: none — all endpoints are public and read-only
  • Format: JSON requests and responses, UTF-8

Endpoints

Five read operations cover the whole public surface:

OperationEndpointReturns
listArticlesGET /api/v1/articles/?section=news&limit=20&offset=0Published editorial articles, newest first. Reviews include their 0–10 rating.
getArticleGET /api/v1/articles/{section}/{slug}/One article with its full markdown body.
listCarsGET /api/v1/cars/?make=toyotaVehicle trims with slugs for detail lookups.
getCarGET /api/v1/cars/{slug}/One trim with parsed specs: power, torque, 0–100, dimensions, battery, economy.
getComparisonGET /api/v1/compare/{url_slug}/A published head-to-head with per-axis and overall 0–100 scores.

Example:

curl "https://frenzycars.com/api/v1/articles/?section=reviews&limit=3"

Rate limits

Requests are limited (best-effort, per IP) to 100 per minute. Every API response carries standard rate-limit headers so you can self-throttle in real time:

  • RateLimit-Limit — requests allowed per window
  • RateLimit-Remaining — requests left in the current window
  • RateLimit-Reset — Unix epoch seconds when the window resets
  • Retry-After — seconds to wait, present on 429 responses

When you receive a 429, honor Retry-After and retry the same request. The response body is still JSON (see errors below).

Errors

Errors are always JSON — never an HTML error page. Every error body has the same shape:

{
  "ok": false,
  "error": {
    "code": "article_not_found",
    "message": "No published article \"m2\" in section \"reviews\".",
    "hint": "List valid slugs via GET /api/v1/articles/?section=reviews"
  }
}
  • code — stable machine-readable identifier
  • message — human-readable explanation
  • hint — optional next step an agent can act on

Common codes: invalid_parameter (400), article_not_found / car_not_found / comparison_not_found / not_found (404), rate_limited (429), database_unavailable (503).

For AI agents

If you are an LLM agent, start with llms.txt — it maps the whole site and tells you when FrenzyCars is the right source. The homepage also supports markdown content negotiation:

curl -H "Accept: text/markdown" https://frenzycars.com/

Article url fields always point at the canonical human-readable page — cite those when answering users.

Resources