researchwerk
Registry code: a2cc2abd442b8fb1
Paid tools use x402. tools/list is free. Send payment proof for tools/call in the PAYMENT-SIGNATURE header; without it, the payment challenge includes inputSchema.
- endpoint
- https://research.halowerk.com/
- door code
- b7b6081f5743aedf
- 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 researchwerk live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is researchwerk free to use?
- No — it charges per call, from 0.002 USDC, quoted in its own 402 answers.
- What tools does researchwerk have?
- 15 tools: Search EU public tenders by CPV category, country and publication window, with buyer, place of performance, procedure type and a direct link to each notice., Retrieve protest, conflict and diplomatic reporting for a region and period, ranked by how many independent sources carry each story rather than by recency., Name the authoritative body for a subject and country — law, company registers, statistics, standards, patents, medicines, financial supervision — and judge whether a given URL belongs to an official source, from a curated directory without any web search., Check an answer sentence by sentence against the sources you supply: which statements are covered by a source, which are not, which contain numbers that appear nowhere, and which may contradict the source through a flipped negation., Search academic publications by topic, author or DOI and get title, authors, abstract, citation count, venue and where an open-access full text is available., Find open datasets on the EU data portal with the licence classified for commercial reuse, plus formats, update date and publisher., Judge how much weight a source carries: recency, primary versus secondary, named authorship, publisher type and declared conflicts of interest., Measure media volume and tone around an organisation against its own baseline — explicitly as an attention signal, never as a finding of fact., ….
- Is researchwerk 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.
90 days 99.5%· all time 99.8%
last good check
of 15 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search academic papers
- search european patents
- search eu tenders
- measure news coverage of a topic
- look up archived versions of a url
- takes → gives
- text → data
- tools
- 14 reads
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.
through this hub
successful
what callers paid
distinct
last 2026-11-10
shared-payto
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
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.
tender_search reads 0.005 USDC paid never probed
Searches Tenders Electronic Daily, the EU procurement journal, and returns notices with buyer, title, place of performance, estimated value, procedure type and publication date, each linked to the full notice. Search runs on CPV codes because that is how TED is indexed — free text finds a fraction of what a category search does — and fifteen common categories are mapped to their codes so a caller need not know them. On deadlines, a measured limitation is stated rather than papered over: the search interface does not expose the submission deadline through its flat field set, so where it is absent days_left is null and the count of notices without one is reported; the deadline stands in the linked notice. Only notices published in the journal are covered, so procurement below the EU thresholds, which runs on national portals, is absent entirely.
conflict_events reads 0.006 USDC paid never probed
Searches global news coverage for protest, conflict and diplomatic activity in a region and returns the reporting with source counts, languages, countries of publication and the article links. Ranking is by breadth of coverage rather than by recency, because a story three outlets carry and one three hundred carry look identical in a raw feed, and the number of independent sources is the only signal available here for whether something is significant or merely recent. Language and publishing-country distribution are returned alongside, since a story carried only by outlets in one country is a different kind of finding from one carried across a dozen. The response states throughout that this measures coverage and not events: an increase means more is being written, not that more is happening, and coverage is systematically thinner for regions with fewer monitored outlets, so a quiet result from an under-covered region is not evidence of quiet. Article text is not returned, only metadata and links.
official_sources reads 0.002 USDC paid never probed
Answers the two questions that open any serious piece of research. First, where does something stand officially: filter a curated directory of authorities, registers, standards bodies and intergovernmental organisations by subject and country and get, for each one, what it is actually authoritative for, which is the real answer rather than a bare list of links. Second, is this address official: a URL is matched against the directory and, failing that, against the domain suffixes reserved for state bodies, which reaches far beyond any list since most authorities worldwide sit under one. A directory hit and a suffix hit are reported as different rules with different confidence, because a suffix says the body is official without saying what it is competent for. The endpoint is explicit about its limits in every answer: no hit is never evidence that a source is unofficial, only that it is not confirmed here, since sixty entries cannot represent the authorities of the world and many standards bodies use ordinary domains. It performs no web search and no network access at all, so an entry is a statement about a name, not about the server behind it or whether that server answers today. The directory carries the date it was last maintained.
grounding_score reads 0.002 USDC paid never probed
Splits the answer into sentences and measures, for each one, how much of it is covered by the supplied sources. Coverage is asymmetric on purpose: the question is what share of the statement appears in the source, so a long source can fully cover a short claim, and it combines single-word overlap with word-pair overlap because the same words in a different order can mean something else. Two checks override coverage and this is the point of the endpoint. Negation is compared separately, so a sentence that matches its source almost perfectly but flips a not is reported as a possible contradiction rather than as supported, no matter how high the overlap. Numbers, years, percentages and amounts are extracted and looked for in the matched source, because an invented figure is the most expensive error in a generated answer and the one plain word overlap cannot see, since the sentence around it is correct. German and English decimal styles are folded together so the same number is not counted twice. Every claim carries its best source, its score, the matched phrase and a verdict; the overall grounding_score weights supported at one and weakly supported at one half. The endpoint measures textual coverage, not logical entailment, and supported here means the sentence stands in the source you provided, never that the source is right. No network access and no language model is involved.
paper_search reads 0.005 USDC paid never probed
Searches OpenAlex and Crossref for publications and returns each with its DOI, authors and their affiliations, publication year, venue, abstract, citation count and, where one exists, a direct link to a legally free full text with the licence it is offered under. OpenAlex stores abstracts as an inverted word index rather than text; it is reconstructed here, because the raw structure is unusable. Results can be filtered by year and restricted to open access. Citation counts are a popularity measure, not a quality measure, and they lag: a paper published last month has few citations regardless of merit. Coverage differs by field — well indexed in the natural sciences and computer science, patchier in the humanities and for non-English work — so an absent paper is not evidence it does not exist.
dataset_discovery reads 0.005 USDC paid never probed
Searches the official EU open data portal and returns datasets with what decides whether they are usable: the licence, classified by whether commercial reuse is allowed and what attribution or share-alike it demands. A dataset under a non-commercial licence is marked as unusable for a paid product rather than listd as if equivalent. Each result also carries its publisher, country, last modification date, the distribution formats available and how many there are, and direct links. Filter by format, country or a maximum age, and optionally hide everything that cannot be used commercially. The licence text comes from the portal and is not always the licence on the file itself; where nothing is declared it is reported as unknown, which means reuse is legally uncertain, not permitted.
source_authority reads 0.002 USDC paid never probed
Scores a source along the dimensions that decide whether a claim can rest on it. Recency: how old the material is against how fast the field moves, because a five-year-old figure is fine in history and worthless in pricing. Directness: whether it reports its own research, official record or announcement, or relays someone else — every relay step loses detail and adds interpretation. Attribution: whether a named, identifiable author stands behind it. Publisher: what kind of organisation issued it, read from the domain and from what you supply. Conflict of interest: whether the publisher has a stake in the conclusion, which is the single most under-weighted factor in practice. The result is a score with every deduction itemised and the threshold it was judged against, so the verdict can be recomputed or disagreed with. It judges provenance, never truth: a well-attributed recent primary source can still be wrong.
controversy_pulse reads 0.006 USDC paid never probed
Tracks how much is written about an organisation and in what tone, comparing a recent window against the same term own longer baseline, and returns both the volume ratio and the tone shift with the articles behind them. The framing is fixed and repeated in the response: this is an attention signal and not a judgement. A tone drop means more negative language is being used, not that something happened, and a product recall, a lawsuit and a critical opinion piece produce the same deflection. Tone itself is a machine estimate from word lists and measures the language of articles rather than the situation, which matters most for organisations whose ordinary coverage uses charged vocabulary. Volume and tone are reported separately because they move independently: a rise in volume with unchanged tone is interest, and a tone drop without volume change is a shift in framing among the same outlets. Links to the driving articles are included so the reader can look rather than infer.
narrative_velocity reads 0.006 USDC paid never probed
Computes the growth of coverage for a topic between a recent window and a baseline, and reports the spread across languages and publishing countries alongside it. The spread is the more informative half: a topic exploding in one language is a national event, one rising simultaneously across eight languages is something else entirely, and a growth rate alone cannot tell them apart. The response gives the volume ratio, the number of languages and countries carrying the topic in each period, which languages are new since the baseline, and the concentration of coverage across countries. A topic whose growth comes entirely from additional outlets in one country is marked as such. Because the source measures coverage rather than events, acceleration here describes attention: a topic can grow quickly because it matters or because one large outlet picked it up and others followed, and the country and language spread is what separates those two.
location_heatmap reads 0.006 USDC paid never probed
Returns the geographic places named in coverage of a topic, each with the number of articles mentioning it, the number of distinct sources, and coordinates where the source supplies them. The distinction the service is built on is between mention and occurrence: an article about a decision taken in Brussels affecting mining in Chile names both places, and reading the resulting map as an event map puts the decision in Chile and the mining in Brussels. Places are therefore ranked by how many independent sources mention them rather than by raw article count, since one outlet repeating a location across twenty pieces is one source and not twenty. Coverage is uneven by language and region as everywhere on this source, so a place with few monitored outlets appears small regardless of what happens there. Coordinates come from the source and are returned unmodified; where they are absent the place is still listd with its name rather than dropped.
patent_prior_art reads 0.015 USDC paid never probed
Collects up to 15 recent EP publication candidates from a caller-supplied IPC class through the official EPO Linked Open Data endpoint, embeds concept and title/abstract text locally with nomic-embed-text, and returns the closest matches. The IPC scope prevents a misleading full-corpus keyword scan that times out at the source. Coverage is European publications only and candidate retrieval is not exhaustive. Similarity is a screening signal, not a novelty opinion, freedom-to-operate analysis or legal conclusion.
patent_search reads 0.005 USDC paid never probed
Queries the European Patent Office Linked Open Data endpoint, which is the only patent source still reachable without a key: PatentsView has been retired, and both EPO OPS and the USPTO Open Data Portal answer 403 without credentials. Coverage is therefore EP publications and this is stated in every response, because an empty result here proves only that no European publication exists, not that no patent does. Three search axes are offered and named in the schema: publication number, applicant name, and IPC class with an optional date range. Free text across all titles is deliberately absent, since that query runs into the endpoint timeout rather than returning a slow answer. Each hit carries its titles in all published languages, the abstract where present, applicants and inventors resolved from their vCard records into readable names rather than left as opaque identifiers, and the IPC classes. For a lookup by number the sibling publications of the same application are listd as well, which is where the one defensible status signal comes from: a B kind code means a granted specification exists. That is explicitly not the legal status. Whether a patent is in force today, has lapsed or was opposed lives in the register, which needs a key, so legal_status stays null with the reason attached instead of being inferred from a publication.
web_archive reads 0.005 USDC paid never probed
Queries the Internet Archive for the captured versions of a URL and returns them with capture time, HTTP status, MIME type and content digest, oldest and newest first. Because consecutive captures share a digest when nothing changed, the versions where the content actually differed are marked — that is the list worth reading, not the raw capture log. A target date returns the nearest snapshot with the gap in days, which is what a citation of a page as it stood on a given day needs. Captures that returned an error at the time are separated from successful ones, so a run of 404s reveals when a page disappeared. The CDX index is the complete source but goes down regularly; when it does, the availability endpoint answers with the closest capture and the degraded state is reported rather than passed off as an empty history.
supply_chain_pulse reads 0.007 USDC paid never probed
For each node you name — a port, a plant, a corridor, a supplier — the service counts reporting on five disruption themes over a recent window and compares it against the same term own longer baseline. Self-referential comparison is the design: Rotterdam and a regional port have entirely different normal reporting levels, so a fixed threshold is blind for one and a permanent alarm for the other, and only the ratio against a term own history means anything. Each finding carries the recent count, the baseline rate, the ratio, the theme that rose and links to the articles behind it, so a spike can be read rather than trusted. Themes are kept separate because a strike and a storm call for different responses. As everywhere on this source, what rises is coverage rather than events, and a node in a region with few monitored outlets can be badly disrupted with no signal here at all — stated rather than implied.
web_search 0.02 USDC paid never probed
Runs one Tavily Basic search credit, at most ten results, optional provider-generated answer and no raw-page content. Query goes to Tavily. Provider answers and scores are not verified facts. Fixed one-credit request; no automatic crawl or follow-up calls.
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida2cc2abd442b8fb1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a2cc2abd442b8fb1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a2cc2abd442b8fb1?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
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.
- datenvertrag.halowerk.com datenvertragswerk
- medien.halowerk.com medienwerk
- lauf.halowerk.com laufwerk
- finops.halowerk.com finopswerk
- buero.halowerk.com buerowerk
- seo.halowerk.com seowerk
- commerce-central.halowerk.com commerce-central
- commerce-south.halowerk.com commerce-south
101 more sit on this domain. All of them.