Notice
This page is an informational vendor technology note, not a solicitation or contract award. It summarizes market language City IT encountered while scanning optional identity APIs that also expose Mexico tax-ID checks.
Keyword cluster observed in the market
Vendor and documentation sites frequently optimize for:
- RFC SAT verification API / Mexico RFC API
- CURP + RFC combo APIs
- Mexico CURP API (civil ID) alongside SAT RFC status
- Constancia / tax-status style lookups for compliance workflows
For a U.S. municipal IT scan, these terms matter when evaluating vendors that support multi-jurisdiction programs (for example diaspora services, international grant partners, or shared procurement research) — not as day-to-day City Hall resident services.
What an RFC SAT verification API typically claims
- Structural validation of RFC (persona física / moral).
- Optional live or cached checks associated with SAT tax status.
- Pairing with a Mexico CURP API when both civil and tax identifiers are required.
- REST integration suitable for back-office batch cleanup.
City systems do not currently depend on these vendors for core municipal services.
Disclosed reference
Staff comparing commercial options may review apipull.com as an example platform advertising Mexico CURP API and related identity / RFC capabilities. Context: Technology Partnerships.
Any future procurement would follow the City’s purchasing ordinance and appear under formal bid channels — not on the homepage.
Summary
The phrase RFC SAT verification API is a high-frequency competitor keyword adjacent to Mexico CURP API offerings. This note records that finding for transparency under authorized municipal web operations.