Feed
by signalsfeed.com in Markets & finance
Real-time signals feed for AI agents. Covers economic indicators, central bank policy, commodities, equities, AI, semiconductors, and geopolitical risk. Structured signals with credibility scoring. Pay-per-request via x402; free discovery available.
https://signalsfeed.com/api/v1/feed- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Expected HTTP 402, got 409
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://signalsfeed.com/api/v1/feed
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://signalsfeed.com/api/v1/feed?ids=652fc5d4-07dc-4c7a-a067-04b399a994ed&limit=1Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | string | Yes | Comma-separated article UUIDs. Max 20 per paid request. |
limit | integer | No | Default: 20. |
Example response
The provider's example. We can't check it without paying.
{
"count": 0,
"format": "full",
"signals": []
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://signalsfeed.com/api/v1/feed?ids=652fc5d4-07dc-4c7a-a067-04b399a994ed&limit=1'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://signalsfeed.com/api/v1/feed?ids=652fc5d4-07dc-4c7a-a067-04b399a994ed&limit=1' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsignalsfeed.com%2Fapi%2Fv1%2Ffeed
const res = await pay("https://signalsfeed.com/api/v1/feed?ids=652fc5d4-07dc-4c7a-a067-04b399a994ed&limit=1");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://signalsfeed.com/api/v1/feed?ids=652fc5d4-07dc-4c7a-a067-04b399a994ed&limit=1")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Expected HTTP 402, got 409 | 409 | 782 ms | - |
| 9 h ago | Expected HTTP 402, got 409 | 409 | 1.1 s | - |
| 15 h ago | Expected HTTP 402, got 409 | 409 | 684 ms | - |
| 20 h ago | Expected HTTP 402, got 409 | 409 | 658 ms | - |
| 26 h ago | Expected HTTP 402, got 409 | 409 | 703 ms | - |
Show 10 older checks
| 32 h ago | Expected HTTP 402, got 409 | 409 | 723 ms | - |
| 37 h ago | Expected HTTP 402, got 409 | 409 | 657 ms | - |
| 42 h ago | Expected HTTP 402, got 409 | 409 | 665 ms | - |
| 2 days ago | Expected HTTP 402, got 409 | 409 | 701 ms | - |
| 2 days ago | Expected HTTP 402, got 409 | 409 | 794 ms | - |
| 2 days ago | Expected HTTP 402, got 409 | 409 | 744 ms | - |
| 3 days ago | Expected HTTP 402, got 409 | 409 | 691 ms | - |
| 3 days ago | Expected HTTP 402, got 409 | 409 | 688 ms | - |
| 3 days ago | Expected HTTP 402, got 409 | 409 | 779 ms | - |
| 3 days ago | Expected HTTP 402, got 409 | 409 | 650 ms | - |