sanbase-metrics

endpoint

https://api.santiment.net/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing

karma

0 · newcomer

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• insight_discovery_tool auth-required 3h ago

  List Santiment insights (analyst-written crypto articles) published in a lookback window. Returns metadata only — id, title, tags, author, link, published_at, prediction — never the article body. ## When to use - The user asks what Santiment analysts have written or published recently. - As step 1 of a two-step read: discover ids here, then pass them to `fetch_insights_tool` for the full text. ## When not to use - Full text of an insight — use `fetch_insights_tool` (it needs ids, so call this tool first). - What the market is talking about right now — use `trending_stories_tool` (stories only) or `combined_trends_tool` (stories + trending words). Insights are human-authored articles, not live social signal. - Numeric metric timeseries for an asset — use `fetch_metric_data_tool`. - Ranking or screening assets by a metric — use `assets_by_metric_tool`. ## Parameters - `time_period` (optional, default `"30d"`) — lookback window as `<integer><unit>`, unit one of `s`, `m`, `h`, `d`, `w`, `y` (e.g. `"12h"`, `"7d"`, `"90d"`, `"1y"`). The window is always `now - time_period` .. `now`; absolute dates and future ranges are not supported. An unparsable value returns an error, not a default. There is no tag, author, asset or full-text filter — filter the returned list yourself. ## Behavior - Read-only: no writes, no state change, nothing destructive. - Requires an authenticated Santiment account (API key or OAuth token); every call counts against the account plan's MCP rate limits. - Returns only published, moderator-approved insights, newest first, hard capped at 100 per call. A wide `time_period` can hit that cap and silently omit the oldest insights — if `total_count` is 100, narrow the window and call again. ## Response JSON object: { "insights": [ { "id": 1234, // integer, feed to fetch_insights_tool "title": "...", "tags": ["BTC", "bitcoin"], // asset tickers/slugs and topics "link": "https://app.santiment.net/insights/read/1234", "published_at": "2025-01-30T10:00:00Z", "author": "username", // "Anonymous" when unset "prediction": "semi_bullish" // heavy_bullish | semi_bullish | // semi_bearish | heavy_bearish | // none | unspecified | null } ], "time_period": "30d", "total_count": 1, "period_start": "2024-12-31T10:00:00Z", "period_end": "2025-01-30T10:00:00Z" } An empty `insights` list with `total_count: 0` means nothing was published in the window — a valid result, not an error.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "time_period": {
        "type": "string",
        "description": "Lookback window as <integer><unit>, unit one of s, m, h, d, w, y\n(e.g. '12h', '7d', '30d', '90d', '1y'). Insights published in\n`now - time_period` .. `now` are returned. Absolute dates and future\nranges are not supported. Defaults to '30d'.\n"
      }
    }
  }

  arguments 9 lines copy
