Signal Feed API: market regime for agents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNAL_FEED_BASE_URL | No | The API base URL. | https://signals.agenttrustapi.com |
| X402_BUYER_PRIVATE_KEY | No | Optional 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_CALLS | No | The maximum number of payments allowed per server process. | 3 |
| SIGNAL_FEED_EXPECTED_PAY_TO | No | The 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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_catalogA | Describe the feed: indicators and their rules, schedule, price, latest and first issue dates, free and paid access, timestamp proofs and the results record. |
| get_schemaC | Closed JSON Schema of one Regime Feed issue. |
| list_issuesC | Append-only ledger of every published issue date with its payload SHA-256. |
| get_delayed_issueA | Free Regime Feed 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_recordB | Full daily PAPER results of the virtual account behind each indicator (equity, return, benchmark, exposure, flat days, weekly fees and drawdown), losses included. Optional indicator id filter. |
| get_deviationsB | Dated list of bugs, outages, stops and other deviations that affected an indicator's account. |
| get_disclosuresB | The publisher's disclosures: personal positions, affiliate commissions, conflicts of interest. |
| get_payment_offerA | The x402 payment offer for today's issue (price, network, asset, payee) without paying, and whether the paid tool is configured in this server. |
| get_latest_issueA | Today's Regime Feed issue, paid per call via x402 (0.10 USDC on Base mainnet) 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The issue-retrieval tools are well differentiated: get_latest_issue is the paid, real-time call, get_delayed_issue is free and date-gated, and list_issues returns only ledger dates with hashes. The main soft overlap is between get_catalog and get_schema, and between get_payment_offer and get_latest_issue (offer returns the same price/network metadata without paying), but descriptions make the boundaries clear enough.
Every tool follows a predictable get_<noun> pattern except list_issues, which is the idiomatic verb for an append-only ledger. No mixed casing or stray verb styles; the naming reads as one designed surface.
Nine tools is a good fit for a single-purpose data feed: content access (latest/delayed), discovery (catalog/schema), integrity (list_issues), and accountability (results, deviations, disclosures, payment offer). Nothing feels padded or missing.
Coverage is strong for a feed publisher: paid and free retrieval, metadata, schema, ledger verification, results, and conflict disclosures. The one mild gap is that there is no tool to fetch a paid issue for an arbitrary past date (only 'latest' is paid; older dates must be 7+ days old via the free tool), which an agent wanting historical paid data would hit as a dead end.