ladewerk
Registry code: 1a4b326bf4d75a1e
Paid tools use x402. tools/list is free. For tools/call, send the payment proof in the PAYMENT-SIGNATURE header; without it the response is the payment challenge with inputSchema.
- endpoint
- https://lade.halowerk.com/
- door code
- c99192ba2db6995c
- 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 ladewerk live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is ladewerk free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ladewerk have?
- 4 tools: E-Bike-Ladepunkte entlang einer übergebenen Route finden., E-Bike-Ladepunkte im Umkreis einer Koordinate suchen., OSM-Details zu einem einzelnen E-Bike-Ladepunkt abrufen., Akku-Reichweite und mögliche Ladehalte entlang einer Route prüfen..
- Is ladewerk 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
- unknown → live
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 115 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-10-20
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.
charging_along_route unknown never probed
Eine zusammenhängende Route als points, Google-Polyline (Genauigkeit 5 oder 6) oder GPX-Track/Route. Bis 300 km, 2000 Punkte und 20.000 km² Suchfläche. Ladepunkte im Korridor von 50 bis 5000 m mit Fortschritt und Luftlinien-Abstand. Kein Routing oder Map-Matching. Endpoint: POST /v1/route.
charging_nearby unknown never probed
OSM-Ladepunkte im Umkreis von 0,1 bis 50 km: Koordinaten, Entfernung, Steckertypen, Zugang, Betreiber, Öffnungszeiten und Gebühren, soweit getaggt. Fahrradtags sind Voraussetzung; unbestätigte Schuko-Punkte können ausdrücklich zugeschaltet werden. Keine aktuelle Belegungsprüfung. Endpoint: POST /v1/nearby.
charging_detail unknown never probed
OSM-Objektkennung node/123, way/123 oder relation/123: Steckertypen, Akku-Schließfach, Kapazität, Öffnungszeiten, Gebühren, Betreiber, Zugang, Roh-Tags, Änderungsdatum und Quellenstand. Nicht erfasste Angaben bleiben null. Keine Live-Verfügbarkeit. Endpoint: POST /v1/detail.
charging_range_check unknown never probed
Akku in Wh, Verbrauch in Wh/km, Startladung und Reserve sowie points, Polyline oder GPX. Liefert ein vereinfachtes Energiemodell mit Ladehalten an OSM-getaggten E-Bike-Punkten und passendem Stecker (Vorgabe Schuko). Vollladung je Halt angenommen. Luftlinien-Abstecher, keine Garantie von Betrieb, Öffnung oder Befahrbarkeit. Endpoint: POST /v1/range.
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 id1a4b326bf4d75a1e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1a4b326bf4d75a1e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1a4b326bf4d75a1e?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
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 116ms
- 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
- —
1 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.
- lauf.halowerk.com laufwerk
- buero.halowerk.com buerowerk
- medien.halowerk.com medienwerk
- seo.halowerk.com seowerk
- commerce-south.halowerk.com commerce-south
- commerce-southeast.halowerk.com commerce-southeast
- commerce-west.halowerk.com commerce-west
- webtechnik.halowerk.com webtechnikwerk
87 more sit on this domain. All of them.