Acceptable Use Policy

This Acceptable Use Policy is part of the Terms of Service. It applies to every account, key, website session, REST call, WebSocket connection, and MCP client. If this policy and a marketing page disagree about what is allowed, this policy and the Terms control.

The policy exists so the Service stays available, so publishers' rights stay intact, and so one customer's workload does not degrade the feed for everyone else.

Related: Terms of Service · Privacy Policy · AI Policy.

1. Who must follow it

You must follow it. So must anyone who uses your keys, including a teammate, a script, a hosted agent, and an MCP client you connect. Their traffic counts as yours. If you build a product on the Service, you must impose restrictions on your users that are at least as protective as Section 3 and Section 4.

2. Permitted uses

While your account is in good standing and the call is inside your plan limits, you may:

• Display headlines, snippets, summaries, entities, timestamps, tickers, sources, and links in your own applications, dashboards, bots, alerts, research tools, and newsletters.
• On a paid plan, include that material in a commercial product you sell, as a feature of your product rather than as a copy of the feed.
• Use the data for internal research, backtesting, and training of models that remain inside your organization and do not re-publish the corpus.
• Cache responses to cut your own request volume.
• Display the full text of a press release that the API includes in the body field, because those releases are written to be distributed. Attribute the wire or the company and link to the original when an end user can see it.
• Filter stock news, press releases, and legal notices, and combine those filters with tickers, sources, dates, and search text, as the documentation describes.
• Connect an assistant to the MCP server on a plan that includes it, and let that assistant answer from tool results with links.

Free-plan use is for evaluation, development, and light production traffic inside the free limits: 100 requests a day, a 15-minute delay, and the last year of history. Free does not include the WebSocket, the MCP server, or the full archive. Production use that needs those belongs on Pro.

3. Attribution and what you may show

• When an end user can see a third-party article, a press release, or a legal notice, show the source and a working link to the original. Do not present the item as your own reporting.
• For publisher stock news and for legal notices, the display right covers the headline, snippet, summary, metadata, entities, and the link. It does not cover republishing the publisher's full article or the law firm's full notice.
• For press releases, you may show the full text the API returns, with the source and a link.
• You may quote a short excerpt of a publisher article where the law of fair use or an equivalent limitation already allows it. This policy does not expand that law, and it does not grant a license to the publisher's copyright.
• Do not strip identifiers that a reasonable reader needs in order to find the original, and do not alter a headline so that it says something the source did not say, while still attributing it to that source.

4. Redistribution and competing products

You may not, without a separate written agreement from us:

• Resell, sublicense, or redistribute the raw feed, a firehose, a bulk file, or a substantial portion of the archive as a data product.
• Offer a news API, a news websocket, an MCP news server, or a downloadable dataset that is substantially our feed, even if you add a field of your own.
• Systematically store the archive in order to stop using the Service while continuing to serve that archive to others.
• Share keys across unrelated organizations, publish a key, or embed a key in code that ships to end users or to a public repository.
• Sublicense MCP access so that people who are not your users reach our server on your key.

Building a product that uses the feed to do something else — an alert, a dashboard, a research note, a summary your own model writes from a single article, a compliance queue — is permitted on a paid plan. Building a product whose value is the feed itself is not, unless we license it in writing. If you are unsure which one you are building, email [email protected] before you launch it.

5. Keys, accounts, and limits

• Keep keys secret. Rotate a key that might have leaked. You can hold up to 20 active keys and you can revoke any of them.
• Do not open additional accounts to stack free quotas, stack trials, or route around a suspension. One trial per email.
• Do not share one account between unrelated companies.
• Stay inside published limits. Pro has no daily request quota, and it still has a burst limit of 20 requests per second, 3 concurrent WebSocket connections, and 200 subscriptions on a connection. Free has 100 requests per day.
• Do not open connections for the purpose of holding them idle in large numbers, and do not retry failed requests in a tight loop.
• Do not hide your traffic behind rotating keys, rotating accounts, or a proxy farm in order to defeat a limit.

A limit exists so the cluster stays up. Traffic that is inside the arithmetic limit but is clearly intended to exhaust it, such as requesting every ticker in a tight loop from many connections, can still be throttled under the Terms.

6. Security

You may not:

• Probe, scan, or test the Service for vulnerabilities except under a written authorization from us that names the scope and the time window.
• Bypass authentication, rate limits, plan checks, or access controls.
• Interfere with other customers' traffic, or attempt to read their keys, queries, or accounts.
• Introduce malware, or send payloads designed to disrupt the API, the WebSocket, the MCP server, or the website.
• Use the Service to attack a publisher or another third party.

If you find a weakness, email [email protected] with enough detail for us to reproduce it, and give us a reasonable time to fix it before you describe it publicly. We will not pursue an account for a good-faith report that stayed inside this section.

7. Unlawful use and market abuse

You may not use the Service, or data from it, for:

• any unlawful purpose, including fraud and the violation of securities, privacy, or intellectual-property law;
• market manipulation, spoofing, or the dissemination of a rumor you present as a headline from the feed;
• spam, unsolicited bulk email, or a newsletter the recipient did not ask for, where the content is our feed;
• impersonating MarketNewsAPI, DTS Analytics, a publisher, or another person;
• building or training a system whose purpose is to generate fake headlines attributed to real sources.

Automated trading systems may consume the feed as one input. You are solely responsible for those systems, for pre-trade controls, and for compliance with the rules of any venue you trade on. The Service is not an execution system and it does not know your orders.

8. Website and MCP clients

• Do not scrape the marketing site, the docs, or the live news desk as a substitute for the API. The API is the supported interface.
• You may fetch the public machine-readable files we publish for that purpose, including robots.txt, the sitemap, llms.txt, and the OpenAPI document.
• An MCP client must send tool calls that match the documented tools. Do not use the MCP endpoint as an unauthenticated bulk download.
• You are responsible for the client's retention of articles. If the client stores results, Section 3 and Section 4 still apply to that store.

9. Enforcement

If we believe this policy has been violated, we may throttle traffic, revoke a key, suspend MCP or WebSocket access, suspend the account, or close it. We will contact you first when the violation is curable and the delay does not put the Service or another person at risk. A compromised key may be revoked immediately, and we will tell you.

We may preserve logs related to an investigation for as long as we need them for security, for a legal claim, or for a duty to a third party. Repeated or serious violations, including resale of the feed and evasion of a prior suspension, can end the account. Fees already paid are not refunded, as the Terms describe.

We are not obligated to monitor the feed or your application, and we do not accept a duty to do so by publishing this policy.

10. Changes

We may update this policy by posting a new version and changing the "Last updated" date. If a change materially narrows a use that was previously allowed, we will give at least 15 days' notice by email before it applies to existing accounts, unless the change is required by law or by a publisher's demand that we cannot postpone. Continued use after the effective date is acceptance.

11. Contact

Questions about whether a use is allowed, and reports of abuse:

DTS Analytics LLC, 1309 Coffeen Avenue STE 1200, Sheridan, Wyoming 82801, USA
Operating as MarketNewsAPI
[email protected]