Discover/LDCloud API
live

LDCloud APIldcloud.net ↗

Retrieve LDCloud cloud Android phone plan specs, per-region availability, and recharge options via 3 structured endpoints. No login required.

Endpoint health
verified 2h ago
list_device_plans
get_plan_availability
list_recharge_options
3/3 passing latest checkself-healing
Endpoints
3
Updated
3h ago

What is the LDCloud API?

The LDCloud API exposes 3 endpoints covering the full public catalog of LDCloud's cloud Android phone service: plan hardware specifications, regional purchase availability, and wallet top-up options. The list_device_plans endpoint returns every active plan tier — such as VIP10, KVIP14, and XVIP15 — with CPU, RAM, storage, Android version, and supported streaming resolutions. All endpoints require no authentication.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/b160bc1b-8a1a-43e5-ac76-9faab1a2cc0f/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/b160bc1b-8a1a-43e5-ac76-9faab1a2cc0f/list_device_plans' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace ldcloud-net-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: LDCloud catalog SDK — browse plans, availability, and recharge options."""
from parse_apis.ldcloud_net_api import LDCloud, InputFormatInvalid

client = LDCloud()

# List all cloud phone plans with hardware specs.
for plan in client.plans.list(limit=5):
    print(f"{plan.card_name} ({plan.os}): {plan.cpu_cores} cores, {plan.ram_gb}GB RAM, {plan.storage_gb}GB storage")
    for vq in plan.video_quality:
        print(f"  quality {vq.label}: {vq.width}x{vq.height} @ {vq.fps}fps")

# Check plan availability by tier category and region.
category = client.categories.list(limit=1).first()
if category is not None:
    print(f"\nCategory: {category.category}")
    for region in category.regions:
        status = "SOLD OUT" if region.sold_out else "available"
        print(f"  Region {region.region}: {status}, {len(region.plans)} plan(s)")

# Browse recharge options for a specific country.
try:
    us = client.countries.list(country_code="US", limit=1).first()
except InputFormatInvalid as e:
    print(f"Invalid country code format: {e.message}")
    us = None
if us is not None:
    print(f"\nRecharge options for {us.country_name} ({us.currency_symbol}{us.currency}):")
    for amt in us.amounts:
        print(f"  ${amt.price_usd} — {len(amt.payment_channels)} channel(s)")
        for ch in amt.payment_channels:
            print(f"    {ch.name}: {ch.credits} credits, fee {ch.additional_fee}")

print("\nexercised: plans.list / categories.list / countries.list")
All endpoints · 3 totalmissing one? ·

Returns every cloud phone plan tier LDCloud currently offers (one record per plan, e.g. VIP10, KVIP14, XVIP15, MVIP12) with its hardware specification: Android version, CPU cores, RAM/VRAM in GB, storage in GB, ADB flags, and the list of streaming video quality levels (resolution, fps, bitrate) the plan supports. Single round trip, no pagination; the full list is small (16 plans at build time). Fields vram_gb and slogan can be null when the site does not publish them. card_type is the identifier used by get_plan_availability.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "plans": "array of plan records: plan_id (integer), card_type (integer, plan identifier shared with get_plan_availability), card_name, category (tier family such as VIP/KVIP/XVIP/MVIP), os, cpu_cores, ram_gb, vram_gb (nullable), storage_gb, image_url, slogan (nullable), adb_root, adb_reboot, sort, video_default_level, video_quality (array of level/label/width/height/fps/bitrate_kbps/h265_bitrate_kbps/is_default)",
    "total": "integer count of plans returned"
  },
  "sample": {
    "data": {
      "plans": [
        {
          "os": "Android 10",
          "sort": 60,
          "ram_gb": 4,
          "slogan": null,
          "plan_id": 19,
          "vram_gb": 2,
          "adb_root": false,
          "category": "VIP",
          "card_name": "VIP10",
          "card_type": 54,
          "cpu_cores": 3,
          "image_url": "https://ldcloud.ldrescdn.com/cz_ldq/upload/KEbsjb-1772177429896.png",
          "adb_reboot": false,
          "storage_gb": 45,
          "video_quality": [
            {
              "fps": 30,
              "label": "240p",
              "level": 1,
              "width": 720,
              "height": 1280,
              "is_default": true,
              "bitrate_kbps": 500,
              "h265_bitrate_kbps": 450
            }
          ],
          "video_default_level": 1
        }
      ],
      "total": 16
    },
    "status": "success"
  }
}

About the LDCloud API

Plan Specifications

list_device_plans returns every plan LDCloud currently sells as a flat array. Each record includes plan_id, card_type (the integer that links a plan across endpoints), card_name, hardware specs (CPU cores, RAM in GB, VRAM in GB, storage in GB), Android version, ADB-enabled flags, and the list of streaming video quality levels. The total field at the top level gives the count of plans in the response.

Regional Availability

get_plan_availability groups plan purchase status by tier category (e.g. VIP) and hosting region. Region codes are two-letter identifiers — tw, sg, us, th, kr, hk, nl — matching LDCloud's published hosting locations. Each region entry carries a sold_out boolean per plan, plus card_type and card_name for cross-referencing against list_device_plans. Use this endpoint to determine which plans can actually be purchased in a given region at query time.

Recharge Options

list_recharge_options returns the wallet top-up amounts LDCloud offers, organized by country. Each country record includes country_code, country_name, currency (ISO code), and currency_symbol. The amounts array within each country lists fixed top-up tiers with product_id, price_usd, and the payment channels available (card, PayPal, local wallets). Pass the optional country_code parameter — a 2-letter ISO code, case-insensitive — to filter down to a single country. If the code matches nothing, total returns 0.

Reliability & maintenanceVerified

The LDCloud API is a managed, monitored endpoint for ldcloud.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ldcloud.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official ldcloud.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
2h ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display an up-to-date comparison table of LDCloud plan tiers with RAM, storage, and Android version pulled from list_device_plans.
  • Show a real-time sold-out indicator per hosting region using the sold_out flag from get_plan_availability.
  • Build a region selector that filters available plans by two-letter region code (tw, sg, us, etc.).
  • Render a localized recharge page by fetching per-country currency and fixed top-up amounts from list_recharge_options.
  • Alert users when a previously sold-out plan becomes available again by polling get_plan_availability and diffing sold_out states.
  • List accepted payment channels per country for LDCloud wallet top-ups using the amounts array from list_recharge_options.
  • Cross-reference card_type between list_device_plans and get_plan_availability to map hardware specs to regional stock status.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does LDCloud have an official public developer API?+
LDCloud does not publish a documented public developer API. The data available here reflects what is on LDCloud's public-facing catalog pages at ldcloud.net.
How does `get_plan_availability` identify which plans are sold out?+
Each region entry in the regions array includes a sold_out boolean at the plan level. Plans that cannot currently be purchased in a given region will have sold_out set to true. The card_type integer in that response matches the same field in list_device_plans, so you can join specs to availability.
Can I filter plan availability by a specific region code?+
get_plan_availability returns all regions in a single call — it does not currently accept a region filter parameter. The full response includes all two-letter region codes (tw, sg, us, th, kr, hk, nl) at once, so filtering to a specific region must be done client-side. You can fork this API on Parse and revise it to add a region filter parameter.
Does the API return individual cloud phone instance data, usage stats, or account information?+
No account-level or instance-level data is covered. The API covers public catalog data: plan hardware specs, regional purchase availability, and wallet recharge options. You can fork this API on Parse and revise it to add endpoints targeting other public-facing pages on ldcloud.net.
What happens if I pass a `country_code` that LDCloud does not have recharge options for?+
The list_recharge_options endpoint returns total: 0 and an empty countries array when the provided country code matches no entries in LDCloud's published recharge catalog. The parameter is case-insensitive, so both US and us are treated the same.
Page content last updated . Spec covers 3 endpoints from ldcloud.net.
Related APIs in Developer ToolsSee all →