Terms of Service

These Terms of Service (the "Terms") govern access to and use of the AproxPay proxy service, including the API endpoints under proxy.aproxpay.com, the CONNECT gateway at gw.aproxpay.com, the published MCP server and client wrappers, and any related documentation (collectively, the "Service"). The Service is operated by AproxPay ("we", "us", "our").

The following documents are incorporated into these Terms by reference and form part of the agreement between you and AproxPay:

• Acceptable Use Policy ("AUP")
• Privacy Policy
• Refund Policy

1. Acceptance of Terms; No Account Required

1.1. The core proxy Service does not require registration, an account, or an API key. Before payment, the applicable x402 payment requirements must identify the current revision of these Terms and provide links to the incorporated policies. By signing and transmitting a payment authorization after that notice, you accept these Terms. Use of a free endpoint is subject to the restrictions in these Terms and the AUP, but does not by itself constitute evidence that you accepted payment or dispute provisions.

1.2. If you use the Service on behalf of an organization, or if the Service is invoked by an automated agent, bot, or software program that you operate, configure, or deploy (an "Agent"), you represent that you have authority to bind that organization, and you accept these Terms on behalf of yourself, the organization, and the Agent. You are fully responsible for all activity performed by your Agents through the Service, whether or not you supervised the specific request.

1.3. You must be at least 18 years old (or the age of majority in your jurisdiction) and legally capable of entering into a binding contract.

1.4. The Service may be used for business, professional, or personal purposes where lawful. If you use the Service as a consumer, nothing in these Terms excludes statutory rights or remedies that cannot lawfully be excluded.

2. Description of the Service

2.1. AproxPay is a pay-per-use residential proxy service designed for autonomous AI agents and developer tooling. The Service offers, without limitation:

• Per-request fetch — a single HTTP(S) request forwarded through a residential exit IP, invoked via POST /v1/proxy (or its higher-cap variants), priced and metered per request;
• Session pass — time- and traffic-limited ephemeral proxy credentials (host, port, username, password) for a standard HTTP CONNECT forward-proxy gateway, suitable for browsers, Playwright, and long-running workflows, invoked via POST /v1/session and its tier variants and extensions.

2.2. Byte caps and time limits. Every purchase is subject to a hard byte cap and, for session passes, a fixed expiry time (TTL), as specified in the pricing published at the time of purchase (in the 402 payment requirements and service discovery documents). When the byte cap is exhausted or the TTL expires, active connections are terminated and the associated credentials stop working. Traffic is metered by actual bytes transferred in both directions at the stream level. Unlimited traffic is not offered at any price point.

2.3. Upstream infrastructure. The Service does not operate its own pool of residential IP addresses. Exit connectivity is provided through third-party upstream proxy providers. Your use of the Service is therefore also subject to the operational constraints and acceptable-use policies of those providers (see Sections 6 and 7).

2.4. We may modify, add, or discontinue features, endpoints, pricing tiers, or upstream providers at any time. Pricing applies per purchase at the moment of payment. Any active session remains subject to availability, safety controls, upstream restrictions, and our suspension rights under these Terms.

3. Payments (x402, Non-Custodial)

3.1. All payments are made in USDC on the Base network (or another network we designate) via the x402 protocol. Payment settlement occurs directly from your wallet to our wallet through a third-party payment facilitator. We are non-custodial: we never hold, store, or control your funds, and we do not provide wallet, exchange, money transmission, or custody services.

3.2. x402 payments are push payments: you authorize each payment individually and in advance. There is no stored balance, no subscription, and no deferred billing.

3.3. Blockchain settlement entries are irreversible. Once a payment settles on-chain, the original transaction cannot be reversed, cancelled, or charged back. Any refund is a separate transfer. All sales are final, subject to mandatory law and the narrow discretionary exception in the Refund Policy.

3.4. You are solely responsible for the security of your wallet and private keys, for transaction fees (if any), and for any taxes arising from your use of the Service.

3.5. Payments and access may be screened by our payment facilitator, our compliance providers, and us for sanctions and financial-crime risk (see Section 7). A payment or request that fails an applicable check may be rejected before or at settlement and will not be served.

