ssh.autos

Catalog / Tenders & public contracts

TENDERS & PUBLIC CONTRACTS · CHILE

Chile Mercado Público Tenders

Scrape Chilean public tenders from Mercado Publico (ChileCompra): title, buyer with RUT and region, UNSPSC codes, procedure, status, deadline in Chile time, amount, items, awards and…

PER CALL · X402 / MPP From $0.01 per call 1 endpoint at api.ssh.autos. Pay in USDC, no account. See the endpoint
APIFY STORE Public actor Run it with your Apify account: bulk runs, schedules and exports. Open on Apify

About this data

Scrape Chilean public tenders from Mercado Publico (ChileCompra): title, buyer with RUT and region, UNSPSC codes, procedure, status, deadline in Chile time, amount, items, awards and suppliers, documents and notice link. Track new, amended and closed tenders between runs.

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/mercado-publico/tenders

Chilean public tenders from Mercado Público for one month: title, buyer, region, procedure, status and deadline.

PRICE$0.01 per call, in USDC
RESULTUp to 5 per call
PAYMENTx402 or MPP · no account

Input

Send a JSON body to POST https://api.ssh.autos/v1/cl/mercado-publico/tenders.

FieldTypeRequiredNotes
yearintegeroptional2000–2100; default 2026
monthintegeroptional1–12; default 11
keywordstringoptionalup to 200 characters
maxItemsintegeroptional1–5; default 3

Returned fields

The answer is JSON: records, a list of up to 5, and summary, the run status and counts. Each record has these 46 fields; a field the source does not publish comes back null.

46 fields per record
FieldTypeNotes
ocidstringThe procurement's stable OCID, one row per OCID.
tenderIdstringThe Mercado Público licitación code, for example 2409-44-L126.
descriptionExcerptstringWhy the award package could not be read, when that happened.
buyerNamestringWhy the award package could not be read, when that happened.
buyerLegalNamestringWhy the award package could not be read, when that happened.
buyerRutstringWhy the award package could not be read, when that happened.
buyerIdstringWhy the award package could not be read, when that happened.
buyerCodestringWhy the award package could not be read, when that happened.
buyerRegionstringWhy the award package could not be read, when that happened.
buyerAddressstringWhy the award package could not be read, when that happened.
buyerContactNamestringWhy the award package could not be read, when that happened.
unspscCodesarray of stringsUnique UNSPSC codes the buyer attached to the items.
categoriesarray of objectsOne entry per UNSPSC code, with the item description the source publishes.
procurementMethodstringWhy the award package could not be read, when that happened.
procurementMethodDetailsstringWhy the award package could not be read, when that happened.
statusstringWhy the award package could not be read, when that happened.
statusDetailsstringWhy the award package could not be read, when that happened.
publishedAtstringFirst tender release date, ISO 8601 (source UTC).
sourcePublishedDatestringLatest tender package publication date, ISO 8601 (source UTC).
tenderStartAtstringTender period start, ISO 8601 (source UTC).
tenderStartChilestringTender period start in Chile civil time, ISO 8601 with offset.
tenderEndAtstringBid deadline, ISO 8601 (source UTC).
tenderEndChilestringBid deadline in Chile civil time, ISO 8601 with offset.
estimatedAmountnumberEstimated amount the buyer published, in the published currency.
currencystringWhy the award package could not be read, when that happened.
itemsCountintegerNumber of items the source published, or null when it published none.
itemsarray of objectsThe published item list; null unless includeItems is on.
awardsCountintegerNumber of award records the releases expose; 0 when none.
awardsarray of objectsAward records exactly as the award releases publish them.
suppliersarray of objectsWinning suppliers from the award releases, plus parties the source marks as supplier.
documentsarray of objectsAward documents exactly as published.
releaseIdsarray of stringsTender release ids, oldest first.
releaseDatesarrayTender release dates, ISO 8601, oldest first.
releaseTagsarray of stringsTender release tags as published, for example tender and tenderUpdate.
awardReleaseIdsarray of stringsAward release ids, oldest first; null when no award package was read.
awardReleaseDatesarrayAward release dates, ISO 8601; null when no award package was read.
awardReleaseTagsarray of stringsAward release tags as published; null when no award package was read.
awardErrorstringWhy the award package could not be read, when that happened.
noticeUrlstringOfficial Mercado Público notice page.
sourceUrlstringThe source's own tender pointer.
sourcestringalways mercadopublico.cl
scrapedAtstringWhen this row was read.
changeTypestringChanges mode only: new, amended or closed; null in full mode.
one of new, amended, closed
changedFieldsarray of stringsChanges mode only: normalized fields that differ from the last delivered row.
previousValuesobjectChanges mode only: the previous value of each changed field.
closedReasonstringChanges mode, closed rows only: closedBySource when the source closed the tender, leftFilters when it no longer matches the filters, unpublished when the source no longer publishes it. Null otherwise.
one of closedBySource, leftFilters, unpublished

Example call

TERMINAL · $0.01 PER RUN
npx agentcash@latest fetch https://api.ssh.autos/v1/cl/mercado-publico/tenders -m POST -b '{"year": 2026, "month": 11, "maxItems": 2}'

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

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: Chile Mercado Público Tenders 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.

Open on Apify

How x402 payment works

  1. Your client sends the request. The API answers 402 Payment Required with the price and where to pay.
  2. 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.
  3. 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

Some links to Apify are affiliate links. We may earn a commission if you sign up and become a paying customer.