Gerege Verify (XYP)¶
Production · Layer 2 — Lookups ·
Repo: sso-gerege-mn (xyp.gerege.mn/) · xyp.gerege.mn
A lookup service that verifies company and organisation details against the state registry. It consists of a Go API plus a Next.js admin screen.
What it does¶
When ecosystem platforms create an organisation, add a member or grant a permission, they often need to confirm that the organisation actually exists in the state registry. Gerege Verify provides that lookup through a single window.
Typical uses:
- whether an organisation is registered, and whether its name and registration number match,
- who the organisation's authorised officers are,
- whether a given citizen is connected to that organisation.
Structure¶
| Part | Technology | Role |
|---|---|---|
api/ |
Go | Lookup API, client / API-key management, usage counters |
web/ |
Next.js | Admin console — client registration, usage reports |
API model¶
| Path | Purpose |
|---|---|
/v1/* |
The main lookup API — rate limited |
/api/clients |
Client registration (admin) |
/api/usage |
Usage telemetry (admin) |
/health |
Health check |
Access is governed by API keys. Each client has its own key, usage is counted, and the totals are visible in the admin screen.
Why the counters matter
State-registry lookups may be a paid, quota-bound source. Without per-client counting there is no way to allocate cost or detect overuse. There is also an audit requirement to trace who looked up which organisation.
Who uses it¶
- Gerege Platform and Template Platform — in their create/search organisation flows,
- Gerege Wallet — in the organisation-account flow,
- internal admin tooling.
Relationship with X-Road¶
In the long run, inter-organisation lookups are heading towards standardisation on X-Road. Gerege Verify is currently a lookup channel that runs alongside X-Road — once X-Road is fully adopted, some of these lookups may move across.
Full documentation¶
Implementation documentation lives in the xyp.gerege.mn/ directory of the
sso-gerege-mn repository.