4. Service Level and Availability — No Guarantees

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT ANY SERVICE-LEVEL COMMITMENT. Specifically, and without limitation:

4.1. No uptime guarantee. We do not warrant any level of availability, and we do not offer an SLA, service credits, or compensation for downtime, maintenance windows, or degraded performance.

4.2. No sticky-IP guarantee. Session passes and sticky sessions are designed to preserve the same exit IP for the purchased duration on a best-effort basis. However, the exit IP may change at any time — for example, when the upstream residential peer goes offline, when the upstream provider rotates or suspends the underlying account, or when we migrate your session to a different upstream allocation for operational or abuse-prevention reasons. Such a change preserves your remaining session time and byte cap but is not a defect and not grounds for a refund.

4.3. No upstream guarantee. We do not control our upstream proxy providers and do not warrant their availability, bandwidth, latency, IP reputation, geographic coverage, or the accuracy of geolocation for any exit IP. Requested exit countries are honored on a best-effort basis subject to upstream availability.

4.4. No target-site guarantee. We do not warrant that any particular destination website or service will be reachable, will not block proxy traffic, will not present CAPTCHAs, or will return any particular content.

4.5. Failed requests where no payment settled cost you nothing. A settled payment for a request that our infrastructure demonstrably failed to serve may be considered under the discretionary process in the Refund Policy.

5. Acceptable Use

5.1. Your use of the Service is subject to the Acceptable Use Policy, which is incorporated into these Terms. Violation of the AUP is a material breach of these Terms.

5.2. You are solely responsible for ensuring that your use of the Service — including the destinations you access, the data you collect, and the actions your Agents perform — complies with all laws applicable to you and with the terms applicable to the destinations you access.

5.3. We apply automated safeguards including rate limiting, traffic metering, URL/domain blocklists, anomaly detection, and sanctions screening. You must not probe, bypass, or interfere with these safeguards.

6. Blocked and Unreachable Destinations

6.1. Some destinations are not reachable through the Service, by design. We block or refuse traffic to destinations that:

• appear on our security blocklists (including third-party phishing, malware, and abuse intelligence feeds, and our internal filters);
• are associated with child sexual abuse material (CSAM) or other illegal content;
• would cause us or our upstream providers to violate sanctions or export-control laws (see Section 7); or
• are disallowed by the acceptable-use policies of our upstream proxy providers. Because exit connectivity is supplied by third-party residential proxy networks, we enforce their content and destination restrictions in addition to our own. A destination that is reachable through other networks or providers may therefore be blocked through the Service.

6.2. Blocklists and provider restrictions change over time and are applied at our sole discretion. A blocked destination is not a defect of the Service and is not grounds for a refund, except as expressly provided in the Refund Policy.

6.3. Attempts to reach blocked destinations may be logged as abuse events and may lead to suspension under Section 8.

7. Export Control and Sanctions Compliance

7.1. We comply with export-control and economic-sanctions laws applicable to the operator and the relevant transaction, including applicable United Kingdom sanctions and export-control requirements and, where a sufficient nexus exists, sanctions administered by the U.S. Department of the Treasury's Office of Foreign Assets Control (OFAC) and other competent authorities.

7.2. The Service is not available to, and must not be accessed or used by or for the benefit of:

• any person, entity, jurisdiction, or region with whom applicable sanctions prohibit us from dealing;
• any designated or blocked person, or an entity owned by designated or blocked persons to the extent specified by applicable law; or
• any use that would violate export-control or sanctions laws, including routing traffic into, out of, or on behalf of parties in sanctioned jurisdictions.

7.3. You represent and warrant that neither you, your organization, nor any Agent acting on your behalf falls into any category in Section 7.2, and that your wallet address is not blocked or sanctioned.

7.4. Screening. Our controls may include payment-facilitator screening, wallet screening, and client-IP geolocation. These controls reduce risk but do not guarantee detection of every prohibited party or transaction. Traffic or payments that fail an applicable check may be rejected, and relevant records may be retained or reported where required by law (see the Privacy Policy).

7.5. We may refuse, suspend, or terminate service at any time to comply with sanctions or export-control obligations, without notice and without refund.

8. Suspension and Termination

8.1. We may throttle, suspend, or permanently block your wallet, sessions, or access to the Service, without prior notice, if we reasonably believe that:

