# Chinese Mini Excavator Specs & Red Flags (`mandarin_nonconformist/chinese-mini-excavator-specs`) Actor

Source-linked specs for long-tail Chinese mini excavators (Rippa, AGT, LTMG, Typhon, Hengwang and more): manufacturer, real operating weight, engine, dig depth, emission claims, conflicts between the maker's own documents, and what listings claim.

- **URL**: https://apify.com/mandarin_nonconformist/chinese-mini-excavator-specs.md
- **Developed by:** [Machine Man](https://apify.com/mandarin_nonconformist) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Chinese Mini Excavator Specs & Red Flags

Source-linked specifications for long-tail Chinese mini excavators that large
spec databases do not cover (Rippa, AGT Industrial, LTMG, Typhon, Hengwang and
more as the database grows).

For each machine you get the manufacturer (factory), operating weight, engine
make/model/power, max digging depth and emission claim. Every value links to
the manufacturer's own document. When the manufacturer's own pages disagree, the
field is marked `conflicting` and all values are listed with their sources; we
never pick one. Unknown values are `null` with status `missing`.

You also get red flags (e.g. listings advertising more horsepower than the
maker states, or a "1.3 ton" name on a 960 kg machine) and what marketplace
listings claim compared with the manufacturer.

### Input

| Field | Example | Notes |
|---|---|---|
| brand | `Rippa` | optional |
| model | `R10` | optional |
| query | `1 ton kubota mini excavator` | optional, matches brand, model and known seller names |
| includeListingClaims | `true` | |
| maxResults | `50` | upper limit of returned machines |

Empty input returns the whole database.

### Pricing

Free during the launch period: you pay only Apify platform usage, which is a fraction of a cent per run.

### Limits

Values are what manufacturers state, not measurements. Emission claims have not
been checked against EPA or EU certification databases. Data is refreshed when
new machines are added; the run summary (`SUMMARY` record) shows the database date.

# Actor input Schema

## `brand` (type: `string`):

e.g. Rippa, AGT, Typhon. Leave empty for all brands.

## `model` (type: `string`):

e.g. R10, QH13R. Leave empty for all models of the brand.

## `query` (type: `string`):

Any words from a listing title, matched against brand, model and known seller names.

## `includeListingClaims` (type: `boolean`):

Add what marketplace listings claim and whether it matches the manufacturer.

## `maxResults` (type: `integer`):

Upper limit of returned machines.

## Actor input object example

```json
{
  "brand": "Rippa",
  "includeListingClaims": true,
  "maxResults": 50
}
```

# Actor output Schema

## `machines` (type: `string`):

Specs, conflicts, red flags and listing claims per machine.

## `summary` (type: `string`):

Database date, machines in database and machines returned.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "brand": "Rippa"
};

// Run the Actor and wait for it to finish
const run = await client.actor("mandarin_nonconformist/chinese-mini-excavator-specs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "brand": "Rippa" }

# Run the Actor and wait for it to finish
run = client.actor("mandarin_nonconformist/chinese-mini-excavator-specs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "brand": "Rippa"
}' |
apify call mandarin_nonconformist/chinese-mini-excavator-specs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mandarin_nonconformist/chinese-mini-excavator-specs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MUcZWBC8s1oDJALrt/builds/aeDcgHbMhPL0EIv81/openapi.json