Three pipes, no dumping ground.
Every message lands with the team that can act on it, and each route states how fast you hear back. Most questions are answered in the docs; everything else is below.
Dedicated nodes, custom SLAs, contracts
Dedicated or co-located fleet, private throughput, custom datasets, procurement and security review. The first call is technical scoping with an engineer, not a sales pitch.
Response within one business day
Keys, quotas, connections, billing
Connection errors, rate limits, key management, invoices. Include your key prefix (never the full key) and the endpoint you're hitting. It saves a round trip.
Response within one business day · priority on Build and Enterprise
Historical exports, custom datasets, integrations
Manual captured-history exports, custom dataset builds, research collaborations, platform integrations, or reselling the feeds inside your product. Bring a date range and schema sketch if you have them.
Response within two business days
The short answers.
The four questions inbound mail asks most. The full set lives on the product and pricing pages.
Get an API key and put it in the URL: https://rpc.arcrpc.com/v1/{API_KEY} for mainnet, rpc-testnet.arcrpc.com for testnet. Any EVM library works unchanged. For streams, point a gRPC client at grpc.arcrpc.com:443 and send the key as x-api-key metadata.
Yes, on Enterprise: isolated Arc execution and consensus nodes, a region of your choice, a custom endpoint domain and a signed SLA with credits.
Yes. Invoices can settle in USDC on Arc, the asset you already hold for gas. Card and bank transfer work too.
Not yet. A Type I engagement is in progress and Type II is targeted for Q2 2027. We would rather say that plainly than imply coverage we do not have.
No question, just want to try it?
Pro is one key for Arc mainnet and testnet, live in minutes, month-to-month billing. No call required.