The entry point for agents landing on CRYPTYX
The entry point for agents landing on CRYPTYX. Returns the full signal registry (every atomic and composite signal, all versions) with class, horizon, geometry, parameters, 30-day trigger stats, three-axis health grades, walk-forward IS/OOS — plus a meta.service block (universe + walk-forward + macro-regime + OKX/Kraken/Coinbase venues), a meta.by_class strategy-family breakdown, a meta.next recommended 5-step flow, and per-signal _actions with direct URLs to explain / backtest / fork / simulate. One call answers "what is CRYPTYX, what can I buy, and what should I call next". Signal evaluations run across the CRYPTYX 200+ tracked digital assets — BTC, ETH, SOL, top-cap + long-tail coverage.
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://cryptyx.ai/api/signals/catalog
| Category | Company and compliance |
|---|---|
| Provider host | cryptyx.ai |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 2 payers (the provider's figure, not ours) |
Our checks, last 30 days
We never call tools that send, buy, move money or file anything, not even without paying.
Example input (from the provider)
{
"method": "GET",
"queryParams": {},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {},
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}