Austria and Germany's farm-machinery market, with the price a buyer actually sees

price is the gross — the number the listing page prints as its headline and in its structured data — on every row, whatever the dealer typed. price_net is the net, price_gross repeats the gross, vat_rate_pct is the rate (19 for Germany, 20 for Austria, 8.1 for Switzerland in the rows measured) and price_entered_as says whether the dealer typed net or gross. Checked against the listing's own page on 12 listings across seven categories and both indexes: 48 of 48 comparisons agreed.

Because the dealer typed 1 as a stand-in for 'ask us', and the marketplace prints it as 1 €. These listings sort first when you order by price: 8 of the first 100 tractors by ascending price were under 10 euros. They are returned as published with price_symbolic: true, so you can drop them from an average without losing the listing. Real 'price on request' listings come back with price null and price_on_request: true.

No. The marketplace stores 'price on request' as 0, so a price range starting at 0 would quietly mix every one of them in — for tractors, a 0 to 50,000 range is 6,058 listings and 1 to 50,000 is 3,762. A price filter here always starts at 1. Hours and horsepower filters work the same way: they return only listings that state hours or horsepower. One thing to know: the marketplace compares the price the way the dealer typed it, so a dealer who typed a net price can appear slightly above your price_max in gross terms; every price-filtered call says so in meta.warnings.

Up to 10,000 rows, 6 to 100 per page. The marketplace's own total also stops at 10,000 — an unfiltered tractor search says 10,000 while the category tree says 10,862 — so search marks that with total_is_capped and categories gives the exact per-category counts. A call that would page past 10,000 rows is refused with a clear message rather than returning nothing.

listing_type=dealer reads the machinery market of commercial dealers, with a condition (used, demo, new or rental), net and gross price and a full dealer profile. listing_type=private reads private classified ads, which carry the seller's own price and currency, a price option such as 'Preis auf Anfrage', and the date the ad went up. The private index also holds livestock, feed and jobs, so pass group_id=1 to keep to agricultural machinery. detail takes the listing_id and listing_type from any search row as they are.

Mostly Austria and Germany, then Switzerland, Italy, Slovenia and a long tail across Europe; the directory lists dealers in 24 countries. Filter with country (ISO code such as AT, DE or CH) and region by its own name (Bayern, Oberösterreich, Bern). categories lists the countries and their regions with live counts for any query.

The marketplace shows Swiss dealer prices in euros, converted by itself, and does not offer the original franc figure. Those rows carry price_converted: true. The search index and the listing page can hold slightly different conversions — on six Swiss listings the search row was exactly 1 euro below the detail record — so use detail when you need the figure to the euro. Private ads do carry the seller's own currency, with price_eur beside it.

One upstream request per call — two only for a private ad looked up without its listing_type. Over two identical runs of 27 calls across all six actions, every call returned what it should, with a median of 1.2 seconds and the slowest single call 2.4 seconds.

Landwirt.com API is a ReefAPI endpoint group for the austrian, german and swiss farm-machinery market as json: ~85,000 dealer listings and ~50,000 private ads with manufacturer, model, year, operating hours, horsepower, the gross and net price with its vat rate, and the dealer behind every machine. It returns live JSON through POST requests under /landwirt/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Landwirt.com calls use the same shared credit balance as every other ReefAPI engine.

No login to Landwirt.com is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

Landwirt.com actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call landwirt actions with the same key, credit pool and JSON envelope used by normal REST requests.