Agent Tools
Back to directory

HALOWERK modellwerk

https://modell.halowerk.com/v1/drift-check
● healthy a2a-agent

HALOWERK modellwerk. Bezahlung über x402 in USDC auf Base Mainnet.

Category
a2a-agent
Chains
base
Price
$0.0030 USDC / call

Quality grade

How grading works
C+ 60.0 / 100
Availability 40.0 / 40
Endpoint responded (HTTP 402)
Payability 20.0 / 20
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 0.0 / 40
Payment address on record, not yet queried on-chain
Owner verified 0.0 / 3
Nobody has claimed this listing yet
Endpoint last checked 7 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass.

Paid endpoints

12 resource(s) advertised by this origin.

POST https://modell.halowerk.com/v1/drift-check

Compares two submitted sample sets feature by feature and returns deterministic drift metrics. Continuous features are binned on the combined value range and receive PSI, Jensen-Shannon divergence and a Kolmogorov-Smirnov statistic; categorical features receive PSI and Jensen-Shannon divergence over

POST https://modell.halowerk.com/v1/llm-catalog

A comparison table of language models: input, output and cache prices per million tokens, context window, maximum output length, batch discount and a short note on what each is suited to. Filter by vendor, by a maximum price, by the context window you need, or by capability tag. Every row carries th

POST https://modell.halowerk.com/v1/model-router

Scores every catalogue model against one task and returns a ranked shortlist. You state the task kind, optionally a per-call budget in USD, how much speed matters, the input size and any vendor restriction; the answer names a model, the estimated cost per call, and the sub-scores it was chosen on, s

POST https://modell.halowerk.com/v1/cost-estimate

Works out what a call would cost. Give either the text itself or a token count, plus the expected output length, and get input, output, cache-read and cache-write cost per model with the total. Token counts derived from text are estimates from character and word statistics, not a tokeniser, and typi

POST https://modell.halowerk.com/v1/context-plan

Plans the division of a long input for a given model. It reserves room for the system prompt, the expected answer and a safety margin, then works out how many chunks are needed and where to cut, preferring paragraph boundaries over line and sentence boundaries and never cutting inside a word. Option

POST https://modell.halowerk.com/v1/output-validate

Validates output against a JSON Schema and reports each violation with its JSON path, the rule it broke and a sentence saying what to change. Accepts either a parsed object or the raw string a model returned: a payload wrapped in a code fence or surrounded by prose is unwrapped, and the wrapping is

POST https://modell.halowerk.com/v1/trace-grade

Takes the steps of one agent run and returns a scored report. It counts identical tool calls (same tool, same arguments) as loops, finds the longest run of consecutive failures, marks calls whose result was empty or null as wasted, and attributes cost per step and per tool so the expensive part is v

POST https://modell.halowerk.com/v1/openapi-validate

Reads an OpenAPI 3.x document and reports what would stop a machine consumer. Errors: missing openapi, info or paths; a path that declares no method; an internal $ref that resolves to nothing; a parameter without a name, location or schema; a request body without content. Warnings: an operation with

POST https://modell.halowerk.com/v1/openapi-to-mcp

Converts each OpenAPI operation into an MCP tool. Path, query and header parameters and the JSON request body are merged into one input schema, because MCP tools take exactly one; a name collision between a body field and a parameter is reported rather than silently overwritten. Internal $refs are e

POST https://modell.halowerk.com/v1/tool-arg-validate

Two checks in one. First the arguments are validated against the tool input schema and every violation is reported with its path and a sentence saying what to change. Second, values that satisfy the schema but look wrong are flagged: an unset required field filled with a placeholder like "string" or

POST https://modell.halowerk.com/v1/tool-compat

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 r

POST https://modell.halowerk.com/v1/llm-catalog-diff

Use this when an agent has an older and a newer LLM catalog snapshot and needs a deterministic migration diff before changing routing or budgets. Rows are matched by vendor plus model, id or name. The result separates added, removed and changed models and reports field-level differences for input, o

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -X POST https://modell.halowerk.com/v1/drift-check
/.well-known/x402.json
https://modell.halowerk.com/.well-known/x402

Listed in

Directories this entry was found in.

a2a x402