# HALOWERK identwerk > HALOWERK identwerk liefert maschinenlesbare Ergebnisse gegen Zahlung nach x402. > Netz Base Mainnet, Zahlungsmittel USDC, Empfänger 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E. ## So wird bezahlt 1. Route ohne Zahlungskopf aufrufen. Die Antwort ist 402 und trägt accepts, description und inputSchema. 2. Bedingungen mit einem x402-Client signieren. 3. Aufruf wiederholen, Nachweis im Kopf PAYMENT-SIGNATURE. Eine 402-Antwort kostet nichts und löst keine Arbeit aus. Scheitert die Arbeit, trägt die Antwort charged=false und es wird nicht abgerechnet. ## Endpunkte ### POST /v1/name-resolve Forward resolution takes a name and returns the address it points to, plus the resolver and the owner. ENS names resolve on Ethereum, .base.eth on Base, .sol through the Solana name service. Reverse resolution takes an address and returns its primary name — and always verifies it by resolving that name forward again, because a reverse entry can be set by anyone and is worthless as identity until the forward record agrees; a mismatch is reported rather than hidden. Optional text records (avatar, url, com.twitter and so on) are read for EVM names. Everything runs against public nodes with no key, and several nodes per chain so one outage does not take the service down. A name that resolves is not proof of who holds it. - Preis: 0.002 USDC - MCP-Werkzeug: `name_resolve` - Eingabe: `["name","address","chain","text_keys"]` ### POST /v1/multisig-inspect Reads a Safe from the public transaction service and returns what decides whether it can act: the owner set, the threshold, the current nonce, any enabled modules and the guard contract, and the master copy version. Queued transactions are listed with the confirmations they already carry and the number still missing, so it is visible which of them are one signature away from executing. Modules and a guard are called out explicitly because either can move funds or block execution independently of the threshold — a Safe with a module is not fully described by its owner list. Supports the chains Safe operates a service for. It reads only: nothing is proposed, signed or executed, and a queued transaction is not a prediction that it will pass. - Preis: 0.005 USDC - MCP-Werkzeug: `multisig_inspect` - Eingabe: `["address","chain","include_queued","queued_limit"]` ### POST /v1/aa-simulate Validates a UserOperation structurally and against chain state. It computes the required prefund from the gas limits and fee fields, reads the sender deposit on the EntryPoint and, when a paymaster is set, that paymaster deposit and stake, and says plainly whether the operation is funded. The nonce is read from the EntryPoint and compared with the one supplied, so a stale nonce is caught before submission. The inner call is executed with eth_call from the sender address, and a revert is decoded into Error(string), a named Panic code, or a custom error selector rather than returned as raw hex. This is not bundler validation: a bundler additionally enforces ERC-7562 storage-access rules that cannot be reproduced without a tracing node, so an operation that passes here can still be rejected. Nothing is submitted. - Preis: 0.005 USDC - MCP-Werkzeug: `aa_simulate` - Eingabe: `["user_operation","chain","entry_point","simulate_call"]` ### POST /v1/dao-snapshot Reads a Snapshot space and returns what a voter or an observer needs to act. Per proposal: the choices with their scores and share, total voting power cast, the leading option, the number of voters, the quorum and whether it is met, when voting closes and how much time is left. Scores are marked final or pending — Snapshot computes them asynchronously, and a pending score can still move, so a result read too early is not a result. The space itself reports its voting type, strategies, delay and period, because a score means something different under quadratic than under single-choice weighting. Proposal bodies are truncated to keep the answer usable; the canonical link is always included. Read-only: nothing is voted on, and a leading proposal is not an executed one. - Preis: 0.005 USDC - MCP-Werkzeug: `dao_snapshot` - Eingabe: `["space","state","limit","body_chars"]` ### POST /v1/onchain-identity Reads Ethereum Attestation Service records for an address and sorts them by what they are actually worth. Each attestation carries its issuer, schema, decoded field values, issue time and expiry. The result separates four states that look identical in a raw list: currently valid, revoked by the issuer, expired, and self-issued — an attestation someone wrote about themselves proves nothing and is counted apart rather than mixed into the total. Issuers are aggregated so a single issuer behind many attestations is visible. Direction can be received (attestations about this address) or issued (attestations this address made about others). Available on Base, Ethereum, Optimism, Arbitrum and Sepolia. Nothing here says an issuer is trustworthy: that judgement stays with the caller. - Preis: 0.005 USDC - MCP-Werkzeug: `onchain_identity` - Eingabe: `["address","chain","direction","schema_id","include_revoked","limit"]` ## Weitere Flächen - OpenAPI: https://ident.halowerk.com/openapi.json - Preise: https://ident.halowerk.com/pricing - x402-Manifest: https://ident.halowerk.com/.well-known/x402 - Bazaar: https://ident.halowerk.com/.well-known/x402/bazaar - MCP: https://ident.halowerk.com/mcp ## Missing a capability? If you looked for something this service does not offer, say so. One call, no payment, no sign-up, no account: POST https://bedarf.halowerk.com/capabilities/request Content-Type: application/json {"requested_capability": "what you would buy", "description": "the use case, one sentence", "callback_url": "optional - we call back once it exists"} Only requested_capability is required, 3 to 160 characters. Schema and status: https://bedarf.halowerk.com/openapi.json Submissions are held for review and are never published verbatim.