openapi.llcloud.vip

我的旅行日志 provides an OpenAI-compatible API relay for accessing AI language models via llcloud.vip.

Models
77 models
From
$0.150/M
Speed
--
Updated
6/8/2026
Latency
--
Created At
8/13/2025
Recharge Rate
¥7.30 per $1 quota

Features

DrawingTaskData Export

API Endpoints

  • Endpoint 1Historical / Unverified
    https://llcloud.vip
  • Endpoint 2Historical / Unverified
    https://openapi.llcloud.vip
Claim this provider

Verify ownership to unlock provider management features:

  • Edit provider name, content, and links
  • Get featured with priority traffic and visibility boost
  • Display a verified badge to build user trust

Leaderboard Rankings

Rankings are based on community-submitted tests and periodic health probes. Advisory only, not official data.

About 我的旅行日志

我的旅行日志 is a service for logging travel experiences, offering audio playback capabilities. It includes user authentication (login and registration) and supports background audio playback. The site provides a simple interface for managing travel logs with integrated audio functionality.

Health Check

0%Recent availability
History (72 pts)
PastNow

API Benchmarks & Pricing

Compare 39 model rows across audit recency, latest speed tests, throughput, latency, and per-token pricing.

Model
Input ($/M)
Output ($/M)
$0.500/request-
$0.500/request-
$0.100/request-
$0.100/request-
$0.100/request-
$0.100/request-
$0.500/request-
$0.500/request-
MiniMax-M3default
$0.100/request-
$0.100/request-
$0.100/request-
$0.100/request-
grok-3default
$0.250/request-
$0.250/request-
grok-3-reasonerdefault
$0.250/request-
grok-3-reasonervip
$0.250/request-
grok-3-deepsearchdefault
$0.250/request-
grok-3-deepsearchvip
$0.250/request-
$0.550/M$2.20/M
$0.550/M$2.20/M
$0.100/request-
$0.100/request-
$0.100/request-
$0.100/request-
$0.100/request-

Showing 25 of 39 model rows

Recent Test Records

No test records available

Similar API Provider Alternatives to Compare

Compare 我的旅行日志 alternatives against 6 nearby API providers using 302 LMSpeed signals across shared model coverage, pricing, benchmark speed, uptime, and free-model availability.

ProviderWhy compareModelsFreeAvg priceSpeed30d uptime
我的旅行日志

my-travel-log

我的旅行日志 provides an OpenAI-compatible API relay for accessing AI language models via llcloud.vip.

Current provider baseline770$0.375/MN/A0%
钱多多 API

api2-aigcbest-top

Provides AI-generated content APIs for various applications, including text and image generation.

  • Lower average pricing
  • Higher 30-day availability
  • More free-model options
  • Broader model coverage
1,4182$0.0025/M101 tok/s9940%
Koyeb AI Gateway

new-api-koyeb-app

An OpenAI-compatible API gateway deployed on Koyeb, providing access to multiple AI models.

  • Higher 30-day availability
  • More free-model options
  • Broader model coverage
578420N/A33 tok/s9960%
Yun API

api-zyai-online

Yun API is a high-speed, stable, and high-concurrency API relay service based on official APIs, offering access to over 100 AI models including text, image, and video generation.

  • Lower average pricing
  • Higher 30-day availability
  • Broader model coverage
4310$0.00000342/M32 tok/s9940%
TommyLam API

new-api-tommylam-me

TommyLam API offers an OpenAI-compatible API gateway for accessing multiple AI models at competitive rates.

  • Higher 30-day availability
  • More free-model options
  • Broader model coverage
231100N/A61 tok/s9990%
SMLC666 API

api-smlc666-top

SMLC666 API provides an OpenAI-compatible API relay service with unified access to various AI models.

  • Lower average pricing
  • Higher 30-day availability
  • Broader model coverage
1830$0.240/M43 tok/s9970%
PackyAPI

codex-api-packycode-com

PackyAPI (codex-api.packycode.com) is an OpenAI-compatible API relay for Codex and other models via a single interface.

  • Lower average pricing
  • Higher 30-day availability
  • Broader model coverage
780$0.041/M69 tok/s9980%

Notes

  • Health checks: Scope: the 72-hour chart and recent availability measure API connectivity only. Each bar summarizes one hour of checks. Targets: LMSpeed tries the configured health check URL and provider status URL first, then API endpoints derived from known API hosts and recent speed-test base URLs. A website host is considered only when it looks like an API endpoint. Probe steps: each candidate goes through DNS lookup, TCP connection, TLS handshake for HTTPS, and an HTTP HEAD request with redirects followed. Probing stops after the first reachable candidate. Reachable criteria: every required network step must succeed. An HTTP response below 500 is treated as reachable, including 401 because it confirms that an authenticated API endpoint responded, except for statuses classified as blocked. Blocked results: HTTP 403, 429, 521, 525, and 530, plus detected WAF or Cloudflare challenges, are shown as blocked and excluded from availability calculations because LMSpeed cannot determine whether the API itself is down. Model availability: when a dedicated test key is configured, LMSpeed sends an authenticated GET request to a derived /models endpoint and compares returned model IDs with this provider's listed models. These per-model results appear in Models & Pricing and are not included in the provider connectivity percentage. Timeouts: TCP connection, TLS handshake, HTTP connectivity, and model requests each use a 20-second timeout. A full run can take longer when several candidates are tried. Frequency: a background worker checks all providers every 5 minutes by default. The 72-hour chart combines those samples into hourly bars, and the schedule may be changed by the service operator. Limit: automated samples are not an SLA and do not guarantee account quota, every model, every region, or successful completion requests. Check the provider's own status page before making operational decisions.
  • Domain Rating data is sourced from Ahrefs. It is a 0–100 backlink-based domain strength signal and does not measure API speed or reliability.
  • Announcements and FAQ are read from this provider's NewAPI status snapshot when available. LMSpeed stores the original content and optional English translations from the provider status source, then shows the localized fields on this page.