Counterparty intelligence

The problem it solves

Public identity, verification and bounded research for a counterparty. Doing this manually means gathering the sources, checking they agree, and deciding what the disagreement means - every time you ask.

What a result looks like

A typed result carrying the finding, the evidence roots behind it, freshness stamps and an explicit confidence with its invalidation condition. The schema is compiled into /catalog.json and /openapi.json.

Plain price

Quoted per request

This product is priced from the actual cost of the request by the deterministic quote engine. The live figure is published at /catalog.json.

Freshness and evidence promise

Source-grounded facts are labelled separately from Arbiter's interpretation, and every interpretation carries confidence and what would prove it wrong. Missing evidence is reported as missing.

Try it with x402 / the API

Machines call the canonical payable endpoints - discovery starts atFor Machines, the live contract at /openapi.json, and the catalog at /catalog. Every inbound route resolves to the canonical x402 Revenue Collection Wallet; the address is advertised by the canonical surface, never copied onto this page.

Schema and docs

The result schema, examples, errors and payment semantics are compiled from the canonical catalog: see /catalog and the operation definitions in /openapi.json.

Related products

• Entity resolution
• Public wallet/address snapshot

Monitoring and OEM path

If this is a recurring question rather than a one-off, the matching watch product delivers material changes instead of repeat requests.