> For the complete documentation index, see [llms.txt](https://docs.pullbay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pullbay.com/documentation/introduction.md).

# Introduction

Pullbay is a data API platform. You send a request, you get structured data back. That's it.

Behind the scenes, we maintain a library of data extraction endpoints for popular platforms and services. See [Services Overview](/documentation/api-and-references/services-overview.md) for the current service catalog. Each endpoint is monitored, tested, and updated automatically — so you don't have to worry about scraper maintenance.

## The problem we solve

Scraping public data sounds simple until you try to do it reliably:

* Websites change their structure without warning
* Anti-bot systems block your requests
* Proxy management becomes a full-time job
* Rate limits and retries need careful handling
* Data formats vary and need constant normalization

Most teams either spend months building and maintaining scrapers, or give up and buy expensive enterprise solutions.

Pullbay sits in the middle. We handle the hard parts so you can focus on using the data.

## How it works

```
1. You send a request    →    GET /v1/app-store/reviews?app_id=123
2. Pullbay processes it  →    Fetches data, handles retries, normalizes output
3. You get JSON back     →    { "data": [...], "pagination": {...} }
4. Credits are deducted  →    Based on data returned
```

When you make a request, Pullbay:

1. **Validates your request** — Checks [authentication](/documentation/getting-started/authentication.md), parameters, and [rate limits](/documentation/plans-and-usage/rate-limits.md)
2. **Routes to the right extractor** — Each endpoint has specialized extraction logic
3. **Handles failures automatically** — Retries transient errors and recovers from common failures. See [Errors and Retries](/documentation/concepts/errors-and-retries.md)
4. **Normalizes the data** — Converts raw responses into consistent JSON schemas
5. **Returns results** — Delivers data with [pagination](/documentation/concepts/pagination.md) metadata and usage info

You don't see any of this complexity. You just get clean data.

## What you get

| Feature               | What it means for you                        |
| --------------------- | -------------------------------------------- |
| Pre-built endpoints   | No scraper development required              |
| Automatic maintenance | We fix breakages before you notice them      |
| Structured output     | Consistent JSON schemas across all endpoints |
| Credit-based pricing  | Pay for what you use, scale as needed        |
| Two pagination modes  | Manual control or automatic aggregation      |

## Who Pullbay is for

**Developers and engineers** — You need data from external platforms for your application. Skip the scraper development, make HTTP requests, get JSON back.

**Data and analytics teams** — You're building reports or datasets. Stable endpoints that just work, no Python scripts to debug or proxies to rotate.

**Automation builders** — You're using n8n or Make.com. Managed pagination endpoints give you all the data in one request, no loops required.

**Product teams** — You're building features that depend on external data. Reliable APIs with transparent health metrics.

## Who Pullbay is not for

* One-off scraping projects — A quick script might be faster
* Custom scraping needs — We don't support arbitrary URLs
* Real-time feeds — We optimize for thoroughness, not millisecond latency

## What Pullbay is not

Pullbay is not a general-purpose web scraper. You can't point it at any URL and expect results.

We provide curated, maintained endpoints for specific data sources. If a source isn't in our library, you can request it — but we focus on quality and reliability over coverage.

## Related topics

Use these pages as your next step:

* [Quickstart](/documentation/getting-started/quickstart.md) — Set up your account and make your first request
* [Authentication](/documentation/getting-started/authentication.md) — Learn how API keys work
* [First API Call](/documentation/getting-started/first-api-call.md) — Walk through a real request and response
* [Services Overview](/documentation/api-and-references/services-overview.md) — See available services and endpoint types
* [Pagination](/documentation/concepts/pagination.md) — Understand standard and managed pagination
* [Rate Limits](/documentation/plans-and-usage/rate-limits.md) — Plan request volume and backoff behavior


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pullbay.com/documentation/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.