Docs

Integration Paths

Choose the smallest integration path that matches your system: native HTTP, schema-mapped HTTP, Python callable, or agent protocol driver.

Pick A Path

Path

Native HTTP

Best for

Services that can speak Evidpath's domain contract directly.

Domains

recommender, search

Path

Schema-mapped HTTP

Best for

Existing HTTP services whose request or response shape differs from the native contract.

Domains

recommender, search

Path

Python callable

Best for

Local functions, classes, model wrappers, rankers, or agents.

Domains

recommender, search, agents

Path

Agent protocol drivers

Best for

Agent services exposed through model APIs, MCP stdio, LangGraph-style objects, or HTTP sessions.

Domains

agents

Driver Config

Use `--driver-config-path` when a target cannot be represented by a simple native target URL. This is the main path for schema-mapped HTTP and agent protocol drivers.

evidpath audit --domain agents \
  --driver-config-path ./driver_config.json \
  --scenario current-info-tool-use

Source Links

  • Recommender contract: https://github.com/NDETERMINA/limitation/blob/main/products/evidpath/EXTERNAL_TARGET_CONTRACT.md
  • Search contract: https://github.com/NDETERMINA/limitation/blob/main/products/evidpath/EXTERNAL_TARGET_CONTRACT_SEARCH.md
  • Agent contract: https://github.com/NDETERMINA/limitation/blob/main/products/evidpath/EXTERNAL_TARGET_CONTRACT_AGENTS.md
  • Schema-mapped transform example: https://github.com/NDETERMINA/limitation/tree/main/products/evidpath/examples/recommender_schema_mapped_transform