We start with a session: write to us from the contact page, we reply to schedule, and from there we move on to validating your company and issuing your credentials.

Yes. After validation you receive courtesy credits to try any endpoint in production, no card and no commitment.

An API key. There are official SDKs in TypeScript, Python and Go, or you can call the REST API directly. The documentation has examples that work as-is.

Yes — we have an MCP (Model Context Protocol) server: your agent can validate a CURP or query any endpoint as a tool call, without you writing an integration. The code lives at github.com/origoid/mcp-server ↗

You choose the configuration: closed (when they run out, queries pause until your next cycle) or open (you keep operating and extra credits are billed individually, at your plan's same per-credit rate).

No — and it's not just a promise: it's design and policy. We don't store the personal data you send: every query is validated, answered and discarded.

Processing runs on redundant infrastructure across multiple regions — that is how we guarantee availability. What matters: data does not stay in any of them. Every query is validated, answered and discarded instantly; there is no database of personal data in any country.

Three things, all with the CURP: whether the person is currently employed and with which employer; their contribution weeks certificate, with the full work history; and their Social Security Number. Compare the three IMSS services.

At a webhook: an address in your system where we send the result when it is ready. When you create the query you get a receipt with an ID, and the result arrives with that same ID. If you have never used one, the webhooks guide explains it step by step.

Most verifications use 1 credit. Some use 2, including IMSS employment verification and NSS lookup, and contribution weeks uses 3. For IMSS queries you are charged when the result resolves; the initial receipt is free.