• assets_by_metric_tool auth-required never probed

  A powerful metrics-based project filtering and sorting tool that works with cryptocurrency assets based on their metrics and allows for ordered, paginated results. The tool allows for filtering assets by a metric and sorting them according to that same metric in ascending or descending metric, or just to sort the assets by a metric without filtering. This tool allows you to discover projects that meet specific criteria by analyzing their metrics over time periods. You can filter projects by absolute values (greater_than/less_than thresholds) or by percentage changes, or just sort projects by some metric. ## When to use vs other metric tools This tool scans the whole asset universe and returns one aggregated value per matching asset — use it for "which assets satisfy X" and "top N by X". It never returns a timeseries: for the values of a metric over time for already-known slugs use `fetch_metric_data_tool`. To check that a metric exists (or fix a mistyped metric/slug) use `metrics_and_assets_discovery_tool`. ## Use Cases - Get top 10 assets by marketcap, sorted in descending order - Get top 50 assets with highest dev_activity_1d - Find assets with price more than $10 - Discover tokens whose price increased by more than 50% in the last 30 days - Screen for projects with market cap less than $100M - Identify assets that have dev_activity_1d decline by more than 20% in the past month ## Examples - Get projects that have a price_usd in the last 24 hours and it's greater_than $500. Get the first 20 ordered by price_usd in descending order `{metric: "price_usd", operator: :greater_than, threshold: 500.0, from: "utc_now-24h", to: "utc_now", sort: "desc, page: 1, page_size: 20}` - Find projects whose price_usd today is 25% higher than 7 days ago, sorted by the highest percent increase in descending order. Get the first 100. `{metric: "price_usd", operator: :percent_up, threshold: 25.0, from: "utc_now-7d", to: "utc_now", sort: "desc", page: 1, page_size: 100}` - Projects with current market cap less_than $50M. Get 100 such projects, ordered by marketcap in descending order. `{metric: "marketcap_usd", operator: :less_than, threshold: 50000000.0, from: "utc_now-1d", to: "utc_now", sort: "desc", page: 1, page_size: 100}` Here is how the filtering works: - For absolute value operators - `greater_than` and `less_than` - fetch the `metric` for each asset in the interval `from`-`to`, aggregting it using the specified `aggregation` method (defaulting to the metric's default). - For percent change operators - `percent_up` and `percent_down` - fetch the `metric` for each asset in the interval `from-`to`, as well as in the same length interval immediately before `from`. The two resulting values are compared to calculate the percentage change. Some metrics like price_usd and marketcap_usd are aggregated with `LAST` aggregation by default, meaning that the last known value in the queried interval is used. For percent change, this means that the tool compares the last known price immediately before `from` and the last known price before `to`. Other metrics like transaction_volume_usd and social_volume_total (and most other volume metrics) are aggregated by default with SUM aggregation, meaning that the total combined sum in the queried interval is used. For these metrics length of the time window is vital. A common mistake is to try to check if the social_total_total for the last 5 minutes is greater_than some threshold. Five minutes is not enough for social volume to accumulate enough. In such scenarios use a longer time window like 1 day or more.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374

  {
    "type": "object",
    "required": [
      "sort",
      "from",
      "to",
      "page",
      "metric",
      "page_size"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "End date/time for the analysis period. Defines the end of the time window for metric aggregation.\nAccepts ISO 8601 datetime strings (e.g., \"2024-12-31T23:59:59Z\") or relative time expressions\n(e.g., \"utc_now\" for current time, \"utc_now-1d\" for yesterday). Defaults to current time if not specified.\nMust be after the 'from' date. Used with percentage operators to calculate change over the specified period.\n"
      },
      "from": {
        "type": "string",
        "description": "Start date/time for the analysis period. Defines the beginning of the time window for metric aggregation.\nAccepts ISO 8601 datetime strings (e.g., \"2024-01-01T00:00:00Z\") or relative time expressions\n(e.g., \"utc_now-30d\" for 30 days ago, \"utc_now-1h\" for 1 hour ago)\nDefaults to 30 days ago if not specified. Used with percentage operators to calculate change over time.\n"
      },
      "page": {
        "type": "integer",
        "description": "Page number for paginated results. Used to retrieve specific pages when the result set is large.\nStarts from 1 (first page). Combine with page_size to control how many results are returned per page.\nUseful when only the top 10, 20, 100, etc. assets are needed.\n"
      },
      "sort": {
        "enum": [
          "asc",
          "desc"
        ],
        "type": "string",
        "description": "Sort order for the filtered results based on the aggregated metric values.\n- \"asc\" - Ascending order (lowest values first, e.g., cheapest prices first)\n- \"desc\" - Descending order (highest values first, e.g., most expensive prices first)\n\nParticularly useful when combined with pagination to get the top/bottom performers.\nExample: sort=\"desc\" with price_usd shows highest-priced projects first.\n"
      },
      "metric": {
        "type": "string",
        "description": "The metric to use for screening projects. This determines what aspect of each project will be analyzed.\nCommon metrics include: 'price_usd', 'marketcap_usd', 'volume_usd', 'dev_activity', 'social_volume', 'active_addresses'.\nUse the data catalog to discover all available metrics for comprehensive screening options.\nDiscover the supported metrics with the metrics_and_assets_discovery_tool.\n"
      },
      "operator": {
        "enum": [
          "greater_than",
          "less_than",
          "percent_up",
          "percent_down"
        ],
        "type": "string",
        "description": "Comparison operator that determines how projects are filtered based on the metric and threshold.\n\nAbsolute value operators (compare current values):\n- `greater_than` - Include projects where the aggregated metric value is greater than the threshold\n- `less_than` - Include projects where the aggregated metric value is less than the threshold\n\nPercentage change operators (compare change from 'from' to 'to' period):\n- `percent_up` - Include projects where the metric increased by more than the threshold percentage\n- `percent_down` - Include projects where the metric decreased by more than the threshold percentage\n\n\nIf this parameter is not provided, the threshold parameter also must not be provided. If they are\nnot provided, the tool will simply sort the assets and will do no filtering.\n\nExample: operator=percent_up, threshold=25.0 finds projects that gained more than 25%.\n"
      },
      "page_size": {
        "type": "integer",
        "description": "Number of projects to return per page (max 100). Controls the size of each paginated response.\n"
      },
      "threshold": {
        "oneOf": [
          {
            "type": "integer"
          },
          {
            "type": "number"
          }
        ],
        "description": "The numeric threshold value used for filtering projects. The meaning depends on the operator:\n\nFor absolute operators (:greater_than, :less_than):\n- The actual metric value to compare against (e.g., 10.5 for price_usd greater_than $10.50)\n- Units match the metric (USD for price/market cap, count for addresses, etc.)\n\nFor percentage operators (:percent_up, :percent_down):\n- The percentage change threshold (e.g., 25.0 for 25% change)\n- Always expressed as a positive number regardless of direction\n\nIf this parameter is not provided, the operator parameter also must not be provided. If they are\nnot provided, the tool will simply sort the assets and will do no filtering.\n\nExamples: threshold=50000000.0 with :less_than finds projects with market cap under $50M\n"
      },
      "aggregation": {
        "enum": [
          "min",
          "max",
          "sum",
          "first",
          "last",
          "avg"
        ],
        "type": "string",
        "description": "Method for aggregating metric data over the specified time period. Determines how multiple data points\nwithin the time window are combined into a single value for comparison.\n\nCommon aggregation methods:\n- \"avg\" - Average value over the period (default for most metrics)\n- \"sum\" - Total sum of values (useful for volume, transaction counts)\n- \"max\" - Maximum value in the period (highest price, peak activity)\n- \"min\" - Minimum value in the period (lowest price, minimum activity)\n- \"last\" - Most recent value in the period\n- \"first\" - Earliest value in the period\n\nIf not specified, uses the metric's default aggregation, whichi is carefully selected based on the metric type.\nSome aggregations do not make sense for certain metrics (e.g., summing prices).\nIf not specifically required, using the metric's default aggregation method is recommended.\n"
      }
    }
  }

  arguments 74 lines copy
