Skip to main content
Glama
Signal Feed API: market regime for agents

Signal Feed API: market regime for agents

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIGNAL_FEED_BASE_URLNoThe API base URL.https://signals.agenttrustapi.com
X402_BUYER_PRIVATE_KEYNoOptional wallet key for a wallet holding a little USDC on Base. Without it, every free tool works; only get_latest_issue is disabled.
SIGNAL_FEED_MAX_PAID_CALLSNoThe maximum number of payments allowed per server process.3
SIGNAL_FEED_EXPECTED_PAY_TONoThe only payee the client will pay. Overrides the published merchant address.0x8b0ad0CE12Ac86822c4d5dE442F5e445d14F9183

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Signal Feed API publishes one Regime Feed issue per day: five machine-readable market-regime indicators (BTC trend, alt trend, US equity regime, SPY RSI-2 state, MSTR BTC filter) derived from virtual PAPER research accounts; there is no track record. Not investment advice. Issues older than 7 days, the full PAPER results record (losses included), deviations and disclosures are free. Today's issue is paid per call via x402 (0.04 USDC on Base, VAT included); get_payment_offer shows the live offer.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_catalogA

Free. Use first, when you need to know what the daily regime labels mean before trusting them: indicators and their exact rules, schedule, price, latest and first issue dates, free and paid access, timestamp proofs and the results record.

get_schemaA

Free. Use when you must parse or validate an issue safely: the closed JSON Schema of one issue.

list_issuesA

Free. Use to see which issue dates exist or to verify an issue you hold: every published date with its payload SHA-256, append-only.

get_delayed_issueA

Free. Use to try the feed before paying, or to backtest your own logic: the issue for a date at least 7 days old (YYYY-MM-DD), with its hash recomputed and compared to the issue's integrity block and to the public ledger.

get_results_recordA

Free. Use when deciding how much weight to give an indicator: full daily PAPER results of the virtual account behind each one (equity, return, benchmark, exposure, flat days, weekly fees and drawdown), losses included. Optional indicator id filter. Not real-money results.

get_deviationsA

Free. Use to check whether a bad day was a data or system problem: dated bugs, outages, stops and other deviations that affected an indicator's account.

get_disclosuresA

Free. Use to check the seller's conflicts of interest: personal positions, affiliate commissions and other conflicts.

get_payment_offerA

Free. Use before paying to see exactly what would be charged: today's x402 offer (price, network, asset, payee) without paying, and whether the paid tool is configured in this server.

get_latest_issueA

Paid, 0.04 USDC on Base via x402. Use once a day when you must decide whether markets are risk-on or risk-off before sizing or gating a trade: today's five rule-based regime labels, paid from the wallet configured in this server (optionally checked first by Agent Trust preflight). Returns the issue, the receipt, the settlement transaction and the hash check against the public ledger.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a clearly distinct resource or action: latest paid issue, delayed free issue, catalog, schema, issue list, results record, deviations, disclosures, and payment offer. The potentially closest pairs, such as get_latest_issue vs. get_delayed_issue and get_catalog vs. get_schema, are explicitly separated by paid/free status, age, and use case.

Naming Consistency5/5

All names use snake_case with a predictable verb_noun structure, mostly get_* with one list_issues. The single list verb is semantically appropriate and does not disrupt the pattern.

Tool Count5/5

Nine tools is well scoped for a read-only market-signal feed with trust, payment, schema, and historical-verification needs. Each tool has a clear role and the set avoids unnecessary breadth.

Completeness4/5

The surface covers the core workflow well: discovery, schema validation, latest paid issue, free delayed issue for testing/backtesting, issue listing, performance results, deviations, disclosures, and payment offer. A minor gap is the lack of a generic paid issue lookup by date for recent dates other than the latest issue.

Maintenance

ActivityMaintained
ResponsivenessOutdated data