REAL ESTATE · URUGUAY, PARAGUAY, BOLIVIA
InfoCasas Property (UY/PY/BO)
Property listings from InfoCasas across Uruguay, Paraguay and Bolivia.
About this data
Property listings from InfoCasas across Uruguay, Paraguay and Bolivia. Sale and rental searches scoped by optional location; one normalized schema: price and currency, property type, area, rooms, bathrooms, address, images, posting date, URL. On-demand scrape — fresh listings every run.
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/uy/infocasas/listings
Live InfoCasas Uruguay listings for one location, for sale or rent: listing ID, name, price and currency, property type, area in m2, rooms, bedrooms where shown, bathrooms, parking where shown, address, publisher, posting date, images and listing URL.
First results page only, up to 20 listings, with no detail-page enrichment.
Input
Send a JSON body to POST https://api.ssh.autos/v1/uy/infocasas/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
location | string | optional | up to 100 characters; pattern ^[a-z0-9]+(-[a-z0-9]+)*$; default "montevideo" |
operation | string | optional | one of venta, alquiler; default "venta" |
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 21 fields; a field the source does not publish comes back null.
21 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | InfoCasas numeric listing id; not guaranteed unique when datasets are merged, prefer listingKey. |
listingKey | string | Composite unique key: source:id (e.g. infocasas.com.uy:194031228). |
url | string | Canonical listing URL (https://www.infocasas.com.{uy|py|bo}/{slug}/{numericId}). |
name | string | Listing title from the search payload. |
price | number | Advertised price amount as listed; null for hidden/consultar prices. |
currency | string | ISO currency of the advertised price: USD ('U$S' marker), UYU/BOB (bare '$' on uy/bo), PYG ('Gs.' or bare '$' on py). Null when the price is hidden. |
propertyType | string | Property type as named by the site (Apartamento, Casa, Terreno, Lote o Terreno, Local Comercial, Oficina, Chacra o Campo, ...). |
areaM2 | number | Area in m²: built surface first, then total, then terrain (terrenos only carry terrain). |
rooms | integer | Ambientes (rooms) as reported by the site. |
bedrooms | integer | Dormitorios; 0 (monoambientes) is reported as null. |
bathrooms | integer | Baños from the listing payload. |
parkings | integer | Garages/parking spots; null when the listing reports none. |
address | string | Street address (when the listing shows it) plus neighbourhood/city/state, comma-joined. |
publisher | string | Publisher (inmobiliaria or owner) name; null on BO listings that carry no owner block. |
postedAt | string | Listing creation date as ISO YYYY-MM-DD from the payload's created_at. |
images | array of strings | Listing image URLs from the search payload (CDN fragments like '#HASTH' stripped). |
imageUrl | string | Primary listing image URL (the payload's img field, fragment stripped; falls back to the first gallery image). |
operation | string | Requested operation: 'venta' or 'alquiler'. |
country | string | Site country: UY, PY or BO. |
source | string | Source website hostname (infocasas.com.uy/.py/.bo). |
scrapedAt | string | UTC ISO-8601 scrape timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/uy/infocasas/listings -m POST -b '{"location": "montevideo", "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: InfoCasas Property Scraper (UY/PY/BO). 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