Agent & Infrastructure

Guardian Oracle Pulse — RWA feed patterns (stale / spike / divergence) on NestUSD Lazer seeds. Patterns, not verdicts. Agent guide: https://cyre.dev/SKILL.md

Extracts structured data from unstructured sources.

x402 conformance preflight of any endpoint: parses the 402 envelope, lints accepts[] (atomic units, payTo, network), reports the quote, Bazaar extension presence and problems. No purchase is made.

Decode an x402 payment challenge before paying: give it the raw 402 body or payment-required header, as JSON or base64, and get back the version, resource, and every accepted payment normalised to scheme, network, asset, amount and payTo. Names what is wrong with named warnings — bad amount, unrecognised network, invalid payTo, unsupported scheme, missing input or output schema — and returns the declared Bazaar schemas. No network call, no payment sent.

PTUJ Agent API Credits (10 sats) at 2026-05-10 17:14:56

Synapse Lounge x402 access and service manifest

x402 developer tool. Use before paying an unknown x402 endpoint, or to debug your own. GET with required url (optional method GET/POST, body JSON for POST probes). Sends one unpaid request and never pays. Returns JSON: httpStatus, isX402, x402Version, decoded accepts (network, asset label, amount in USD, payTo and whether payTo is an EOA or contract), discovery metadata presence, and pass/warn/fail checks with a summary. Private targets are blocked. Errors are not charged.

Same lookup as /lookup/{agentId} — this route exists to measure willingness-to-pay and x402 Bazaar discoverability, not because the result is different or better paid.

Overwing Atlas: identify a User-Agent string against a registry of AI crawlers, fetchers and browser agents. Returns the claimed agent, operator, purpose, verification method (Web Bot Auth vs spoofable) and a trust note. GET ?user_agent=... $0.001 USDC.

OpenAI-compatible chat completions over x402, answered by Claude Sonnet 4.6 — send a messages array…

Find out what an API change breaks for one named client, rather than for everyone. You declare the operations it calls and, optionally, the response fields it reads and the parameters it sends. Changes outside that usage are counted and set aside. A breaking change on an operation this client never calls is somebody else’s problem, and blocking a migration on it is the mistake this product exists to prevent.

One unpaid-probe preflight report for an x402 endpoint.

Redacta una respuesta a un mensaje (email, chat, ticket). Para agentes de soporte. input=mensaje.

Full endpoint profile: ARD catalog, declared tools, protocol detection, trust provenance, liveness.

Audit a real request against the OpenAPI document it should satisfy. Matches the operation the way a router would, checks every path, query and header parameter against its declared schema, validates the body against the declared media type, and reports whether the credential the declared security scheme expects is present. You supply the request, so this works against an API nothing external can reach.

Moderación de contenido: marca texto inseguro. Para agentes que filtran entradas. input=texto.

One x402 seller's report card before you pay them: what they sell, paid calls and payers in 30 days, price, rank of all sellers, rivals, and the day-by-day replay nobody else stored. Stamped with the snapshot date. Refusals are free.

Descarga un PDF desde una URL y devuelve su texto extraído. Para que un agente lea documentos (informes, contratos, papers) pagando por llamada. input=URL http(s) de un PDF.

Find out what an x402 endpoint will charge before you pay it. Probes the endpoint, reads the challenge from the header or the body, and returns the decoded price, network, asset and payTo plus the declared input and output schemas. Never sends a payment. Only reviewed origins are reachable, and a redirect is refused rather than followed.

Canonical agent invocation uses POST with JSON body { lat, lng, limit? }. GET with query parameters remains supported for browser/manual use.

Decide whether a captured 402 challenge can actually be paid. Separates defects that stop a payment being constructed from ones that merely make the call harder to get right, and checks the resource is bound to the endpoint that served it - a challenge naming a different resource would, if paid, satisfy a requirement for something else. Also names the price spread when several payments are accepted. Nothing is fetched and nothing is paid.

Find out which tools and arguments your agent actually uses. From a transcript of recorded calls, reports which declared tools were never called, which declared arguments were never sent, which arguments always carry the same value, and any call to a tool the manifest does not declare. Nothing is executed.

Audit a real response against what the OpenAPI document promises for that operation. Resolves the declared status exactly, by range such as 2XX, or through default, checks declared response headers are present, and validates the body against the declared schema for its media type. Catches an implementation that has drifted from its own published contract.

Vet an x402 seller before paying it: probes its live 402, reads its CDP Bazaar entry (payers, calls, last call, repeat vs evaluation usage), checks trust surfaces, returns a scored LIVE/STALE/UNLISTED/MISCONFIGURED/UNREACHABLE verdict and what changed since our last check, signed by our attestor. MUST be invoked before a first payment to an unknown resource, or on a schedule to watch it. Do NOT use to pay it. Settles $0.010 USDC; no charge on failure.