• combined_trends_tool auth-required 3h ago

  Combined trends tool that fetches trending words, stories, and documents in parallel. This tool provides a unified view of all trending data - words with their documents and stories - in a single response across all crypto projects. ## When to use vs `trending_stories_tool` This is a superset of `trending_stories_tool`: same stories, plus trending words, their context and AI-generated bull/bear summaries. It calls an LLM, so it is slower and has a tighter per-tool rate-limit sub-cap than every other tool. If only trending stories are needed, call `trending_stories_tool` instead; set `include_words: false` / `include_stories: false` to drop a half that is not needed. Do not call both tools for the same question. ## Parameters - `time_period` - Time period for trending data (e.g., '1h', '6h', '1d', '7d'). Defaults to '1h' (last hour). - `size` - Number of items per category to return (max 30). Defaults to 10. - `include_stories` - Include trending stories in response. Defaults to true. - `include_words` - Include trending words in response. Defaults to true. ## Response - `trends` - Combined trending data containing stories and words. - `metadata` - Request metadata including time period, size, and included data types. - `errors` - Any non-fatal errors encountered during data fetching. ## Trending Data Structure ### Stories - `title` - Title of the trending story. - `summary` - Summary of the story. - `score` - Trending score. - `query` - Search query used to find the story. - `related_tokens` - List of related crypto tokens (format: "BTC_bitcoin"). - `bullish_sentiment_ratio` - Bullish sentiment ratio. - `bearish_sentiment_ratio` - Bearish sentiment ratio. ### Words - `word` - The trending word. - `score` - Trending score. - `slug` - Associated project slug (if word is project-related). - `summary` - AI-generated summary of discussions. - `bullish_summary` - Summary of bullish sentiment. - `bearish_summary` - Summary of bearish sentiment. - `positive_sentiment_ratio` - Positive sentiment ratio. - `negative_sentiment_ratio` - Negative sentiment ratio. - `neutral_sentiment_ratio` - Neutral sentiment ratio. - `positive_bb_sentiment_ratio` - Positive bull/bear sentiment ratio. - `negative_bb_sentiment_ratio` - Negative bull/bear sentiment ratio. - `neutral_bb_sentiment_ratio` - Neutral bull/bear sentiment ratio. - `context` - Related words that appear with this trending word. - `documents_summary` - AI-generated summary of related social media discussions.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "properties": {
      "size": {
        "type": "integer",
        "description": "Number of items per category to return (max 30).\n\nDefaults to 10.\n"
      },
      "time_period": {
        "type": "string",
        "description": "Time period for trending data (e.g., '1h', '6h', '1d', '7d').\nThis parameter defines how far back to look for trending data.\n\nDefaults to '1h' (last hour).\n"
      },
      "include_words": {
        "type": "boolean",
        "description": "Include trending words in the response.\n\nDefaults to true.\n"
      },
      "include_stories": {
        "type": "boolean",
        "description": "Include trending stories in the response.\n\nDefaults to true.\n"
      }
    }
  }

  arguments 21 lines copy
