Skip to content
Signalith

Signalith for AI agents

Add one URL to your AI agent and it can look up, read and check Signalith’s signed data on its own, through the Model Context Protocol. Nothing to install. What it may spend is set by you, not by a prompt.

server URL
https://signalith-gw.187-53-130-188.sslip.io/gw/mcp

Without a key it can search, describe and verify for free. Connected to your wallet it also reads reports from the packs you bought, reads past reports, and asks you to buy more: it sends you a payment link, and nothing is bought until you sign it in your wallet. You choose what it may do when you connect it; everything is allowed by default. The hosted server holds no wallet and never pays by itself.

What the agent can do

ToolCostWhat it does
search_feedsFreeFinds feeds by words or category, with price per call, packs, heartbeat, signer and uptime.
get_feedFreeEverything about one feed before paying: methodology, sources, decimals, prices, signers, reliability.
read_feedPaidThe latest signed report, verified before the agent sees it. Spends a pack call, or pays in USDG inside the budget.
buy_feedYou approveHosted: sends you a payment link for a pack. Nothing is bought until you sign it in your wallet; then the agent reads from it.
list_packsFreeThe calls you already bought, per feed, and when they expire.
read_historyPack callsPast signed reports from the last two days, taking calls from a pack.
verify_reportFreeChecks a report someone else handed the agent, and that it is of the feed the agent expected.

Set it up

Pick where your agent runs and what it may spend. The configuration below follows your choice.

Your agent runs in
What it may spend
connector URL
https://signalith-gw.187-53-130-188.sslip.io/gw/mcp
  1. In Claude on the web or in the desktop app, open Settings, Connectors, and choose Add custom connector. Name it Signalith and paste the URL above. Leave the OAuth Client ID and Client Secret empty.
  2. Press Add, then Connect. A Signalith page opens: sign in with the wallet that bought your packs, or paste an API key. Choose what Claude may do: read reports, ask you to buy calls, read past reports. All three are ticked by default. Press Allow Claude and you are sent back to Claude.
  3. In a new chat, turn Signalith on in the tools menu and ask, for example, "Which Signalith packs do I hold?"
  4. When Claude needs calls you do not hold, it gives you a payment link. Open it, pay with the same wallet, and tell Claude you paid: it reads from the new pack.
  5. Signalith is then there in Claude on the web, in the desktop app and on your phone. If an earlier Signalith connector failed to connect, remove it and add it again.

The key it receives shows under Dashboard, API keys, named after Claude. Revoke it there and Claude asks you to connect again.

Try it

Ask the agent in plain words. It picks the tools itself.

prompts
Search Signalith for feeds about inflation and tell me what each costs per call.
Read the latest value of lumoracle/eur-usd-ecb-reference from Signalith and tell me when it was observed.
Which Signalith packs do I hold, and how many calls are left on each?
Buy me the smallest pack of lumoracle/eur-usd-ecb-reference on Signalith.
Check this Signalith report and tell me whether it is genuine: <paste the JSON>

Your money stays under your control

  • Every purchase is yours to sign. Through the hosted server an agent never pays: buy_feed gives you a link to the feed's page with the pack it wants chosen and the wallet named, and you pay in your own wallet or leave it. Its key only spends calls you already bought, so a leaked key costs at most the calls left, and you revoke it from the dashboard.
  • A wallet stays on your machine. An agent that pays for itself runs the server locally, and its budget lives in that process: it is checked before anything is signed, so nothing the agent reads on a web page or in a tool result can raise it, and reads sent at once cannot pass it together.
  • Reports are checked before the agent sees them. The local server checks on Robinhood Chain that a payment goes to the provider’s vault and that each report’s signer is in the registry. The hosted server runs beside the gateway and checks against the registry the gateway mirrors, which the gateway checks on chain before it sells a report.
  • Every failure says what it cost. A failed read tells the agent whether it was charged: no, yes, or maybe when a payment was sent and its settlement is not yet known. After a maybe the server will not pay for that feed again for five minutes, and a payment that lands is credited as calls the next read spends.
  • Narrow a local server further if you like. SIGNALITH_MAX_PAYMENT_USDG caps one payment, SIGNALITH_PROVIDERS and SIGNALITH_CATEGORIES limit what the agent may read, SIGNALITH_SIGNER_KINDS and SIGNALITH_MIN_SOURCES limit which reports it accepts. Anything outside them is refused before a call is spent.

More

Every setting is listed under Agent integration in the docs. To check a report by hand, paste it into Check a report. Signalith’s contracts are not audited; see Security before trusting a report with more than you can lose.