POST /v1/jobs/latam-dossier

Latin American company due-diligence dossier

An agent identifies the company in the official registries (SUNAT, Receita Federal CNPJ, RUES), pulls its record and public-contract history (SEACE, SECOP II), and returns a sourced dossier: identity, status, activities, people, contracts, a short summary and red flags (deregistration, lookalike entities, name changes), each citing its source. Covers: Peru, Brazil, Colombia.

PRICE$0.25 per report, in USDC

RESULTOne sourced JSON report

PAYMENTx402 or MPP · no account

ON APIFYNot on the public Store

ERC-8004 agent profile · agentId 1171168

What you get

Registry facts are copied from the sources, never written by the model.

Give a tax ID, or a name for Peru and Colombia; if a name matches several active companies the dossier lists the candidates instead of guessing (status ambiguous).

Every dossier also screens the company's legal name against the US OFAC SDN list.

Sanctions screening

The example report below screened the company’s names against the OFAC SDN (US Treasury). Its “not checked” list says what it did not cover.

Input

Send a JSON body to POST https://api.ssh.autos/v1/jobs/latam-dossier.

Field	Type	Required	Notes
`country`	string	required	PE (Peru), BR (Brazil) or CO (Colombia) one of `PE`, `BR`, `CO`
`taxId`	string	optional	RUC (PE), CNPJ (BR) or NIT (CO). Brazil requires it. up to 20 characters
`name`	string	optional	Legal name or fragment, when no tax ID is known (PE, CO). 3–120 characters

Returned fields

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

8 fields per record

Field	Type	Notes
`status`	string	found, not_found or ambiguous (several candidates).
`country`	string	PE, BR or CO.
`summary`	string	Short plain-language summary of the company.
`redFlags`	array of objects	Findings worth a second look, each with a severity and its sources.
`candidates`	array of objects	Matching companies when the query is ambiguous.
`sources`	array of objects	Every registry record the dossier cites.
`sanctions`	object	OFAC SDN screening of the legal name.
`notChecked`	array of strings	What could not be checked.

Example call

TERMINAL · $0.25 PER RUN

npx agentcash@latest fetch https://api.ssh.autos/v1/jobs/latam-dossier -m POST -b '{"country": "PE", "taxId": "20100055237"}'

The example values come from the API spec or the actor’s own sample input. Running it is a paid call.

Example report

A real report, captured by calling the endpoint once on 2026-11-07 with {"country": "PE", "taxId": "20100055237"} and saved unchanged. It took 12.6 s. Download the full JSON.

Summary

The RUC 20100055237 resolves to ALICORP SAA, an active, HABIDO open corporation registered with SUNAT since 1992 and operating since 1956 in vegetable and animal oils and fats manufacturing. No SEACE government contract awards were found for 2024 to 2026. The OFAC SDN screen of the legal name and trade name returned no matches.

Registry identity [S1]

Tax id	20100055237
Legal name	ALICORP SAA
Trade name	ALICORP
Status	ACTIVO
Condition	HABIDO
Legal form	SOCIEDAD ANONIMA ABIERTA
Registered on	09/10/1992
Activity started on	16/07/1956
Address	AV. ARGENTINA NRO. 4793 URB. PARQUE INDUSTRIAL PROV. CONST. DEL CALLAO - PROV. CONST. DEL CALLAO - CARMEN DE LA LEGUA REYNOSO
Activities	1040 - ELABORACIÓN DE ACEITES Y GRASAS DE ORIGEN VEGETAL Y ANIMAL

Red flags

None found.

Public contracts [S2]

Years	2024 2025 2026
Award count	0

Sanctions screening

OFAC SDN (US Treasury), list published 2026-11-05. [S3]

ALICORP SAA: no match
ALICORP: no match

Not checked

Named directors and legal representatives were not available from the Peru registry tool, so they were not screened against OFAC.
Only the OFAC SDN list was screened; EU, UK and UN sanctions lists were not checked.
Government contract history was checked only for 2024 to 2026 and only by RUC match.
Financial condition, litigation and beneficial ownership were not checked.

Sources

S1 e-consultaruc.sunat.gob.pe — {"ruc": "20100055237"}
S2 prod4.seace.gob.pe — {"ruc": "20100055237", "years": [2024, 2025, 2026]}
S3 US Treasury OFAC SDN list — {"names": ["ALICORP SAA", "ALICORP"]}

What is and isn’t charged

You pay $0.25 for

An answer, including a definitive “not found” or an empty result.

Free

Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
Not charged when no clean report is produced.
Typical time 5 to 30 s, at most about 2 minutes: set your client timeout to at least 130 s (a client that gives up first is not charged).

How x402 payment works

Your client sends the request. The API answers 402 Payment Required with 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