ZuseDevelopersPricing

    One API.
    Many board formats,
    already handled.

    Bring board-published veterinary credential records into your application. Use REST for your software or MCP for compatible clients. Start with the source, coverage, and response contract.

    Get API access
    curl -G https://api.zuse.live/v2/licenses \
  -H "Authorization: Bearer $ZUSE_KEY" \
  --data-urlencode "name=Jane Doe" \
  -d jurisdiction=CA

    Example configuration. Replace the key in your secure environment.

    The source matters.
    So does what it
    doesn’t tell you.

    A credential record can establish what a board reported. It doesn’t establish job interest, a current workplace, or permission to contact someone. Keep those boundaries clear in the tools you build.

    27 states are indexed as of October 2026. Available professions, fields, and location details vary by board. Confirm the coverage your use case needs and review record freshness where available.

    Frequently
    asked questionsGood to know before you say hello.

    Do I need an AI agent to use Zuse?

    No. REST works with conventional application integrations. MCP is an additional option for compatible clients.

    Does API access include private Talent preferences?

    Do not assume it does. Public board records and Talent account information are separate sources. Review the documented response fields and access terms, or contact the Zuse team about your use case.

    Can I connect Zuse to practice-management software?

    A PIMS add-on is a future direction, not a current feature promised here. Contact the team to discuss a potential integration.

    $10 in starting credit. No card required. Usage-based charges after that.
    Make your first request