# No-KYC web reader API: no ID, no card, pay in crypto

> No-KYC web reader API: turn web pages into Markdown with no ID, no selfie and no card. Account-number login, crypto top-up, credits from $0.07/1K pages.

- URL: https://webreaderapi.com/no-kyc-web-reader-api/
- Last updated: 2026-10-22
- Publisher: WebReaderAPI (https://webreaderapi.com)

Many developers want an API key, not a compliance process. This page explains what you skip with WebReaderAPI, what you still agree to, and what we keep about you.

**Quick answer — Is there a web reader API that needs no KYC and no credit card?**

Yes. **WebReaderAPI**, a no-KYC web reader API, asks for no ID, no selfie, no company documents and no card: you sign in with an account number and pay in BTC, USDT, USDC, ETH, SOL, LTC. Credits cost $3.75 for 10,000 pages and fall to $0.07/1K pages, as of October 2026. The acceptable use policy and robots.txt still apply to every request.

## What you need, and what you do not

| Attribute | Value |
| --- | --- |
| Identity document or selfie | Not needed |
| Company papers or a work email | Not needed |
| Credit card | Not needed: crypto only |
| Login | An account number; adding an email is optional |
| Payment | BTC, USDT, USDC, ETH, SOL, LTC, from a $25 top-up |
| Rules that still apply | Acceptable use policy, robots.txt, site owners' refusals |
| What we keep | Account number, optional email, payment records, 30 days of logs with host names only |

## Why does an API need no identity check?

Because nothing in the service depends on knowing who you are. You pay before you use anything, so there is no credit to recover. The crawler's behaviour does not change with the customer: it follows each site's robots.txt and stops at every refusal, whoever sent the request.

An identity check would add a delay and a store of documents worth protecting, without making the service safer for the sites we read. We ask for what the service actually needs: a payment and a key.

## How does an account work without an email?

You get an account number when you sign up, and that number is your login. If you add an email, it gives you a way back into the account; without one, a lost number cannot be recovered.

Inside the account you create API keys, one per application or agent if you like, and revoke any of them when you want. Losing a key is not a problem; losing the account number without an email is, so store it in a password manager.

## What rules still apply without KYC?

Every rule that protects websites and people applies to every account. We respect robots.txt: our crawler identifies itself as WebReaderAPI, follows the rules written for it or for all robots, and does not read a page that a site disallows. Refused pages are not charged. If a site refuses our request, we return its answer: we never solve CAPTCHAs, log in to accounts, or try to get around a block or a paywall.

The [Acceptable Use Policy](https://webreaderapi.com/acceptable-use/) bans, among other things, Reading pages to collect personal data about private people, reading content behind a login or a paywall, child sexual abuse material, spam, fraud, and any use that breaks the law where you or we operate. Reports are checked by a person, and breaches end in suspension. Skipping the identity check never means skipping these rules.

## What do we keep about you?

Less than a typical API provider, because there is less to keep: your account number, an optional email, your payments and credits, and request logs that hold host names only, deleted after 30 days. No page content is stored.

We never hold an ID document, a selfie or a card number, so none can leak. The [privacy policy](https://webreaderapi.com/privacy/) lists every item and how long it stays.

## Who chooses a no-KYC web reader?

Mostly people for whom paperwork is the slowest part of trying a tool:

- **Independent developers** building an AI agent who want a key in minutes.
- **Small teams** without a company card, or in countries where card payments to foreign APIs fail.
- **Autonomous projects and bots** funded by a crypto wallet rather than a bank account.
- **Privacy-minded builders** who prefer to share as little as possible with each supplier.

## How do I get started without an ID?

1. Create an account and save the account number.
2. Top up from $25 in BTC, USDT, USDC, ETH, SOL, LTC: send the exact amount shown on the network shown, then click "I've sent the payment". The top-up is credited once it is confirmed.
3. Buy a pack, such as 10,000 pages for $3.75, and copy your API key.
4. Send your first URL to `https://webreaderapi.com/api/v1/read`, as shown in the [quick start](https://webreaderapi.com/docs/).

## What does the no-KYC web reader cost?

The same prices apply to every account: 10,000 pages for $3.75, 100,000 pages for $21.75, down to $0.07/1K pages on the largest pack. Credits never expire.

| Plan | Quantity | Price | Price per unit |
| --- | --- | --- | --- |
| Test | 10,000 pages | $3.75 | $0.38/1K pages |
| Build | 100,000 pages | $21.75 | $0.22/1K pages |
| Volume | 1,000,000 pages | $74.25 | $0.07/1K pages |

In every plan: Main-content extraction · JavaScript rendering when needed · Failed and refused pages not charged · Credits never expire

Packs are bought from a crypto balance topped up with at least $25. Prices in USD, set on 2026-10-22.

## No-KYC web reader: common questions

### Can I use WebReaderAPI without a credit card?

Yes, and in fact only without one: payments are in BTC, USDT, USDC, ETH, SOL, LTC. There is no card on file and nothing renews by itself.

### Does no KYC mean anything goes?

No. Every request follows robots.txt and stops when a site refuses, and the acceptable use policy applies to every account. Breaking it gets an account suspended.

### Will you ask for documents later, for example above some spend?

Our sign-up and top-up process does not ask for documents. We disclose records to authorities only when the law requires it, as the privacy policy says.

### What if I lose my account number?

Then the account cannot be recovered unless you added an email to it. Keep the number in a password manager, and add an email if you want a safety net.

### Can a bot or an agent pay for its own credits?

Yes, as long as someone sends the top-up from a wallet. The account then works like any other: buy a pack, use a key, watch the balance with `GET https://webreaderapi.com/api/v1/credits`.

---

WebReaderAPI: WebReaderAPI is a web reader API for AI agents that turns any public web page into clean Markdown, paid in crypto with no ID upload. Prepaid credits from $0.07/1K pages never expire, and robots.txt is respected. No KYC — no ID, no selfie, no documents. Pay in crypto.
