# Tool Compatibility Checker (modell.halowerk.com)

> Tool Compatibility Checker (modell.halowerk.com) is a paid API for AI agents from modell.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Compares a producer tool's output schema against a consumer tool's input schema to determine whether they can be chained, reporting exact matches, synonym-based renames, and missing required fields.

## Facts

- Endpoint: POST https://modell.halowerk.com/v1/tool-compat
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-compatibility-checker-modell-halowerk-com-92f97d9a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RjyVgEt5ab8Sc64Mk9O3X

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability tool-compatibility-checker-modell-halowerk-com-92f97d9a -d '<json body>'
```

Example prompt: Check if I can chain these two tools together — here's the producer's output schema and the consumer's input schema — and tell me which fields match cleanly, which ones need renaming (like url vs uri), and which required consumer fields are missing entirely.

## When to prefer this

Use this endpoint when building or validating multi-step agentic pipelines and you need to confirm that one tool's output can feed directly into another tool's input. It is especially valuable when field names may differ by synonym (url vs uri, id vs key) and you want automated rename detection rather than manual inspection. Prefer this over generic JSON diff tools because it understands agentic tool-chaining semantics and required-field coverage.

## Known failure modes

- Invalid or malformed JSON Schema provided for producer or consumer — returns schema parse error
- Producer or consumer schema missing entirely — returns 400 bad request
- Schema with circular references may cause unexpected behavior
- Very large or deeply nested schemas may increase latency

## How this service works

Compares a producer output schema against a consumer input schema and reports whether the two can be chained. Every required field of the consumer is looked for in the producer: exact name matches first, then well-known synonyms (url/uri/link, id/key/ref, created_at/timestamp and so on), which are reported as renames needing a mapping rather than as clean matches.

## Output

A structured compatibility report indicating whether the producer and consumer schemas can be chained. Includes a list of exact field matches, synonym-based matches flagged as renames (e.g. url↔uri, id↔key), and any required consumer fields that are absent from the producer output, along with an overall chainability verdict.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "use_synonyms": {
   "type": "boolean",
   "default": true,
   "description": "Accept well-known renames as a match."
  },
  "consumer_name": {
   "type": "string",
   "maxLength": 128,
   "description": "Name of the consuming tool, for the report."
  },
  "producer_name": {
   "type": "string",
   "maxLength": 128,
   "description": "Name of the producing tool, for the report."
  },
  "consumer_schema": {
   "type": "object",
   "description": "Input schema of the second tool."
  },
  "producer_schema": {
   "type": "object",
   "description": "Output schema of the first tool."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tool-compatibility-checker-modell-halowerk-com-92f97d9a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from modell.halowerk.com](https://www.zero.xyz/host/modell.halowerk.com/llms.txt)