Terms of use

What this service is

The RaiderRouter MCP service is a pass-through processor. It takes a request from your agent, calls a financial data vendor on your behalf using a key you supplied, and hands you back what that vendor said, wrapped in a record of where it came from. It is plumbing. It does not resell data, it does not hold a licence to anybody's market data, and it does not give investment advice.

Some sources need no key at all (public government and exchange feeds). For those, the proxy calls the public endpoint directly on your behalf. Anything else runs on a key you connected.

Your vendor accounts are yours

You bring your own vendor API keys. Every call the proxy makes with one of your keys is a call made under your agreement with that vendor, billed to your quota, subject to your plan and your vendor's terms. You are responsible for reading those terms and for staying inside them, including any limit on how the data may be redistributed, displayed or stored.

We are not a party to your vendor agreement, and we cannot grant you rights a vendor did not. If a vendor terminates your key or changes what it unlocks, the tools that depended on it stop appearing. That is the vendor's decision, not ours.

Your keys are never shared

Vendor credentials are encrypted before they are written to the database and are decrypted only for the length of one call made on your behalf. A credential belongs to exactly one account and is bound to that account cryptographically, so it cannot be moved to another account's row and still be readable.

No account's vendor data is ever cached for, or served to, another account. The short-lived response cache is partitioned per account: there is no way to name another account's entry, because the account is fixed when the cache handle is created and is not something a lookup can pass.

Signing in

Sign-in is with Google and nothing else. We do not issue passwords and there is nothing here for you to remember. If you lose access to the Google account you signed up with, you lose access to this one.

Your agent authenticates separately through OAuth when that flow is available, or with a manual bearer token you generate. A manual token is shown once at creation and stored only as a hash, so we cannot recover it and neither can anyone who reads our database. Treat either access token as a password: anyone holding it can use your connected vendor keys through this service while it remains valid.

We check your keys against the vendor

So the tool list you see is the tool list that actually works, the proxy tests each stored key by making a small real request to that vendor:

• immediately when you save or change a key,
• whenever a real tool call tells us something about the key, and
• on a background schedule, by default about every 15 minutes per key.

Those probes are real vendor requests made with your key, so they count against your quota. Where a vendor meters by the day rather than by the minute, the adapter for it sets a longer floor (the Alpha Vantage adapter asks for 6 hours, because its free tier is 25 requests per day). A key we could not reach because the vendor was down is retried sooner, about two minutes later, so a brief outage clears on its own instead of leaving your tools switched off for a full cycle.

No warranty on vendor data

We do not verify, correct, or stand behind the numbers a vendor returns. The proxy tells you which vendor answered, which endpoint it came from, and what date the vendor said the figure belongs to. Whether that figure is right is between you and the vendor.

The service is provided as is, without warranties of any kind, and without any guarantee of availability. Do not use it as the only input to a trading decision, and do not use it where being wrong is unacceptable.

Missing is reported as missing

When a vendor does not publish a field, the response names that field as unavailable with a reason instead of filling it with a zero, a null or an estimate. When every source for a request fails, the call fails and says so. A vendor answer that turns out to be a sample payload, a plan notice, or data about a different company is refused rather than passed through.

This is deliberate and it means you will sometimes get less than you asked for. A blank we told you about is safer than a number we made up.

Using the service

Do not use the proxy to work around a vendor's limits, to share one key across people who are not entitled to it, or to redistribute vendor data in a way your vendor agreement forbids. Do not attempt to reach another account's credentials, tokens, or data. Do not use the service for anything unlawful.

We may suspend or close an account that does any of that, or that is causing problems for the vendors we call on other people's behalf. We will tell you at the address on your account when we can.

Ending it

You can stop using the service at any time. Revoking a bearer token cuts off an agent immediately. You can delete your account and everything attached to it yourself from Account settings, under "Account data"; you will be asked to type the address on the account to confirm. Deleting the account permanently deletes its stored credentials, its tokens, its call log and its IP allowlist; routine database backups can hold deleted rows for a while before they age out. If you can no longer sign in, email [email protected] from the address on the account and we will do it for you.

Changes

If these terms change in a way that matters, the effective date above changes with them. Continuing to use the service after that date means you accept the new version.

Contact

Questions about these terms, about a specific request, or about deletion: [email protected]. Quoting the request_id from a response lets us find exactly the call you are asking about.