API Terms of Use

1. Acceptance and Scope

These API Terms of Use (“API Terms”) apply to all application programming interfaces, machine-readable responses, x402-enabled endpoints, documentation, developer tools, sample code, schemas, keys, credentials, and related services made available through or in connection with MyCoinEdge (“APIs”).

These API Terms supplement the MyCoinEdge Terms of Service, Privacy Policy, Disclaimer, Publisher Agreement, and Acceptable Use Policy.

2. Definitions and Protected Parties

“Developer” means any person, business, automated agent, or system that accesses, calls, integrates, displays, stores, processes, or redistributes an API response.

3. Limited API License

Subject to compliance with these API Terms, you receive a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to access and use the APIs for lawful, authorized purposes.

No ownership right is transferred. All rights not expressly granted are reserved.

4. Credentials, Identifiers, and Access

If API keys, account credentials, wallet addresses, widget IDs, tokens, or other access identifiers are issued, you are responsible for safeguarding them and all activity performed through them.

You may not share, sell, publish, expose, or transfer credentials except as expressly authorized. Suspected compromise must be reported promptly.

5. Permitted Use

You may use the APIs to retrieve educational market intelligence, build authorized applications, display responses to end users, support internal research, and create lawful integrations consistent with documentation and applicable agreements.

Any end-user presentation must preserve the educational nature of the information and must not misrepresent API output as personalized financial, investment, trading, legal, tax, or other professional advice.

6. Prohibited Use

You may not use the APIs to:

• bypass, forge, replay, manipulate, or defeat x402 payment challenges, transaction verification, credits, authentication, rate limits, or access controls;
• scrape, mirror, bulk-download, harvest, or reconstruct databases beyond documented or authorized use;
• reverse engineer, decompile, disassemble, or discover proprietary formulas, models, prompts, weights, heuristics, classifications, or source code;
• create guaranteed-profit claims, personalized trading instructions, deceptive financial products, unlawful gambling products, or regulated services without required authorization;
• misstate the source, freshness, accuracy, ownership, sponsorship, endorsement, or certainty of API output;
• introduce malware, excessive traffic, denial-of-service activity, abusive automation, security probes, or harmful code;
• use responses to train, fine-tune, benchmark, or evaluate models in a way that extracts or reproduces protected platform logic without written permission;
• resell, sublicense, or redistribute access except as expressly authorized; or
• violate law, sanctions, privacy rights, consumer-protection rules, intellectual-property rights, or third-party agreements.

7. Rate Limits and Fair Use

APIs may be subject to documented or dynamic rate limits, quotas, concurrency limits, caching rules, request-size limits, or other controls.

You may not evade limits through multiple accounts, wallets, IP addresses, domains, agents, or other means. We may throttle, reject, delay, or block requests that create operational, security, payment, legal, or abuse risk.

8. x402 Challenges, Paid Endpoints, and Settlement

Certain APIs may require payment through an x402-compatible process or other supported payment method. A payment challenge may specify price, asset, network, recipient, request conditions, and settlement requirements.

You are responsible for verifying all payment details before approval. A request is not considered paid merely because a wallet signed, a transaction was attempted, or a challenge was returned.

Access may depend on verified settlement and valid payment proof. Blockchain transactions generally cannot be reversed by MyCoinEdge.

Except where required by law or expressly agreed otherwise, successfully delivered digital API responses are final and non-refundable.

9. API Data and Response Use

API responses may be cached, stored, displayed, or processed only as reasonably necessary for authorized use and subject to any endpoint-specific restrictions.

You must preserve material timestamps, confidence indicators, educational disclaimers, source labels, and freshness information when omission would make the response misleading.

You may not present stale data as current or alter a response in a way that materially changes its meaning.

10. Resale, Redistribution, and Derived Products

Public display or resale may require a separate publisher, enterprise, reseller, or licensing agreement.

Unless expressly authorized, you may not sell raw API access, provide pass-through access, create a substitute API, republish substantial response archives, or offer a competing data service built primarily from the APIs.

Lawful derived products must add meaningful independent value and must not misrepresent ownership, endorsement, accuracy, or source.

11. Security Requirements

You must use reasonable technical and organizational safeguards appropriate to your application, users, credentials, wallet activity, and data.

You may not conduct penetration testing, vulnerability scanning, protocol probing, or security research against the APIs without prior written authorization.

