Legal Data Hunter Resolve API

The Resolve API from Legal Data Hunter — 2 operation(s) for resolve.

GitHub OpenAPI

Operations 2

POST /v1/resolve Resolve #
GET /v1/resolve/coverage Resolve Coverage #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/legaldatahunter-com:legaldatahunter-com-resolve-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

legaldatahunter-com-resolve-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Legal Search Resolve API
  description: Hybrid semantic + keyword search over EU legal data (case law, legislation, doctrine).
  version: 0.1.0
tags:
- name: Resolve
paths:
  /v1/resolve:
    post:
      tags:
      - Resolve
      summary: Resolve
      description: 'Resolve a loose legal reference to exact document(s).


        Tries fast-path regex for machine-readable identifiers first,

        then falls back to LLM parsing + SQL query. Capped at

        RESOLVE_BUDGET_SECONDS wall time; overrun returns match_type="timeout".


        TIP: pass `hint_country` (and `hint_type` when known). It roughly doubles the

        resolution rate (~65% vs ~31% without it) — many citation formats are

        ambiguous across the 230+ jurisdictions in the corpus, and the country hint

        scopes resolution to the right one. The resolver is strict (returns nothing

        rather than risk a wrong document), so the hint is often the difference

        between a result and none.


        When the new resolve engine is enabled and no country is passed, the

        service detects it from the reference; if it cannot, the response is

        `resolved: false`, `match_type: "country_required"` with an `error`

        message asking for `hint_country` (same 200 response shape).'
      operationId: resolve_v1_resolve_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ResolveRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /v1/resolve/coverage:
    get:
      tags:
      - Resolve
      summary: Resolve Coverage
      description: 'Pattern coverage report: which sources have resolve patterns and which don''t.


        Merges source_patterns.yaml with the pre-computed manifest to show coverage

        status, pattern counts, and document counts per source.'
      operationId: resolve_coverage_v1_resolve_coverage_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    ResolveRequest:
      properties:
        reference:
          type: string
          maxLength: 2000
          minLength: 1
          title: Reference
          description: Legal reference to resolve (e.g., 'art. 6 code civil')
        hint_country:
          anyOf:
          - type: string
          - type: 'null'
          title: Hint Country
          description: 'LDH jurisdiction code — mostly ISO 3166-1 alpha-2, plus aggregate/supranational codes (e.g. ''FR'', ''DE'', ''BG''; ''EU'' for EU law, ''CoE'' for ECtHR, ''INTL'' for international courts, also ''UN'', ''OECD''). Call discover_countries for the full list. STRONGLY RECOMMENDED: roughly doubles the resolution rate (~65% vs ~31%) by scoping ambiguous citations to the right one of 230+ jurisdictions. Pass it whenever the jurisdiction is known.'
        hint_type:
          anyOf:
          - type: string
          - type: 'null'
          title: Hint Type
          description: 'Type hint: ''legislation'' or ''case_law''. Recommended — further narrows resolution.'
      type: object
      required:
      - reference
      title: ResolveRequest
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError