$0.001
per call · USD Coin on Base
Semantic search across the entire monitored x402 catalog. Given a free-text query (e.g. "weather forecast", "image generation", "EVM gas price oracle"), returns the closest endpoints by advertised purpose. Ranking is deterministic: cosine similarity bucketed to whole percentage points first (80.3% and 80.5% are the same bucket), then trust score, then described-before-undescribed, then endpoint id. Matches below a 0.5 cosine-similarity floor are dropped entirely, so a query can return fewer than the requested limit (or none). Endpoints that advertise no description are still matched: they are embedded from their service name and URL path tokens instead of a written description (host name as a last resort). The exact effect of a missing description: no fixed point deduction and no direct similarity malus; the only deterministic penalty is the described-before-undescribed tiebreak (at equal similarity bucket AND equal trust score, a described endpoint ranks first). Beyond that it is purely indirect: the shorter fallback text typically yields lower cosine similarity than a prose description, so such endpoints tend to land in lower similarity buckets, by a query-dependent amount. Each match carries its resource URL, trust score, grade, cosine similarity (0-1, raw value; ranking buckets it), advertised description when present, and a free endpoint-page URL. Matches also carry the advertised price as machine-readable fields: amountUsd (null when not advertised) and priceCeiling (true when the endpoint uses the x402 'upto' scheme, i.e. amountUsd is an authorization ceiling and the real charge is typically lower). This is a DISCOVERY product: it deliberately carries no verdict, recommendation or flag detail (the per-endpoint trust report sold at /v1/x402-trust carries those). The query is embedded with the same model as the catalog, so phrasing the capability you need works better than guessing keywords.
Endpoint
POST https://x402.fuchss.app/v1/semantic-search6
Calls / 30d
6
Unique payers / 30d
Sep 9
Last called
exact
Payment scheme
Call this service
import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const fetchWithPay = wrapFetchWithPayment(fetch, account);
const res = await fetchWithPay("https://x402.fuchss.app/v1/semantic-search", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"limit": 25,
"query": "weather forecast"
}),
});
const data = await res.json();curl -X POST \
"https://x402.fuchss.app/v1/semantic-search" \
-H "Content-Type: application/json" \
-d '{"limit":25,"query":"weather forecast"}' \
-H "X-PAYMENT: <signed x402 payment>"Example response
{
"count": 2,
"generatedAt": 1782826208450,
"matches": [
{
"amountUsd": 0.002,
"description": "Hyperlocal weather forecasts, priced per call.",
"endpointPage": "https://x402.fuchss.app/endpoint/12345",
"grade": "A",
"id": 12345,
"priceCeiling": false,
"resource": "https://api.weather.example/v1/forecast",
"score": 88.1,
"similarity": 0.912
},
{
"amountUsd": null,
"description": null,
"endpointPage": "https://x402.fuchss.app/endpoint/12399",
"grade": null,
"id": 12399,
"priceCeiling": false,
"resource": "https://wx.example.net/api/now",
"score": null,
"similarity": 0.874
}
],
"note": "Ranked by cosine similarity, with trust score as a tiebreaker. score/grade are null when the endpoint is not yet scored. No verdict or flag detail here: POST /v1/x402-trust carries those.",
"query": "weather forecast"
}Payment details
0xbbecbe90f28632a9d52ed67b33b43767b8c89285USD Coin · 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913Is this your API?
Pin it to the top of Search & Web and the homepage with a featured placement.
More from Fuchss & similar services
Fuchss · X402 Trust
x402.fuchss.app
Trust score (0-100, grade A-F) for any x402 endpoint -- listed in our catalog or not. Unlike uptime-only checkers, we return ECONOMIC PROOF: the REAL on-chain USDC settlement volume and distinct-payer count for the endpoint's payTo address -- is anyone actually paying it, or is it just live? Computed deterministically from continuous monitoring: 30d probe uptime, 402-envelope spec compliance, latency, observed age, on-chain settlement activity, and advertised-price stability. Includes a full component breakdown, machine-readable flags, and an honest observedDays (we report only the history we actually have, with dataCompleteSince marking our gap-free on-chain coverage). Uncataloged endpoints are live-probed on your first query and auto-adopted into the monitored catalog (first-contact score with low confidence -- history accumulates from there). Know before you pay.
Fuchss · X402 History
x402.fuchss.app
Raw observation history for any publicly listed x402 endpoint: discovery snapshots (listed/delisted/relisted, price changes, payTo changes) and probe time-series (uptime, latency, quoted amount) over the requested window (1-90 days).
Fuchss · Watch Endpoint 30D
x402.fuchss.app
Monitor ONE x402 endpoint for 30 days and get alerted on changes that break agents: payTo changes (critical — possible takeover/rug), price changes, asset/network changes, 402-spec regressions, delisting, and liveness (down/recovered). Account-free: pay, receive a one-time secret + poll URL. Push to multiple signed HTTPS webhooks and/or Slack/Discord incoming webhooks (up to 5 each per watch). Every push URL is connection-tested before payment — unreachable URLs are rejected with no charge. Edit URLs or cancel early for free via bearer-authed PATCH/DELETE /v1/watch/{id}. Poll the append-only event log; nothing is lost between polls.