• you or your Agent violated these Terms or the AUP;
• your traffic triggers our automated abuse, anomaly, or safety systems, including repeated attempts to reach blocked destinations or indicators of CSAM-related activity. Suspected CSAM activity may result in immediate restriction or permanent suspension and will be escalated and reported where required or permitted by applicable law;
• suspension is required by law, by a sanctions obligation, or by an upstream provider; or
• your use creates risk or liability for us, our upstream providers, or third parties.

8.2. Suspension or termination for cause does not entitle you to any refund, including for unused session time or byte cap.

8.3. Sessions terminate automatically at TTL expiry or byte-cap exhaustion. You may close a session early; early closure does not create a refund claim (see the Refund Policy).

9. Privacy

Our collection and handling of data is described in the Privacy Policy. The Service is designed to be data-minimal: our proxy application logs do not persist client IP addresses in plain form, full target URLs, or request/response bodies. Infrastructure and network providers may process connection metadata as described in the Privacy Policy.

10. Intellectual Property

10.1. We and our licensors retain all rights in the Service, its software, documentation, and branding. These Terms grant you a limited, revocable, non-exclusive, non-transferable right to use the Service as described here, for the duration of each paid request or session.

10.2. Open-source components we publish (such as the MCP server package) are licensed under their own license terms, which govern those components.

11. Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, OR UNINTERRUPTED OR ERROR-FREE OPERATION. WE DO NOT WARRANT THE CONDUCT, CONTENT, OR AVAILABILITY OF ANY DESTINATION ACCESSED THROUGH THE SERVICE, THE PERFORMANCE OF ANY UPSTREAM PROVIDER, OR THE OPERATION OF ANY BLOCKCHAIN NETWORK OR PAYMENT FACILITATOR.

12. Limitation of Liability

12.1. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT WILL APROXPAY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST DATA, BUSINESS INTERRUPTION, OR PROCUREMENT OF SUBSTITUTE SERVICES, ARISING OUT OF OR RELATED TO THE SERVICE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

12.2. TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICE WILL NOT EXCEED THE TOTAL AMOUNT YOU PAID TO US FOR THE SERVICE IN THE THIRTY (30) DAYS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

12.3. Some jurisdictions do not allow certain limitations; in those jurisdictions, the above limitations apply to the fullest extent permitted.

13. Indemnification

You will defend, indemnify, and hold harmless AproxPay and its owners, employees, contractors, and upstream providers from and against any claims, damages, liabilities, costs, and expenses (including reasonable legal fees) arising out of or related to: (a) your or your Agents' use of the Service; (b) your violation of these Terms, the AUP, or applicable law; (c) the destinations you access and the data you collect or transmit through the Service; or (d) your violation of any third party's rights.

14. Changes to These Terms

We may update these Terms from time to time. Each revision is identified by the Revision number and Effective date at the top of this document. Changes take effect on the stated effective date and apply to payments made on or after that date. Your continued use of the Service after the effective date constitutes acceptance of the updated Terms. Material changes will be reflected in the changelog below.

15. Governing Law and Disputes

15.1. These Terms are governed by the laws of England and Wales, without regard to conflict-of-laws rules.

15.2. Any dispute arising out of or relating to these Terms or the Service will be resolved exclusively in the courts of England and Wales, with proceedings ordinarily brought in London where permitted, except where mandatory law provides otherwise.

15.3. To the extent permitted by law, any claim must be brought within one (1) year after the cause of action accrues.

16. Miscellaneous

16.1. Entire agreement. These Terms, together with the documents incorporated by reference, are the entire agreement between you and AproxPay regarding the Service.

16.2. Severability. If any provision is held unenforceable, the remaining provisions remain in effect.

16.3. No waiver. Failure to enforce a provision is not a waiver of it.

16.4. Assignment. You may not assign these Terms; we may assign them in connection with a merger, acquisition, or sale of assets.

16.5. Force majeure. We are not liable for failures caused by events beyond our reasonable control, including failures of blockchain networks, payment facilitators, upstream providers, or internet infrastructure.

17. Contact

• Legal and general inquiries: legal@aproxpay.com
• Abuse reports: abuse@aproxpay.com

Document changelog