intelligence

Describe what you want to know in plain language and get back the services worth buying, with price, endpoint, free-sample link and the keywords that matched. A question with several parts, for example 'btc leverage and eurozone inflation', is split into topics and routed separately, and the picks are bundled with a total price. Routing only: nothing is called or purchased, and it matches keywords rather than interpreting the question. Start here when you do not yet know which services you need.

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "description": "Your question or need in plain language, up to 300 characters, for example 'what can move bitcoin next, and when'."
    }
  },
  "required": [
    "question"
  ]
}

Find intelligence services by keyword. Returns id, name, description, family and price for each match. Start here when you know what evidence you need but not which service provides it.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search, for example 'bitcoin leverage' or 'eurozone inflation'."
    },
    "limit": {
      "type": "integer",
      "description": "Maximum results to return (default 25).",
      "minimum": 1,
      "maximum": 100
    }
  },
  "required": [
    "query"
  ]
}

List the families the catalogue is organised into, with a service count for each. Use this to browse when a keyword search is too narrow, or to check coverage of a subject area before committing to a purchase.

{
  "type": "object",
  "properties": {}
}

Look up one service by its id and return its full public record: what it produces, its price, its freshness target, its output schema version and its purchase endpoint. Call this before purchasing so the price and freshness are known rather than assumed. The top result is the exact id match.

{
  "type": "object",
  "properties": {
    "serviceId": {
      "type": "string",
      "description": "The service id, as returned by edge_search_services or a product bundle's sample.serviceId."
    }
  },
  "required": [
    "serviceId"
  ]
}

Fetch a free, illustrative sample of a service's output so the response shape and evidence style can be inspected before paying. The sample is illustrative: treat it as a schema and quality guide, not as current market evidence.

{
  "type": "object",
  "properties": {
    "serviceId": {
      "type": "string",
      "description": "The service id to sample."
    }
  },
  "required": [
    "serviceId"
  ]
}

List the packaged products, each of which composes several specialist services into one buyer outcome, with its free sample and its representative purchase path. Prefer these over assembling specialist services yourself when a product already matches the question.

{
  "type": "object",
  "properties": {}
}

Report per-service availability and data freshness. Call this when a purchase matters and staleness would change the decision: a service can be operational but working from evidence older than its freshness target, which is reported rather than hidden. Omit serviceId for the platform summary; pass one for a single service's probe record.

{
  "type": "object",
  "properties": {
    "serviceId": {
      "type": "string",
      "description": "Optional. A single service's id, for its own probe record instead of the platform summary."
    }
  }
}

Read the live x402 payment terms for a service's report: the price, and one offer per settlement rail, exactly as the paid endpoint issues them. Use this to check a report's cost against your own spend policy before committing. Settlement happens over the plain HTTP endpoint named in the response, not through this tool -- signing a payment needs your own wallet, which no MCP client holds.

{
  "type": "object",
  "properties": {
    "serviceId": {
      "type": "string",
      "description": "The service id whose payment terms you want."
    }
  },
  "required": [
    "serviceId"
  ]
}