Skip to content

50% OFF your first payment. Limited time!

Claim your 50% Discount

Legal

Terms of service

What we commit to, what you commit to, and how either side ends the arrangement.

Last updated 2026-09-01

01The service

ArcRPC provides managed JSON-RPC, archive and data access to the Arc network on the plans published on the pricing page. Access is granted per key, scoped to the networks, methods, throughput and residency policy that the plan and your key configuration allow.

We may change endpoints, add methods or deprecate an API surface. A breaking change to a served API gets 90 days notice by email and an entry in the changelog. A change the Arc protocol forces on us gets as much notice as the protocol gives us, which is sometimes none, and we say so.

02Your account and keys

You are responsible for keeping keys secret and for traffic sent with them. Keys can be scoped by method and IP allowlist, and we recommend both for production. Tell us at [email protected] if a key leaks and we will revoke and reissue without charging for the rotation.

One account may hold multiple keys across both networks. Sharing a key with a third party is permitted; reselling raw access as your own RPC product is not, unless we agree that in writing.

03Fees and billing

Paid plans bill monthly in advance for the included allowance, and in arrears for overage at the published per-million rate. Invoices settle in USDC on Arc, by card, or by bank transfer. Annual commitments take the published discount and are not refundable mid-term.

Unused units roll over for one cycle and then expire. We will not silently reprice: a change to list price applies to your account at the start of the next term, after notice.

04Availability and credits

Enterprise plans carry a 99.99% monthly availability commitment with service credits, measured per region using the method published on the status page. Credits are the exclusive remedy for missed availability and are requested within 30 days of the affected month.

Other plans are served on the same infrastructure but carry no contractual availability commitment.

05Acceptable use

The acceptable use policy is part of these terms. In short: no traffic that attacks the network or other customers, no attempt to evade rate limits with account farming, and nothing illegal in your jurisdiction or ours.

06Liability

We are not liable for indirect or consequential loss, and aggregate liability is capped at the fees paid in the twelve months before the claim. Nothing here limits liability that cannot be limited by law.

ArcRPC is infrastructure. We do not custody funds, we never hold a signing key, and a response from our endpoint is not financial advice or a settlement guarantee. The settlement proof we return is the chain's certificate, not ours.

07Term and termination

Either side may end a monthly plan at the end of a cycle. We may suspend a key immediately for a security incident or an acceptable use breach, and will tell you why. On termination you can export your stream configuration and any stored gap reports for 30 days.

This page is a plain-language summary written for the website. The executed agreement governs, and Enterprise customers receive the full document during procurement. Questions go to [email protected].