• show_chart auth-required 3h ago

  Render a Santiment chart with an asset's price (OHLC) plus an optional overlay metric in a second pane. The widget that consumes this tool is built on the Santiment chart library (lightweight-charts under the hood), so the response is render-ready — the client just feeds each `series` entry into the chart unchanged. ## Parameters - `slug` — asset slug (e.g. `bitcoin`, `ethereum`). Defaults to `bitcoin`. - `primary` — what goes into the main pane. - `"price"` (default) — OHLC candlestick. - any metric name from the catalog — line/area instead of candles. - `overlay` — optional metric name to render in a second pane. Allowed values are listed below. - `range` — `24h`, `7d`, `30d`, `90d`, `1y`. Defaults to `30d`. ## Available overlay metrics (catalog) social_volume_total, social_dominance_total, sentiment_balance_total, sentiment_weighted_total, daily_active_addresses, network_growth, transaction_volume_usd, velocity, mvrv_usd, nvt, realized_value_usd, mvrv_long_short_diff_usd, exchange_balance, whale_transaction_count_100k_usd_to_inf, top_holders_held_supply_percent, dev_activity, github_activity, volume_usd, marketcap_usd, funding_rate_perp.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "Asset slug (e.g. 'bitcoin', 'ethereum'). Defaults to 'bitcoin'."
      },
      "range": {
        "type": "string",
        "description": "Time range. One of: 24h, 7d, 30d, 90d, 1y. Defaults to 30d."
      },
      "overlay": {
        "type": "string",
        "description": "Optional metric to overlay in a second pane. Must be one of the catalog names (see tool description)."
      },
      "primary": {
        "type": "string",
        "description": "Primary series — 'price' for candlestick OHLC, or a metric name from the catalog. Defaults to 'price'."
      }
    }
  }

  arguments 21 lines copy
• fetch_insights_tool auth-required never probed

  Fetch full text content for specific santiment crypto insights IDs

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [
      "insight_ids"
    ],
    "properties": {
      "insight_ids": {
        "oneOf": [
          {
            "type": "array",
            "items": {
              "type": "integer"
            }
          },
          {
            "type": "string"
          }
        ],
        "description": "Array of santiment crypto insights IDs to fetch full content for (max 10)"
      }
    }
  }

  arguments 22 lines copy
