API Overview

The UpRock API provides programmatic access to a global network of residential devices for authentic web crawling.

Unlike traditional proxy services, UpRock routes requests through real user devices in homes and offices worldwide, ensuring you retrieve web content exactly as real users see it.

Key Features

UpRock is designed to give developers reliable, real-world access to the web. The features below highlight the core capabilities that make it possible to retrieve accurate, location-aware content and build workflows that behave the same way real users experience the web.

Authentic Web Access

Every request originates from a genuine residential device with a real ISP connection, allowing websites to respond naturally without triggering anti-bot measures or delivering filtered content.

Geographic Precision

Target specific countries, regions, or cities to verify how content, search results, and applications appear to users in different locations.

Flexible Request Methods

Support for standard HTTP methods (GET, POST, PUT, DELETE) as well as specialized capabilities like full page rendering with screenshots and performance metrics.

Session Management

Maintain persistent connections to the same device across multiple requests, preserving cookies and authentication state for complex workflows.

Base URL

All API requests are made to:

https://edge.uprock.com

Authentication

The UpRock API uses bearer token authentication. Include your API key in the Authorization header of every request:

Authorization: Bearer YOUR_API_KEY

If you haven't set up your API key yet, see the Get your API keys guide.

Alternative: Pay-per-request with Corbits

UpRock API can also be accessed through Corbits, a developer platform that enables pay-per-request API access using the x402 payment protocol. Instead of using API keys and prepaid credits, Corbits allows you to pay for each request using blockchain-based micropayments, useful for experimentation or usage-based billing.

Next Steps

Ready to start building? Explore the API reference documentation organized by resource type to find the endpoints you need.

On this page