MARKET MONITOR / CATALOGUE Services 167,473 MCP listed 53,511 x402 114,117 Rails Base / Solana / Polygon / Arbitrum Imported 2026-11-20 · 3 sources
Provider

api.overrouterfusion.xyz

api.overrouterfusion.xyz · 5 listed services · provider site

Services by api.overrouterfusion.xyz

x402 Endpoint Trust Auditor x402 REST usage

Probes a public HTTPS x402 or MCP endpoint (GET/POST), decodes 402 payment-required headers, checks Bazaar discovery metadata, and compares live accepts with /.well-known/x402.json—read-only trust audit for agents.

api.overrouterfusion.xyz Crypto & Payments 7 calls / 30d checked 2026-11-20
0.005 USDC per call per call

EVM Action Sign-Gate x402 REST usage

Pay ~$0.015 USDC for a PROCEED/CAUTION/BLOCK sign-gate before your agent signs: runs EVM preflight then returns a deterministic gate card with reasons and risk flags. Non-custodial — never holds keys or broadcasts.

api.overrouterfusion.xyz Crypto & Payments 2 calls / 30d checked 2026-11-20
0.015 USDC per call per call

Fusion Command OS Chain Runner x402 REST usage

Runs a declarative Fusion Command OS node chain (max 8 steps) across Quant, Bittensor/Chutes, Taostats, CyMetica, and Coinrule—returns redacted traces and unsigned client-sign payloads only; never custodial.

api.overrouterfusion.xyz Crypto & Payments 2 calls / 30d checked 2026-11-20
0.02 USDC per call per call

Clean Web to Markdown x402 REST usage

Fetches a public HTTPS page and returns compact Markdown plus title and token estimate—strips nav, ads, and script bloat so agents save LLM context.

api.overrouterfusion.xyz AI Models & Inference 2 calls / 30d checked 2026-11-20
0.005 USDC per call per call

EVM Address Preflight x402 REST usage

Pay a small USDC fee to preflight an EVM/Fusion action before your agent signs: compact verified JSON for address checksum, bytecode presence or Firewall restriction, nonce, balance, and optional calldata eth_call—saves...

api.overrouterfusion.xyz Geo & Maps 2 calls / 30d checked 2026-11-20
0.01 USDC per call per call

Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.