• fetch_metric_data_tool auth-required never probed

  Fetch metric timeseries for one metric and one or many slugs. Defaults: last 30 days (time_period="30d"), interval="1d". Use this when the assets are already known and the values over time matter. For the opposite direction — "which assets satisfy X" / "top N by X", one aggregated value per asset across the whole universe — use `assets_by_metric_tool`. To confirm a metric exists for a slug first, use `metrics_and_assets_discovery_tool`; to draw the result, use `show_chart`.

  mcp-tool

  12345678910111213141516171819202122232425262728

  {
    "type": "object",
    "required": [
      "metric",
      "slugs"
    ],
    "properties": {
      "slugs": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "List of slug identifiers (e.g., [\"bitcoin\"], [\"bitcoin\", \"ethereum\"], etc.).\n\nAccepts at most 10 slugs at a time.\n\nOnly metrics that have `supports_many_slugs: true` can accept more than one slug.\nCheck the `supports_many_slugs` field in the metrics_and_assets_discovery_tool response\nbefore passing multiple slugs. Financial and on-chain metrics generally support multiple\nslugs; social, sentiment, and derivatives metrics generally do not.\n\nThe tool returns data for one metric and one or many slugs.\n"
      },
      "metric": {
        "type": "string",
        "description": "Metric name to fetch (e.g., 'price_usd').\n\nIMPORTANT: Before fetching data, verify metric names by calling the\nmetrics_and_assets_discovery_tool first. Only metrics listed there are supported.\nDo not guess or infer metric names — they may differ from what you expect.\n"
      },
      "interval": {
        "type": "string",
        "description": "The interval between two data points in the timeseries data (e.g., '5m', '1h', '1d').\n\nThe format is: <number><suffix>, where:\n- <number> is an integer\n- <suffix> is one of:\n  - m (minutes)\n  - h (hours)\n  - d (days)\n  - w (weeks)\n  - y (years)\n\nFor example, 5m means that the data returned will have a 5 minute interval between two data points.\n\nEach metric has predefined `min_interval`. It describes the lowest possible interval for which data is available.\nIf the metric has `min_interval=1d` it means that Santiment has one data point per day for that metric. For these\nmetrics `interval=\"5m\"` won't work as 5 minutes is less than 1 day.\n"
      },
      "time_period": {
        "type": "string",
        "description": "How far back in time to fetch the data for (e.g., '7d', '30d', '90d').\nThis parameter defines the range of metric data to fetch - from <time_period> time\nago up until now.\n\nDefaults to 30d.\n"
      }
    }
  }

  arguments 28 lines copy
