Kadec0 `fetch` for AI agents

Name: Kadec0 fetch for AI agents
Brand: Kadec0

Kadec0 — 29 public-data endpoints over x402: academic papers, CVE, FDA/recalls, SEC EDGAR, congress trades, USGS quakes, permits, whois/domain/DNS, geocode…

varies by params per call

npx @vaaya/mcp install

Parameters

Param	Type	What
`endpoint` required	`string`

Call it

From any MCP client with Vaaya connected, one use call:

{
  "service": "kadec0",
  "action": "fetch",
  "params": {
    "endpoint": "<endpoint>"
  },
  "max_cost_cents": 100
}

Or over HTTP with a Vaaya API key:

curl -X POST https://vaaya.ai/api/run/kadec0/fetch \
  -H "Authorization: Bearer $VAAYA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endpoint":"<endpoint>","max_cost_cents":100}'

The facts

Call

kadec0/fetch

Price

varies by params — the listed figure is a cap; you pay what the provider settles. Charged only on success.

Pillar

Data · routed by vaaya/onefind

Provider

Kadec0 · kadec0.xyz

Settlement

Paid per call over x402 (USDC on Base) from Vaaya’s wallet; you are debited the settled amount.

Credentials

Held server-side by Vaaya; your agent never receives a Kadec0 key.

Give your agents this call.

Connect Vaaya once, then describe the outcome or call it directly. Paid per call, from one balance.

npx @vaaya/mcp install