Automata 1RPC
  • LLM relay
    • Overview
  • Using the LLM API
    • Getting started
    • Models
    • Authentication
    • Payment
  • Errors
  • Web3 Relay
    • Overview
  • USING THE RPC API
    • Getting started
    • Design
  • Guide
    • Transaction sanitizers
    • Start using 1RPC
      • Supported networks
      • Features
      • About 1RPC
    • Build with 1RPC
    • Subscribe to 1RPC
      • How to make a payment
        • Fiat Payment
        • Crypto Payment
      • How to top up crypto payment
      • How to change billing cycle
      • How to change from fiat to crypto payment
      • How to change from crypto to fiat payment
      • How to upgrade or downgrade plan
      • How to cancel a plan
      • How to update credit card
      • How to view payment history
    • Zero-tracking
    • 1RPC Subscription Plans
  • Resources
    • 1RPC Demo
    • Specifications
    • Policy
    • Useful links
  • Getting help
    • Discord
Powered by GitBook
On this page
  1. USING THE RPC API

Getting started

1RPC.io provides a single endpoint that protects users' privacy and assets.

1rpc.io and 1rpc.ai have separate account systems. API keys for each platform are unique and cannot be used interchangeably.

  • Zero tracking: Enforces that user metadata is not retained once the request has been successfully relayed. This is also known as burn after relaying.

  • Metadata masking: Metadata attached to a user's request is placed with 1RPC's own.

  • Random dispatching: Requests are dispatched randomly to providers to break the linkage between wallets when requests are sent from different addresses. Shuffling requests in this manner makes it impossible to log the association between accounts with the same private key.

PreviousOverviewNextDesign

Last updated 3 hours ago