• metrics_and_assets_discovery_tool auth-required never probed

  Catalog lookup: which metrics and which crypto assets (slugs) Santiment supports, and whether a given metric exists for a given asset. Returns names and metadata only — it never returns metric values or timeseries. ## When to use - Resolve a name before any data call: turn "Ethereum" into the slug `ethereum`, or "active addresses" into the metric `daily_active_addresses`. - Check availability before calling `fetch_metric_data_tool`, `assets_by_metric_tool` or `show_chart`, so a bad slug/metric does not waste a data call. - Recover from a "metric/slug not supported" error from any other tool. ## When not to use - Actual metric values over time — use `fetch_metric_data_tool`. - Ranking, filtering or screening assets by a metric value — use `assets_by_metric_tool`. - Rendering a chart — use `show_chart`. - Trending words/stories or insights — use `combined_trends_tool` or `insight_discovery_tool`. Those data sets are not in this catalog. ## Parameters Both parameters are optional and the four combinations do four different things: | Arguments | Returns | |----------------------------|---------------------------------------------------| | `{}` | Every supported metric and every supported asset | | `{"slug": ...}` | All metrics available for that one asset | | `{"metric": ...}` | All assets that support that one metric | | `{"slug":..., "metric":...}`| Whether that exact pair is available (validation) | - `slug` — lowercase, hyphen-separated asset id: `"bitcoin"`, `"ethereum"`, `"avalanche"`. Not a ticker: use `"bitcoin"`, not `"BTC"`. One slug per call; lists are not accepted. - `metric` — lowercase snake_case metric id: `"price_usd"`, `"marketcap_usd"`, `"daily_active_addresses"`. One metric per call. Examples: {} {"slug": "ethereum"} {"metric": "price_usd"} {"slug": "bitcoin", "metric": "daily_active_addresses"} ## Behavior - Read-only: no writes, no state change, nothing destructive. - Requires an authenticated Santiment account (API key or OAuth token); every call counts against the account plan's MCP rate limits. - Results are cached server-side, so the catalog can lag a newly listed asset by a few minutes. - Large responses (notably `{}`, which covers ~500 assets) are truncated to stay under the client token limit. When that happens the response carries `"truncated": true` plus `"truncation_notice"`, and the counts are adjusted to what was actually returned — pass `slug` or `metric` to get a complete answer instead of a truncated one. ## Response Always a JSON object. Its shape depends on the arguments. `{}` — full catalog: { "metrics": [{"name": "price_usd", "description": "...", "unit": "USD", "supports_many_slugs": true, "min_interval": "1m", "default_aggregation": "last", "documentation_urls": [{"url": "..."}]}], "assets": [{"name": "Bitcoin", "slug": "bitcoin", "ticker": "BTC"}], "metrics_count": 120, "assets_count": 500, "description": "..." } `{"slug": ...}` — `{"slug", "metrics" (same metric objects as above), "metrics_count", "description"}`. `{"metric": ...}` — `{"metric", "assets" (same asset objects as above), "assets_count", "description"}`. `{"slug": ..., "metric": ...}` — on success `{"slug", "metric": <metric object>, "available": true, "description"}`. Unsupported input is reported inside a successful response, not as a tool error: an unknown `slug` yields `{"error": "...", "available_assets": [...]}`, an unknown `metric` yields `{"error": "...", "available_metrics": [...]}`. There is no `"available": false` — read `error`. Error messages include a fuzzy suggestion for near-miss metric names (`price_uds` -> `price_usd`), so retry with the suggested name.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "Santiment slug of one crypto asset: lowercase, hyphen-separated, e.g.\n'bitcoin', 'ethereum', 'avalanche'. Not a ticker - use 'bitcoin', not\n'BTC'. One slug per call; lists are not accepted.\n\nAlone: returns all metrics available for this asset. With `metric`:\nchecks only whether that metric exists for this asset. Omit both to list\nthe whole catalog.\n"
      },
      "metric": {
        "type": "string",
        "description": "Santiment id of one metric: lowercase snake_case, e.g. 'price_usd',\n'marketcap_usd', 'daily_active_addresses'. One metric per call; lists are\nnot accepted.\n\nAlone: returns all assets that support this metric. With `slug`: checks\nonly whether this metric exists for that asset. Omit both to list the\nwhole catalog.\n"
      }
    }
  }

  arguments 13 lines copy
• trending_stories_tool auth-required 1h ago

  Fetch current trending crypto stories with sentiment analysis ## When to use vs `combined_trends_tool` Prefer this tool when only stories are needed: it is the cheap, fast path and has no per-tool rate-limit sub-cap. `combined_trends_tool` is a superset — same stories plus trending words, their context and AI-generated bull/bear summaries — but it calls an LLM, so it is slower and capped much lower per plan. Use it only when trending *words* or those summaries are actually needed, and never call both for the same question. ## Parameters - `time_period` - Time period for trending stories (e.g., '1h', '6h', '1d', '7d'). Defaults to '1h' (last hour). - `size` - Number of trending stories to return (max 10). Defaults to 10. ## Response - `trending_stories` - List of trending stories. - `time_period` - Time period for trending stories. - `size` - Number of trending stories to return. - `period_start` - Start time of the time period. - `period_end` - End time of the time period. - `total_time_periods` - Total number of time periods. ## Trending stories - `title` - Title of the story. - `summary` - Summary of the story. - `bearish_sentiment_ratio` - Bearish sentiment ratio. - `bullish_sentiment_ratio` - Bullish sentiment ratio. - `score` - Score of the story. - `query` - Query used to find the story. - `related_tokens` - List of related tokens. They have the format `BTC_bitcoin` - first part is the ticker, second part is the slug in Sanbase.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "properties": {
      "size": {
        "type": "integer",
        "description": "Number of trending stories to return (max 10).\n\nDefaults to 10.\n"
      },
      "time_period": {
        "type": "string",
        "description": "Time period for trending stories (e.g., '1h', '6h', '1d', '7d').\nThis parameter defines how far back to look for trending stories.\n\nDefaults to '1h' (last hour).\n"
      }
    }
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.