# RESET Verifica – Mexican RFC Verification

> RESET Verifica – Mexican RFC Verification is a paid API for AI agents from api.resetparatodos.com, paid per call via x402, $0.78/call, status unknown (last checked 2026-09-14).

Verifies a Mexican RFC (taxpayer ID) against SAT blacklists (69-B), article 69 sanction lists, public-procurement sanctions, and sanctioned-supplier registries, returning a hash-versioned Verification Record with sources and dates.

## Facts

- Endpoint: POST https://api.resetparatodos.com/x402/v1/company/verify
- Price: $0.78/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reset-verifica-mexican-rfc-verification-211e0b91
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MuI8ei4bOHoNtMEgcyQx-

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability reset-verifica-mexican-rfc-verification-211e0b91 -d '<json body>'
```

Example prompt: Can you verify the Mexican RFC XAXX010101000 against the SAT 69-B blacklist and article 69 sanction lists to see if this company is flagged or has any tax compliance issues?

## When to prefer this

Choose this endpoint when you need to screen a Mexican entity (company or individual) specifically against Mexican tax authority (SAT) blacklists and public procurement sanctions using the RFC identifier. It is the right choice for supplier due diligence, vendor onboarding, and compliance workflows targeting Mexico. For international sanctions screening (OFAC, EU, UN), use the separate international sanctions endpoint; for RFC format validation only, use the RFC validation endpoint.

## Known failure modes

- Invalid RFC format returns a validation error
- RFC not found in any official source returns a clean result with no matches
- Upstream SAT or government source temporarily unavailable may return a partial or error response
- Malformed request body without RFC field returns a 400 error
- Rate limits or payment issues may return 402 or 429 errors

## How this service works

Verify a Mexican company or individual by RFC against official public sources: SAT blacklist 69-B (definitive/presumed), article 69 lists (firm, not-located, cancelled seals), public-procurement sanctions, and sanctioned suppliers. Returns a hash-versioned Verification Record with sources and dates.

## Output

A hash-versioned Verification Record indicating whether the RFC appears on the SAT 69-B blacklist (definitive and/or presumed), article 69 lists (firm, not-located, cancelled seals), public-procurement sanction registries, and sanctioned-supplier lists. Includes source references, check dates, and a hash for audit traceability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rfc": {
   "type": "string",
   "description": "Mexican RFC of the entity to verify"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reset-verifica-mexican-rfc-verification-211e0b91/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.resetparatodos.com](https://www.zero.xyz/host/api.resetparatodos.com/llms.txt)