LogoLMSpeed
  • Home
  • Free
  • Models
  • Providers
  • Docs
LogoLMSpeed
LogoLMSpeed

The best API speed test tool

GitHubGitHubTwitterX (Twitter)Email
Product
  • Features
  • Pricing
  • FAQ
Leaderboard
  • Overview
  • Speed Ranking
  • Latency Ranking
  • Health Ranking
  • Input Price
  • Output Price
  • Reasoning
  • Coding
Models
  • All Models
  • GPT
  • Claude
  • Gemini
  • DeepSeek
  • Llama
  • Qwen
Free Models
  • All Free Models
  • Free GPT
  • Free Claude
  • Free Gemini
  • Free DeepSeek
  • Free Llama
  • Free Qwen
Resources
  • Speed Test
  • Provider Directory
  • Documentation
Legal
  • Cookie Policy
  • Privacy Policy
  • Terms of Service
© 2026 LMSpeed All Rights Reserved.Made by Nexmoe with ❤️
A

Freddy Greve

Relay

AI API provider offering machine learning and artificial intelligence services.

Freddy Greve offers 6 LLM API models.

Speed benchmark average: 180 tok/s.

Freddy Greve interface preview
OverviewPerformance6HealthEmbed
Avg Speed179.78 tok/s
Latency2.52 s
Updated4/16/2026
Created At12/7/2025
Website

API Endpoints

  • ai-api.freddygreve.com
Unhealthy
Last checked 6/5/2026, 5:45:29 AM
Day
0%
Recent availability
Week
0%
Recent availability
Month
0%
Recent availability
Latency
—

Health Check

1000History (1000 pts)
PastNow

Health history

TimeStatusHourly uptimeLatency
2026-06-050/130%—
2026-06-040/540%—
2026-06-030/540%—
2026-06-020/590%—
2026-06-010/570%—
2026-05-310/600%—
2026-05-300/600%—
2026-05-290/590%—
2026-05-280/540%—
2026-05-270/610%—
2026-05-260/600%—
2026-05-250/610%—
2026-05-240/590%—
2026-05-230/590%—
2026-05-220/570%—
2026-05-210/590%—
2026-05-200/550%—
2026-05-190/590%—

Recent Incidents

TimeStatus CodeLatencyError
6/5/2026, 5:45:29 AM——fetch failed
6/5/2026, 5:15:32 AM——fetch failed
6/5/2026, 4:45:36 AM——fetch failed
6/5/2026, 4:15:27 AM——fetch failed
6/5/2026, 3:55:33 AM——fetch failed
6/5/2026, 3:25:32 AM——fetch failed
6/5/2026, 2:55:35 AM——fetch failed
6/5/2026, 2:25:37 AM——fetch failed
6/5/2026, 1:55:22 AM——fetch failed
6/5/2026, 1:25:33 AM——fetch failed
6/5/2026, 12:55:21 AM——fetch failed
6/5/2026, 12:35:34 AM——fetch failed
6/5/2026, 12:15:18 AM——fetch failed
6/4/2026, 11:55:20 PM——fetch failed
6/4/2026, 11:35:31 PM——fetch failed
6/4/2026, 11:15:19 PM——fetch failed
6/4/2026, 10:55:24 PM——fetch failed
6/4/2026, 10:35:21 PM——fetch failed
6/4/2026, 10:15:15 PM——fetch failed
6/4/2026, 9:55:18 PM——fetch failed

Health Check Rules

  • Check target: the provider's dedicated health check URL, or its website URL as fallback.
  • Request method: HTTP GET with automatic redirect following.
  • Healthy criteria: HTTP status code 200–399 is considered healthy; any other status or network error is unhealthy.
  • Timeout: each check has a 5-second timeout. If the server does not respond within 5 s, the check is marked as failed.
  • Frequency: health checks run periodically via an automated cron job for all providers.

Data as of Apr 16, 2026, 02:44 PM·Rankings are based on community-submitted tests and periodic health probes. Advisory only, not official data.