Security vulnerabilities should be reported privately through the published contact method and not publicly disclosed before reasonable remediation opportunity.

12. Logging, Monitoring, and Enforcement

Requests may be logged and analyzed for billing, settlement, performance, fraud prevention, security, support, compliance, rate limiting, and enforcement.

Logs may include endpoint, method, timestamp, status code, payment status, wallet or transaction identifiers, referrer, user agent, IP address, and diagnostic information.

13. API Changes and Versioning

APIs, schemas, fields, endpoints, prices, authentication methods, supported assets, documentation, limits, and response formats may change.

We may deprecate or discontinue an API or version. Reasonable notice may be provided when practical, but immediate changes may be made for security, legal, operational, or third-party dependency reasons.

14. Availability and Service Dependencies

API availability is not guaranteed. Requests may fail, time out, be delayed, return unavailable values, or become incompatible with your integration.

APIs may depend on third-party data, hosting, networks, wallets, facilitators, nodes, gateways, and blockchain infrastructure outside the control of the Protected Parties.

15. Accuracy and Educational Nature

API output is educational information only. No response is a recommendation, guarantee, or personalized instruction.

Data may be incomplete, stale, inconsistent, unavailable, incorrectly formatted, or affected by source, software, network, model, or human error.

Confidence values describe evidence strength or agreement, not certainty.

16. Third-Party Services

Your application may rely on wallets, blockchain networks, exchanges, stablecoins, hosting, cloud services, frameworks, or other third parties.

The Protected Parties are not responsible for third-party outages, defects, security incidents, policy changes, transaction failures, asset risks, or legal compliance.

17. Intellectual Property

APIs, documentation, schemas, software, reports, models, classifications, interfaces, naming systems, and related technology are owned by or licensed to the applicable Protected Parties.

You retain ownership of your original application code and lawful content, but no ownership of the APIs or underlying platform technology is transferred.

18. Suspension and Termination

Access may be suspended, limited, revoked, or terminated for abuse, nonpayment, legal risk, security risk, operational harm, policy violations, excessive use, or suspected fraud.

Termination does not eliminate accrued payment, tax, indemnification, confidentiality, intellectual-property, liability, or dispute obligations.

19. Disclaimer of Warranties

THE APIS ARE PROVIDED “AS IS,” “AS AVAILABLE,” AND “WITH ALL FAULTS,” WITHOUT WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, SECURITY, COMPATIBILITY, OR CONTINUITY.

20. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NO PROTECTED PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES; LOST PROFITS; LOST REVENUE; LOST DATA; BUSINESS INTERRUPTION; WALLET LOSS; PAYMENT LOSS; OR COST OF SUBSTITUTE SERVICES.

THE TOTAL AGGREGATE LIABILITY OF ALL PROTECTED PARTIES ARISING FROM THE APIS OR THESE API TERMS WILL NOT EXCEED THE GREATER OF: (A) THE AMOUNT PAID DIRECTLY FOR THE SPECIFIC API SERVICE GIVING RISE TO THE CLAIM DURING THE THREE MONTHS BEFORE THE EVENT; OR (B) TEN U.S. DOLLARS (US $10.00).

21. Developer Indemnification

To the maximum extent permitted by law, you agree to defend, indemnify, and hold harmless the Protected Parties from claims, liabilities, penalties, losses, damages, settlements, costs, and reasonable attorneys’ fees arising from or related to:

• your application, integration, users, content, claims, or business;
• your use or misuse of the APIs;
• your breach of these API Terms, law, or third-party rights;
• security failures, exposed credentials, payment abuse, or unauthorized access attributable to you; or
• your redistribution, interpretation, display, resale, or commercialization of API output.

22. Governing Law and Disputes

These API Terms are governed by Florida law, without regard to conflict-of-law principles, except where federal or non-waivable law applies.

Before filing a claim, the parties will attempt informal resolution for at least 30 days after written notice.

Any court proceeding must be brought in the state or federal courts located in the Florida county where the MyCoinEdge operator maintains its principal place of business, subject to non-waivable rights.

23. General Terms

You may not assign these API Terms without written consent. MyCoinEdge may assign them in connection with a reorganization, license, sale, merger, financing, transfer of assets, or change of control.

If a provision is unenforceable, it will be modified to the minimum extent necessary and the remaining provisions will remain effective.

Failure to enforce a provision is not a waiver. These API Terms and incorporated policies are the entire agreement concerning API access.