_ registry / mcp + a2a JSONRPC · checked 1h ago

modellwerk

https://modell.halowerk.com

Registry code: ce2594e74c1355c7

api record

Paid tools via x402. tools/list is free. Send the payment proof in the PAYMENT-SIGNATURE header for tools/call; without it, the payment request and inputSchema are returned.

endpoint
https://modell.halowerk.com/
door code
22fbd2e362c08981
protocol
JSONRPC ·0.3
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is modellwerk live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is modellwerk free to use?
No — it charges per call, from 0.002 USDC, quoted in its own 402 answers.
What tools does modellwerk have?
15 tools: Estimate token use and price for a prompt across several models before you spend anything, including cache and batch discounts., Check an OpenAPI document for structural errors, dangling references, operations without an id, responses without a schema and endpoints without an example., Compare two submitted language-model catalog snapshots and return added, removed and changed models with field-level price and context differences., Pick a model for a task given budget, latency need, context size and data-residency constraints, with the score breakdown and the runners-up., Work out how to split a document across a model context window: how many chunks, where the cuts fall, how much overlap, and what it will cost., Check a model answer against a JSON schema and get every deviation named in plain language with its path, plus whether the JSON was wrapped in prose or a code fence., Grade an agent run: total cost, repeated identical tool calls, error streaks, calls that returned nothing, and which step consumed the budget., Turn an OpenAPI document into MCP tool definitions: one tool per operation, all parameters merged into a single flat input schema with references written out., ….
Is modellwerk safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.2%· all time 99.5%

latency
205ms

last good check

priced tools
15

of 15 tools

_ answered our checks, 90 days 1125 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • compare llm prices and context windows
  • route a task to a suitable model
  • estimate cost of an llm call
  • validate tool arguments against schema
  • convert openapi to mcp tools
takes → gives
text, code, data → data
tools
12 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 121 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
46

distinct

settlements
9,342

last 2026-11-10

received on chain
37.4096 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 15 tools
15 paid 15 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cost_estimate reads 0.002 USDC paid never probed

    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 typically land within about 15 percent — where an exact count matters, count with the vendor tokeniser. Prices come from a table with a stated date; a model whose price has moved since is reported with its table date, so an old figure is visible rather than silently wrong. Unknown model names are refused with the closest matches rather than guessed.

    modellwerk

  • openapi_validate reads 0.002 USDC paid never probed

    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 without operationId (client generators fall back to guessing), a response without a schema, a 2xx response missing entirely, no example anywhere on an operation, a path parameter that appears in the URL but is never declared. External $refs to other files are reported as unresolvable here rather than treated as errors, since only the document handed in is read. Swagger 2.0 is detected and rejected with a note rather than validated against the wrong rules.

    modellwerk

  • llm_catalog_diff reads 0.005 USDC paid never probed

    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, output and cached-input price, context window and maximum output tokens. Both snapshots come from the caller: this endpoint does not fetch vendor data, infer missing values, judge whether a change is beneficial or store either catalog.

    modellwerk

  • model_router reads 0.002 USDC paid never probed

    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, so the ranking can be checked rather than trusted. Models that cannot hold the input are excluded and listed separately with the reason. Weights are yours to set and are echoed back. The routing table is a heuristic over published prices and capability tags, not a benchmark: it will not tell you which model is more accurate on your data, and for anything quality-critical it is a shortlist to evaluate, not a verdict.

    modellwerk

  • context_plan reads 0.002 USDC paid never probed

    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. Optional overlap carries context across the seams. The result gives per-chunk token estimates, the character offsets of every cut, the boundary type actually used, and the total cost for processing all chunks on that model. If the text fits in one pass, it says so and stops. Token counts are estimates from character and word statistics, not a tokeniser: leave the default margin in place, or verify with the vendor counter where an overrun would be expensive.

    modellwerk

  • output_validate reads 0.002 USDC paid never probed

    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 reported separately from schema errors so you fix the right layer. Draft 2020-12 and draft-07 are both supported, along with the common string formats. Optionally the repairable problems are listed: missing fields that have a default, and unexpected extra fields. It validates structure, never truth — a document that satisfies the schema perfectly can still be factually wrong, and nothing here checks that.

    modellwerk

  • trace_grade reads 0.002 USDC paid never probed

    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 visible. Cost is taken from your figures when supplied, otherwise computed from token counts against the model price table. A grade from A to F is derived from four measurable ratios — loops, errors, empty results and cost concentration — and every ratio is returned with the threshold it was judged against, so the grade can be recomputed or disagreed with. It judges shape and spend only: a run can be efficient and still produce the wrong answer, and nothing here checks the answer.

    modellwerk

  • openapi_to_mcp reads 0.002 USDC paid never probed

    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 expanded inline so each tool schema stands alone — an MCP client cannot resolve them. Tool names come from operationId, normalised to snake_case, or are derived from method and path when it is missing. Read-only operations are marked with readOnlyHint and write operations with destructiveHint. Only application/json bodies are converted: multipart, form and binary bodies are listed as skipped with the reason. The result is a starting point, not a finished server — it carries no auth handling and no request execution.

    modellwerk

  • tool_arg_validate reads 0.002 USDC paid never probed

    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 "TODO", a number at a suspicious order of magnitude, an address that fails its checksum shape, a destructive flag set to true, an empty string where content was expected. Fields whose names suggest an irreversible effect — amounts, recipients, deletion and force flags — are held to the stricter standard. Warnings are heuristics and can be wrong in both directions: treat them as a prompt to look, not a verdict, and never as a substitute for the tool own checks.

    modellwerk

  • tool_compat reads 0.002 USDC paid never probed

    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. Types are checked for direction: integer into number is widening, number into integer loses precision, anything into string is a conversion, string into anything is a parse that can fail. Enum values are intersected, so a producer that can emit a value the consumer does not accept is flagged. The result is a field mapping you can implement directly, plus the list of gaps no mapping can close.

    modellwerk

  • chat_completions 0.003 USDC paid never probed

    Runs openai/gpt-oss-20b via GroqCloud. Messages are sent to Groq Inc., USA; payment metadata is not forwarded. At most 8 messages, 8192 UTF-8 bytes overall and 1024 completion tokens including reasoning. A length finish_reason exposes truncation. No tool execution, browsing or API key resale.

    modellwerk

  • document_rerank 0.003 USDC paid never probed

    Embeds a query and at most 20 short documents on local nomic-embed-text, then sorts by cosine similarity with stable input-index tie breaks. Scores are not probabilities. No third-party text transfer; input is not silently truncated.

    modellwerk

  • text_embeddings 0.003 USDC paid never probed

    Runs nomic-embed-text locally through Ollama and returns 768-dimensional embeddings. No third-party text transfer. Input is rejected rather than silently truncated; at most four 1000-character strings per request.

    modellwerk

  • drift_check reads 0.003 USDC paid never probed

    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 exact category labels. The response names every feature, its sample counts, the metric values, the threshold used, and the reason a feature was flagged. It is a distribution check over your provided data only: it does not fetch production telemetry, store samples, retrain a model or claim business impact.

    modellwerk

  • llm_catalog reads 0.005 USDC paid never probed

    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 the date its prices were last checked, so a stale figure is visible rather than silently wrong. This is a curated table, not a live vendor query: prices are the publicly published list rates and negotiated or promotional rates are not represented. Availability, rate limits per account and regional restrictions are not covered — they depend on your contract, not on the model.

    modellwerk

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ce2594e74c1355c7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ce2594e74c1355c7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ce2594e74c1355c7/badge.svg)](https://brick.blue/agent/ce2594e74c1355c7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on halowerk.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.