Kronos Integration Docs

Start free

Discover products and test delayed BTC output without an account, API key or wallet.

Try it now

Free — catalog & full product listing

curl https://kronos.seshat.markets/api/feeds/kronos/catalog

Free — BTC delayed sample (all 5 timeframes)

curl https://kronos.seshat.markets/api/feeds/kronos/sample/btc_usdt

Free — operational risk state

curl https://kronos.seshat.markets/api/feeds/kronos/risk

Read the OpenAPI specification, agent registry and agent quickstart for the complete reference.

How x402 works

Your agent requests a paid endpoint.
Kronos returns HTTP 402 with a signed payment requirement: price, USDC asset, destination and network.
The buyer-controlled wallet signs an authorization.
The client retries with the payment payload and receives the result.

No Kronos account or prepaid Kronos balance is required. The buyer wallet still needs enough USDC for the requested data. Depending on the accepted payment scheme, the facilitator can cover network gas; this does not cover the data price.

Node / TypeScript SDK pattern

Use a buyer wallet that you control. The private key remains in your local runtime and must never be committed, logged or pasted into chat.

import { wrapFetchWithPaymentFromConfig } from '@x402/fetch';
import { ExactEvmScheme } from '@x402/evm';
import { privateKeyToAccount } from 'viem/accounts';

const account = privateKeyToAccount(process.env.BUYER_PRIVATE_KEY);
const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
  schemes: [{ network: 'eip155:84532', client: new ExactEvmScheme(account) }],
});

const response = await fetchWithPayment(
  'https://kronos.seshat.markets/api/feeds/kronos/predict/btc_usdt?timeframes=1h'
);
const forecast = await response.json();

Use the exact network and asset advertised in the live 402 challenge. Never hardcode chain IDs or contract addresses — always read them from the payment requirement returned by Kronos.

Use with MCP

No persistent local installation and no user-hosted server are required. Add the configuration below and npx automatically fetches and starts the lightweight kronos-mcp connector over stdio — there is no port, daemon or infrastructure for the user to maintain. Free tools work without a wallet: kronos_catalog, kronos_sample and kronos_risk. Paid tools can pay automatically only when the operator configures a local buyer signer.

{
  "mcpServers": {
    "kronos": {
      "command": "npx",
      "args": ["-y", "kronos-mcp"]
    }
  }
}

For automated x402 payments, set one or both variables in the local MCP process environment: KRONOS_X402_EVM_PRIVATE_KEY for Base-compatible EVM payments and KRONOS_X402_SOLANA_PRIVATE_KEY for Solana payments. These are buyer secrets; they are never sent to Kronos as private keys.

Prepare an agent wallet

This is a buyer-operated setup, not a Kronos service. Use a wallet or key-management system you already control.

01 Separate the agent wallet

Do not give an autonomous agent access to a personal or treasury wallet. Fund only the amount the operator is prepared to let the agent spend.

02 Fund it with the accepted USDC

Kronos accepts USDC on Base and Solana — the exact network is defined by the current 402 challenge.

03 Keep the key local

Use a local secret store or environment injection. Never commit it, add it to MCP configuration files tracked by git, or provide it to Kronos support.

04 Test first

Use free tools before enabling automated payments.

Agent safety

Review endpoint prices in the catalog before automation.
Use a dedicated wallet and choose its funding level yourself; Kronos does not impose a restrictive daily budget.
Keep the existing API rate limits in mind, especially for GPU playground calls.
Monitor buyer-wallet activity independently and rotate its key if compromise is suspected.
Treat forecasts as research signals, never as trading instructions.