Terms of Service

Version 2.1 · Effective 13 August 2026 · Supersedes all prior versions

1. Who we are and what this covers

"M2M Sentinel", "we" and "us" mean Akselis, the operator of the API published at https://m2msentinel.com. "You" means the person or organisation using the API or the website. These Terms govern all use of the API, the website, the SDKs and any key issued to you. The operator can be contacted at [email protected].

By requesting an API key, settling an x402 payment, or calling any endpoint, you accept these Terms. If you do not accept them, do not use the service.

2. What the service is — and what it is not

The service performs static analysis of on-chain bytecode and returns observations about contract capabilities, proxy structure, market data and observed large transfers.

The service is not financial, investment, legal or tax advice. It is not an audit in the sense of a manual security review by human auditors. It does not prove that a contract is safe, and a favourable rating is not a guarantee against loss.

• Static bytecode analysis cannot prove reachability. A capability we report may be unreachable behind access control; a capability we do not report may still exist through paths we do not model. Every response states this in its metadata.disclaimer.
• When the service cannot obtain decision-grade data it returns capabilityRating: "UNVERIFIED", a null score, or HTTP 503 with DATA_SOURCE_UNAVAILABLE. You must handle these responses. Treating an UNVERIFIED verdict as a pass is your risk, not ours.
• Market prices and whale signals are relayed from named third-party sources with a stated retrieval time and age. They may be stale, incomplete or wrong. We do not warrant third-party data.
• You are solely responsible for any transaction you sign or broadcast. We never take custody of your funds and never sign on your behalf.

3. Accounts, keys and security

• Keys are issued to a wallet address that has proved control by signing a challenge.
• We store only a SHA-256 digest of each key. We cannot recover a lost key — we can only issue a replacement.
• You must keep keys secret and send them only in the x-api-key or Authorization: Bearer header. The API deliberately rejects credentials passed in a query string, because query strings are recorded by edge logs, proxies and browser history.
• You are responsible for all use made of your key until you revoke it at POST /v1/keys/revoke.
• If you believe a key has been exposed, revoke it immediately. Notify us at [email protected] if you believe the exposure originated with us.
• The free plan is limited to one key per wallet. Creating wallets to obtain additional free allowances is a breach of the Acceptable Use Policy.

4. Plans, credits and metering

• Every plan has a hard monthly credit cap. One successfully served response to a protected endpoint consumes one credit. No plan is unlimited.
• Current prices, credit allowances and burst limits are published at /v1/plans and rendered on the pricing page. That endpoint is the authoritative source; if any other page disagrees with it, the endpoint governs.
• Exceeding the burst limit returns HTTP 429. Exhausting the monthly cap returns HTTP 402 with CREDITS_EXHAUSTED. Neither is an outage.
• Remaining allowance is published on every authenticated response in the X-RateLimit-* and X-Credits-* headers.
• Unused credits do not roll over between billing periods.

5. Payment, renewal and refunds

• Subscriptions settle on-chain on Base in USDC, or in native ETH against a quote frozen when your purchase intent is created. The amount you sign is the amount owed.
• There is no automatic renewal and no stored payment method. A key carries an expiry date; to continue, complete a new checkout. Nothing is charged to you without a transaction you sign yourself.
• A subscription period is 31 days from issuance. x402 payments are per-call and are consumed immediately.
• Refunds. If the service fails to issue a key after a confirmed payment, we will either issue the key or refund that payment in full to the paying address. Contact [email protected] with the transaction hash.
• Change of mind. Within 14 days of purchase, if you have consumed less than 10% of your credit allowance, you may request a full refund to the paying address. After that point, subscription fees are non-refundable except where required by law.
• Refunds are paid to the address that sent the payment, in the asset that was sent. On-chain settlement is irreversible by us; we cannot claw back or reverse a transaction you sent to the wrong address.
• You are responsible for any taxes applicable to your purchase, and for your own network gas costs.

6. Availability

• The Free and Starter plans carry no availability commitment. Growth and Pro plans carry the availability target published at /v1/plans as a target, not a financially backed guarantee, unless a separate signed agreement says otherwise.
• We publish only measured health. The status page reports the instantaneous state of each dependency and historical availability only for windows with sufficient recorded health samples. We do not estimate or backfill missing measurements.
• Enterprise customers may contract for a specific availability commitment with defined remedies. That commitment exists only if it is in a signed agreement.
• We may perform maintenance, and may change, deprecate or withdraw endpoints. Breaking changes will be announced in the changelog with at least 30 days' notice where practicable.

7. Acceptable use

Your use must comply with the Acceptable Use Policy, which forms part of these Terms. We may suspend or revoke a key immediately, without refund, for a material breach.

8. Intellectual property

We retain all rights in the service, the API and its documentation. You retain all rights in your own data and applications. You may use, store and redistribute the API responses you have paid for within your own products, provided you do not present the output as a guarantee of safety and do not resell bulk access to the API itself as a competing service.

9. Warranty disclaimer

The service is provided "as is" and "as available", without warranty of any kind, whether express or implied, including any implied warranty of merchantability, fitness for a particular purpose, non-infringement, accuracy or uninterrupted operation, to the fullest extent permitted by law.

10. Limitation of liability

To the fullest extent permitted by law, we are not liable for any indirect, incidental, special, consequential or punitive loss, nor for any loss of profit, revenue, data, goodwill, tokens or digital assets, however caused.

Our total aggregate liability arising out of or relating to the service is limited to the greater of (a) the fees you actually paid us in the three months immediately preceding the event giving rise to the claim, or (b) USD 100.

Nothing in these Terms excludes liability that cannot lawfully be excluded, including liability for fraud, fraudulent misrepresentation, or death or personal injury caused by negligence. If you are a consumer, your statutory rights are unaffected.

11. Indemnity

You will indemnify us against claims, losses and reasonable legal costs arising from your breach of these Terms or the Acceptable Use Policy, or from your use of API output in a way these Terms prohibit.

12. Suspension and termination

• You may stop using the service at any time and revoke your keys.
• We may suspend or terminate access for a material breach, for conduct that threatens the integrity or availability of the service, or where required by law. Where practicable we will give notice first.
• If we terminate for reasons other than your breach, we will refund the unused portion of your current subscription period pro rata.

13. Changes to these Terms

We may update these Terms. Material changes will be announced in the changelog and the version and effective date at the top of this page will change. Continued use after the effective date constitutes acceptance. If you do not accept a change, stop using the service and request a pro-rata refund of the unused portion of your current period.

14. Applicable law and disputes

These Terms and any dispute relating to the service are governed by the law applicable to the relationship, and disputes may be brought before any court that has jurisdiction under that law. Nothing in this section limits mandatory consumer protections or any right to bring a claim in another court where applicable law requires it. Before commencing proceedings, both parties will attempt in good faith to resolve the dispute by contacting [email protected].

15. Contact

• General and legal: [email protected]
• Billing and refunds: [email protected]
• Security reports: [email protected]
• Privacy and data requests: [email protected]