Catalog / Retail, marketplaces & classifieds
RETAIL, MARKETPLACES & CLASSIFIEDS · CHILE
Chileautos Vehicle Listings
Collect used and new cars from Chileautos in Chile.
About this data
Collect used and new cars from Chileautos in Chile. Returns unique vehicle rows with numeric CLP prices, kilometres, make, model, trim, year, transmission, fuel, region, seller type, business dealer name, images and listing URL.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/cl/chileautos/listings
Live Chileautos car listings by make, model, region and used/new condition: title, make/model/version, year, price in CLP, kilometres, fuel, transmission, body type, region, condition, seller type and dealer name where published, images and listing URL.
First results page only, up to 20 vehicles, with vehicle details and seller enrichment disabled.
Input
Send a JSON body to POST https://api.ssh.autos/v1/cl/chileautos/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
make | string | optional | up to 80 characters |
model | string | optional | up to 80 characters |
region | string | optional | up to 80 characters |
condition | string | optional | one of used, new, all; default "used" |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 26 fields; a field the source does not publish comes back null.
26 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | — |
listing_key | string | listing key |
make | string | — |
model | string | — |
version | string | — |
year | integer | — |
price_clp | integer | price clp |
price_uf | number | price uf |
km | integer | — |
fuel | string | — |
transmission | string | — |
body_type | string | body type |
colour | string | — |
region | string | — |
city | string | — |
condition | string | — |
seller_type | string | seller type |
dealer_name | string | dealer name (dealer listings only) |
seller_name | string | seller name as shown on the listing card, for dealers and private sellers; null when the card shows no name |
images | array of strings | — |
published_at | string | published at |
url | string | — |
source | string | — |
scraped_at | string | scraped at |
details_parsed | boolean | details parsed |
details_error | string | details error |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/cl/chileautos/listings -m POST -b '{"maxResults": 3}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Chileautos Vehicle Listings Scraper. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt