Get started
Introduction
Zuse is a maintained, board-verified index of licensed professionals, available over a REST API and an MCP server.
Licensure data is public, but it is scattered across dozens of state and provincial boards, each with its own format, search page, and refresh cycle. Zuse ingests those rosters, normalizes them into one schema, resolves the same person across jurisdictions, and serves the result as a small set of resources.
Resources
| Resource | What it answers | Endpoint | Priced as |
|---|---|---|---|
| Professionals | Who is licensed near this location? | GET /v2/professionals | Nearby |
| Clinics | Which clinics are near this location, and who works there? | GET /v2/clinics | Nearby clinics |
| Practices | Which registered practices are near this location? | GET /v2/practices | Nearby |
| Licenses | Is this person licensed, and is the license in good standing? | GET /v2/licenses | License check |
| People | What licenses does this one person hold? | GET /v2/people/{id} | License check |
| Enrichments | What does the public web say about this person? | POST /v2/enrichments | Background |
| Briefs | What should I know, and say, before I contact this person? | POST /v2/briefs | Intro notes |
| Web searches | Who are the groomers, front desk and kennel staff near here? | POST /v2/web-searches | Web search |
| Contacts | What is this person's email and phone? | POST /v2/contacts | Contact |
| Clinic research | Who owns and runs this clinic, and how do I reach it? | POST /v2/clinic-research | Clinic research |
| Reference data | Specialty types, coverage, your usage. | GET /v2/specialty-types and others | Free |
The same capabilities are exposed as tools on the MCP server.
Names
The console and the website use plain names. The API uses identifiers that do not change. They are the same things:
| Name | Resources | operation in billing and usage | MCP tool |
|---|---|---|---|
| Nearby | professionals, practices | source | source_professionals |
| License check | licenses, people | verify | verify_license |
| Background | enrichments | enrich | enrich_person |
| Intro notes | briefs | brief | research_brief |
| Web search | web-searches | web | find_people_on_web |
| Contact | contacts | contact | find_contact |
| Nearby clinics | clinics | clinics | find_clinics (get_clinic for one, priced as a License check) |
| Clinic research | clinic-research | clinic_research | research_clinic |
One set of rules
Every endpoint follows the same conventions, so learning one teaches the rest:
- Resources are plural nouns.
GETreads,POSTcreates. There are no verbs in paths. - Lists page the same way.
limitandcursorin,pagination.next_cursorout. See Pagination. - Filters and sorting are query parameters, with the same names everywhere:
postal_code,radius_miles,profession,specialty_type,sort. - Responses share one envelope:
data, thenpaginationandmetafor lists, thenbilling. - Every record has an
id, and a reference to another resource is always<resource>_id. - Dates are ISO 8601 (
2027-01-31). Distances are miles and say so in the field name. - Errors share one shape with a stable
code. See Errors. - Retries are safe. Send an
Idempotency-Keyand a repeated request is not charged twice. See Idempotency.
Two layers, kept apart
Zuse returns two different kinds of information and never blends them:
- The verified record: identity and licensure taken from the licensing board of record. Professionals, practices, licenses and people read only from this layer.
- The derived layer: employer, education, public contact details and social profiles gathered from the public web. Enrichments return this layer, marked
"layer": "derived", with a source URL for each field.
If a field came from a board, it is authoritative. If it came from the web, it is a cited best effort and is labeled that way.
Coverage
| Jurisdiction | Professions | Status |
|---|---|---|
| California | Veterinarians, registered veterinary technicians, veterinary assistant permit holders, registered premises | Live |
| Arkansas, Colorado, Illinois, Iowa, Montana, Wisconsin | Veterinarians, veterinary technicians | Live |
| Michigan, Missouri, West Virginia | Veterinarians, veterinary technicians. Current licenses only | Live |
| Alabama, Arizona, Idaho, Kansas, Maryland, Mississippi, Oregon, Washington | Veterinarians, veterinary technicians (and, in Washington, medication clerks). No locations, so License check only | Live |
| Nevada | Veterinarians, veterinary technicians, technicians in training. Names, category and standing only: no license numbers or status | Live |
| Connecticut, Florida, New Jersey, Wyoming | Veterinarians. These states do not license veterinary technicians | Live |
| Massachusetts, Rhode Island, South Dakota, Vermont | Veterinarians | Live |
| Other US states | See GET /v2/coverage for each state's standing | Added as records become available |
GET /v2/jurisdictions returns what is covered right now. A license search for a jurisdiction that is not indexed answers meta.outcome: "jurisdiction_not_indexed" rather than an empty result, so a missing board is never mistaken for a missing license.
Next steps
- Quickstart: make a first call in a few minutes.
- Authentication: create and manage API keys.
- Rate limits and retries: the limits, and how to back off.