Trámite (Procedure)

Trámite (Procedure) — connector documentation

• MCP endpoint: https://tramite.connectorbay.com/mcp
• REST API: POST https://tramite.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://tramite.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://tramite.connectorbay.com/health · Tool schemas: https://tramite.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/tramite · agent@connectorbay.com

What Trámite (Procedure) is for

The paperwork questions that come up constantly for anyone living in Mexico — what does my CURP actually mean, what counts as an RFC, what do I need to bring for my INE credential, how do I get a copy of my acta de nacimiento, how long does a passport take — answered as a general orientation, from one local reference, without needing to hunt through several agencies' sites first.

What it does

curp_validator checks whether an 18-character CURP is well-formed — real structure, real check-digit algorithm — and, if it is, decodes the birth date, sex and state of birth encoded in it; if it isn't, it explains exactly what's wrong. curp_info and rfc_info explain what each identifier is, its structure basics, and why it exists. procedure_guide gives a step-by-step overview for five common trámites — the INE voter/photo credential, a passport, a birth-certificate copy (acta de nacimiento), obtaining or looking up a CURP, and RFC registration — each with typical documents and the agency responsible. document_checklist and the deeper required_documents list what to bring; office_directory_hint says which agency generally handles a trámite (RENAPO, SAT, INE, SRE, or the state Registro Civil); estimated_time_cost gives a typical processing-time range and fee tier. procedure_glossary defines the everyday terms — CURP, RFC, homoclave, acta, credencial, trámite, cita, comprobante de domicilio, vigencia, constancia.

What it is not

Not a lookup service, and not legal or official advice. Trámite never checks whether a CURP or RFC is actually issued, registered or belongs to anyone — only whether the format and check digit are correct, and what they decode to. It has no live connection to RENAPO, SAT, INE, SRE or any Registro Civil, and cannot check appointment availability, application status or office hours. Procedures, requirements, fees and processing times change and vary by state and office; always confirm current details directly with the official agency before relying on anything here.

Tools

Identifiers

curp_validator — Check whether a CURP is well-formed (structure and check digit) and, if so, decode the birth date, sex and state of birth it encodes. Explains exactly what's wrong when it isn't well-formed. Never confirms the CURP is registered or real — format and checksum only. Use for "is this CURP valid", "what does this CURP decode to", "what's wrong with my CURP". Args: curp.

curp_info — What a CURP is, who needs one, and why it exists (population registry / birth registration). Use for "what is a CURP", "why do I need a CURP".

rfc_info — What an RFC is, its structure basics (name letters, birth date, homoclave), who needs one, and why (Mexico's tax ID). Use for "what is an RFC", "what does an RFC look like".

Procedures

procedure_guide — A step-by-step overview for a common Mexican trámite — INE voter/photo credential, passport, birth certificate (acta de nacimiento), CURP, or RFC registration — with typical required documents and which agency handles it. Use for "how do I get my INE credential", "steps to get a Mexican passport". Args: name.

document_checklist — The typical documents needed for a given trámite, as a short checklist. Use for "what do I need to bring for my INE credential", "documents for a Mexican passport". Args: procedure.

required_documents — A deeper look at the documents a trámite needs — each item with a note on what it's for or how to get it — plus which agency handles it and where to go. Use for "what exactly counts as proof of address for the INE", "what document proves Mexican nationality for a passport". Args: procedure.

Practical

office_directory_hint — Which agency generally handles a given trámite (RENAPO, SAT, INE, SRE, or the state Registro Civil) and where to go — informational only, not a live office directory or lookup. Use for "who issues passports in Mexico", "which agency handles the CURP". Args: procedure.

estimated_time_cost — A typical processing-time range and fee tier (free / nominal / moderate) for a trámite — heavily caveated, since exact figures change and vary by state and office. Use for "how long does an INE credential take", "is there a fee for the CURP", "how much does a Mexican passport cost". Args: procedure.

Reference

procedure_glossary — Definitions of common Mexican civic-procedure terms (CURP, RFC, homoclave, acta, credencial, trámite, cita, comprobante de domicilio, vigencia, constancia). Use for "what does homoclave mean", "what's a comprobante de domicilio". Args: term.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/tramite/support

Trámite (Procedure) — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Trámite is. Trámite (Procedure) is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for general guidance on Mexican civic procedures: CURP structure decoding, RFC basics, and step/document/agency/time-cost guidance for trámites like the INE credential, a passport, an acta de nacimiento, a CURP, or an RFC. You interact with your assistant; the assistant sends us only the arguments needed for that one request.

What we receive. The arguments of each tool call — which may include a CURP you're asking us to check, a procedure name, or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

A CURP you send is checked in memory and never stored or logged. When you ask curp_validator to check a CURP, it is parsed against a published structural rule and check-digit algorithm entirely in memory on this server, the result is returned, and the CURP itself is discarded immediately afterward. It is never written to a log, never saved to a database, never sent to any third party, and never used to look anyone up — no such lookup exists here. Retention for any identifier you send: none.

Everything else is answered from a bundled, hand-curated reference file. Procedure guides, document checklists, agency information, time/cost guidance and glossary definitions are all local, static data — there is no upstream call at all, live or otherwise.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally; nothing is forwarded anywhere. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in Mexico, California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, and never store what you send to curp_validator at all, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Trámite is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Contact. Unify Dynamics LLC · agent@connectorbay.com

Trámite (Procedure) — Terms of Service

Effective 24 September 2026. These terms govern use of the Trámite (Procedure) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Trámite returns general guidance on Mexican civic procedures: CURP format and check-digit decoding, RFC structure basics, and step-by-step overviews, document checklists, responsible-agency information and typical time/cost tiers for common trámites (the INE voter/photo credential, a passport, an acta de nacimiento, a CURP, and RFC registration), plus a glossary of everyday terms. It is accessed through an AI assistant or directly over MCP or HTTP.
2. General informational guidance only — not legal or official advice. Nothing in the Service is legal, tax or immigration advice, and it is not affiliated with or endorsed by RENAPO, SAT, INE, SRE, any Registro Civil, or the Mexican government. Procedures, required documents, fees and processing times change and vary by state and office. Always confirm current requirements directly with the official agency before relying on anything here.
3. Format checking is not registration checking. A "valid" result from curp_validator means a CURP is well-formed and its check digit is correct — it does not mean the CURP is issued, registered, active, or belongs to any person. The Service performs no such lookup and has no live connection to any government system.
4. Accuracy. Reference content (procedure steps, documents, agencies, glossary) is curated as general guidance and may not reflect the most recent rule changes in every state or office; it is not a substitute for the official agency's own published requirements.
5. Acceptable use. Do not use the Service to attempt to construct, validate at scale, or otherwise generate real people's identifiers. Automated use within the published rate limits is otherwise welcome.
6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
7. Data. Our Privacy Policy describes what we process. In short: a CURP you send is checked in memory and never stored; retention is none.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
9. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any loss arising from relying on general guidance in place of the official agency's current requirements. Our total liability is limited to US $100.
10. Governing law. California law; venue in San Mateo County, California.
11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/tramite

Trámite (Procedure) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://tramite.connectorbay.com/mcp
• REST API: https://tramite.connectorbay.com/openapi.json
• Live status: https://tramite.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Trámite (Procedure) never asks for them.