The rules for AlphaYou API keys and the MCP server: what you may do with the data, the limits that apply, what we log, and when we can throttle or suspend a key.
These terms apply to every AlphaYou API key, the REST API at api.alphayou.net, the @alphayou/mcp package, and any hosted MCP endpoint we run (together, the API). They add to the Terms and the Privacy page. If they disagree about the API, these API terms win. Creating or using a key means you accept them.
A key belongs to your account. Keep it secret, do not share it, and do not put it in code other people can read. You are responsible for every call made with it.
An account may hold up to 2 live keys at once, so you can swap one without downtime. Your daily allowance belongs to the account, not the key. Every key on an account, and every alias of the same inbox (for example name+2@gmail.com), shares one allowance. Making extra keys or accounts to get more allowance is not allowed.
Use the API for your own research, your own internal tools, and your own agents and assistants that work for you or your own team. You may quote a few rows, with credit, in your own articles, posts and reports. Anything else needs written permission, see below.
Need more? We license the API to partners. Write to vansh@alphayou.net about an Enterprise licence.
When you show or quote API data, say “Source: AlphaYou” and link to alphayou.net. Keep the as-of date and the source filing link that came with it. When you quote a performance number, quote its period, benchmark, sample size and full range with it, the way the response gives them. Do not say or suggest that AlphaYou endorses you or your product.
You may keep responses for up to 24 hours to save calls. Do not keep them longer, and do not build a standing database of what the API returned. Do not present old data as current.
A free key gets 20 requests a day. A Pro key gets 50,000 a day. Most calls cost 1 request and some cost more. Every response says what the call cost and what is left today, in the X-RateLimit-Cost and X-RateLimit-Remaining headers.
There are also limits per minute and on how many calls may run at the same time. Over a limit you get a 429 and a Retry-After header. We may change limits and costs. The limits you see in the responses are the ones that apply.
If a key is used in a way that breaks these terms, puts the service at risk, or looks like abuse, we may cut its allowance, suspend it, revoke it, or stop the person behind it from making new keys. We may do this with or without notice, though we try to write first when the risk is low. If you think a suspension was a mistake, write to vansh@alphayou.net.
You can stop at any time by revoking your keys at /developers. When use ends, stop calling the API and delete what you cached. The limits on use, usage logging, research-only and liability sections continue after that.
Paid API plans are not on sale yet. Today every key is on the free plan. If we suspend or end a paid key and you did not break these terms, we refund the unused part of what you paid, in proportion to the time left. In every other case the Refund policy applies. If a paid plan ends, your keys fall back to the free plan.
We record each call: which key, which endpoint, which day, how many requests it cost, and whether it was turned away. We also record the caller’s IP address and the account behind it. If we add protection against bulk copying, we may also record which stocks a key asked about. We use this to enforce limits, spot abuse, help you, and fix faults. Daily usage records are kept about 35 days. A response may carry a request id and a tag naming the key it was issued to, so copies can be traced. See Privacy.
Some data, now or later, comes from US government financial disclosure reports, such as reports by members of Congress and by executive branch officials. Federal law (5 U.S.C. 13107) limits how reports like these may be used. You must follow it, and you are responsible for how you use this data.
Data comes from public filings and our own calculations. It can be late, incomplete or wrong, and filings can be amended. A date usually shows when something was disclosed, which can be well after the trade.
We aim to keep the API running, but on self-serve plans we offer no uptime promise and no support response time. Outages, maintenance and changes happen. We may add, change or remove endpoints and fields. We will try to post notice on /developers before removing something people rely on. An uptime commitment exists only in a written Enterprise agreement.
The API is impersonal. It takes no information about your money, goals or risk, and the same question about the same stock gets the same answer, except that the number of rows can depend on your plan. Nothing it returns is investment advice or a recommendation to buy or sell. You are responsible for your own decisions and for what your agent or app does with the data. If you show our data to people, do not present it as advice.
The API is provided as is. The disclaimers and limits of liability in the Terms apply to it. We may update these API terms. We will post the new version here with a new date, and for paid plans we will email you about a change that matters. Using the API after that means you accept it.
Questions, permissions, abuse reports, Enterprise licences and suspended-key appeals: vansh@alphayou.net.
AlphaYou