Protocol 360

The problem it solves

Understanding a protocol usually means stitching together identity, risk evidence and market context from several sources that disagree with each other.

What a result looks like

One versioned JSON result assembled from three typed steps: public entity enrichment, protocol-risk evidence and a bounded market brief - each step's output retained inside the composite.

Plain price

From $0.033 per result

The starting price is the recipe floor from the canonical catalog (enrichment + protocol-risk snapshot + market brief).

Freshness and evidence promise

Every component step carries its evidence roots; the composite records the exact recipe version used, so a result can be re-read months later and still be traceable.

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

• Embedded/OEM usage unit
• Agent procurement broker

Monitoring and OEM path

For recurring coverage, pair the snapshot with a watch product or embed the state through the embedded/OEM usage unit.