Delta Signal ATLAS-7 Terms and Conditions
These terms define the public boundary for using Delta Signal ATLAS-7 evidence workflows, MCP/API routes, x402-enabled access paths, design-partner feedback, and agent-facing documentation.
1. Scope
These Terms and Conditions apply to public use of Delta Signal ATLAS-7 pages, documentation, OpenAPI descriptions, MCP tool surfaces, Arazzo workflows, x402-compatible access paths, readiness checks, pricing metadata, and related evidence-rendering outputs.
By using these materials or routes, you agree that Delta Signal ATLAS-7 is an evidence-routing and issuer-intelligence system, not a brokerage, investment adviser, legal adviser, accounting adviser, or fiduciary service.
2. Evidence and Non-Advice Boundary
Delta Signal ATLAS-7 outputs are evidence packages, workflow responses, route metadata, and generated summaries based on returned evidence. They are not personalized investment advice, portfolio recommendations, price targets, guarantees, or instructions to buy, sell, hold, or short any security, token, issuer, derivative, or other instrument.
Users are responsible for reviewing source dates, filing dates where available, computed times, stale flags, caveats, quality flags, evidence hashes, renderer status, payload mode, route or tool provenance, and non-advice disclaimers before relying on any output.
Natural Language briefs and rendered Markdown compile returned evidence into readable form. They do not create new evidence, fill missing data, override caveats, or convert screens into recommendations.
3. API, MCP, Arazzo, and x402 Usage
Public users and agent clients may inspect route metadata, OpenAPI schemas, MCP tools, and Arazzo workflows to understand available capabilities before execution. Route availability, pricing, schemas, response envelopes, and payment behavior may change as the service evolves.
MCP-compatible clients should discover available tools before execution and prefer bounded workflows such as Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, and other published composite routes when they match the user intent.
Large response paths may require file output or redirect handling. Clients should not assume that every shell, editor, or agent pipe can safely display large route responses without truncation.
4. Design Partner Feedback
Delta Signal may work with design partners, early users, integrators, customers, subscribers, developers, and integration testers to improve route contracts, field naming, pricing metadata, workflow ergonomics, output limits, response schemas, payment behavior, reliability, documentation, agent-facing surfaces, and related developer experience.
Unless otherwise agreed in a separate written agreement, any non-confidential feedback, suggestions, feature requests, bug reports, workflow observations, integration notes, schema comments, pricing comments, or documentation comments provided to Delta Signal may be used, modified, incorporated, published, or commercialized by Delta Signal without restriction, compensation, royalty, attribution requirement, or ownership claim by the contributor.
Delta Signal may use non-confidential feedback to improve public route contracts, API behavior, MCP tools, x402 pricing metadata, documentation, examples, output limits, error handling, and workflow design.
Helpful feedback includes route behavior and path-scope issues; field naming stability and schema versioning needs; pricing metadata and billing reconciliation issues; response-size and output-limit issues; MCP, REST, OpenAPI, Arazzo, x402, and agent-client workflow friction; provenance, freshness, caveat, and evidence-hash requirements; and documentation gaps that affect real integrations.
Please avoid sending private source code, trading rules, customer data, wallet secrets, API keys, regulated data, proprietary implementation details, or third-party restricted information unless a separate written agreement is in place.
5. Ownership and License Boundaries
Delta Signal retains ownership of its software, documentation, route contracts, MCP surfaces, OpenAPI descriptions, Arazzo workflow definitions, pricing metadata, evidence-rendering logic, names, trademarks, designs, systems, workflows, and other pre-existing or independently developed materials.
Each party retains all rights, title, and interest in its pre-existing technology, source code, data, systems, workflows, models, prompts, documentation, trademarks, confidential information, and other proprietary materials. Providing feedback does not transfer ownership of either party's underlying technology, private systems, source code, trading logic, datasets, research processes, customer data, wallet infrastructure, or confidential materials.
Delta Signal is not obligated to implement, maintain, support, or prioritize any requested change. If Delta Signal implements a feature, route, schema, field name, documentation improvement, or workflow pattern based on feedback, that implementation belongs to Delta Signal unless a separate written agreement states otherwise.
No feedback exchange, support conversation, bug report, or workflow observation transfers ownership of either party's pre-existing intellectual property unless a separate written agreement explicitly says so.
6. Confidentiality and Public Documentation Boundary
Public pages should not include private design-partner names, personal mailboxes, wallet addresses, grant balances, customer lists, support artifacts, private keys, API keys, unpublished data, or non-public integration details.
Do not submit secrets, credentials, private keys, regulated personal data, customer-sensitive data, confidential third-party material, proprietary trading rules, private architecture diagrams, dashboard logic, wallet infrastructure, or private implementation details through public examples, issue reports, or publicly visible workflow prompts.
Public attribution, testimonials, named case studies, or references to a design partner's identity, company, wallet address, codebase, dashboard, trading workflow, or integration architecture require separate permission.
7. Pricing, Credits, Grants, and Payments
Published prices, credits, route estimates, x402 challenges, grants, and payment metadata are operational route metadata, not a guarantee that every route will remain available at the same price, mode, or output shape forever.
Paid calls may return an HTTP 402 challenge. Compatible clients may submit valid payment proof or use an authorized grant/key path when available. Users are responsible for inspecting current pricing and payment status returned by the route or tool response.
8. Availability, Accuracy, and Missing Data
Delta Signal ATLAS-7 may return unavailable routes, stale markers, caveats, quality flags, not-found responses, partial evidence, soft misses, or payment-required responses. A structured not_found or caveated response means evidence is unavailable or incomplete for that route/ticker pair at that moment; it does not mean missing facts should be inferred.
Users should treat outputs as research inputs requiring review. No warranty is made that any route, workflow, issuer universe, filing-derived fact, or generated brief is error-free, complete, current, uninterrupted, or suitable for any specific investment, compliance, accounting, legal, or operational decision.
9. Acceptable Use
Do not use Delta Signal ATLAS-7 to bypass payment controls, scrape abusively, attack service availability, extract secrets, misrepresent outputs as personalized advice, remove caveats or non-advice boundaries, or create misleading claims about source coverage, freshness, or evidence availability.
Agent clients should preserve provenance, caveats, source dates, quality flags, and missing-data boundaries in downstream outputs.
10. Changes to These Terms
Delta Signal may update these terms as products, workflows, pricing, MCP surfaces, evidence contracts, and partner programs evolve. Continued use of the public pages, routes, tools, or documentation after updates means the updated terms apply.
Effective date: June 13, 2026.