Some document APIs give you raw text blocks. Some give you structured JSON. Some expect you to handle storage, polling, reconstruction, and final output on your side.
That can be the right approach if you are building a document-intelligence system. But many developers are solving a simpler problem:
Take a scanned PDF in. Get a finished searchable PDF out.
That is what XRPpdf's API is designed to do.
The workflow
Submit a scanned PDF:
curl -X POST https://xrppdf.com/api/v1/ocr \
-H "Authorization: Bearer xrpocr_live_YOUR_KEY" \
-F "[email protected]"
You get back a job ID. Then you can:
- poll the job status
- subscribe to a webhook
- download the finished searchable PDF
No storage bucket setup. No separate rendering step. No manual rebuild of a text layer.
What the API returns
XRPpdf is not a raw extraction API. It is a finished-output API.
- Input: scanned PDF
- Output: searchable PDF with an embedded text layer
- Authentication: API key or session bearer token
- Idempotency: supported for safe retries
- Webhooks: signed with HMAC-SHA256 and retried automatically
- Concurrency: scaled for batch use
If your application ultimately needs a user-ready PDF, returning the final artifact is often simpler than returning intermediate data.
Pricing
Live XRP/RLUSD feed: $1.42 per XRP.
Current public tiers:
| Tier | XRP cost | Pages | Effective rate | Effective USD/page |
|---|---|---|---|---|
| Bundle 25 | 1 XRP | 25 | 0.04 XRP/page | $0.0567 |
| Bundle 100 | 2 XRP | 100 | 0.02 XRP/page | $0.0283 |
| Pro | 8 XRP | 1,000 | 0.008 XRP/page | $0.0113 |
| Scale | 30 XRP | 10,000 | 0.003 XRP/page | $0.0043 |
Credits never expire. Buy once, use them over time.
Where this API fits best
XRPpdf works well when:
- you want searchable PDFs rather than raw OCR primitives
- your app needs a document a human can immediately open and search
- you want one API for both manual and automated workflows
- you do not want to stand up extra infrastructure around OCR
- short document retention matters to you
Example use cases
Archive cleanup
You have years of scanned PDFs that are visually readable but not searchable. Submit them in bulk, download searchable outputs, and re-store them in your archive.
Internal tools
An operations dashboard receives uploaded scans and needs to return a usable searchable PDF to staff. A finished-output API keeps the integration small.
Customer-facing upload flows
If users upload scans and expect a clean result back, you can hand them the searchable file directly instead of building a custom post-processing layer.
Short retention is built in
XRPpdf's retention model is intentionally narrow:
- trial uploads: deleted within 1 hour
- paid uploads: deleted immediately after successful processing
- outputs: deleted within 24 hours
That makes it a better fit for workflows that want cloud convenience without long-lived uploaded documents.
Quick start
- Link an XRP wallet at xrppdf.com
- Fund your account with XRP page credits
- Create an API key in the dashboard
- Call
POST /api/v1/ocr
Full docs are at /docs, including webhook delivery, status polling, and authentication examples.
Want the simplest version? Try XRPpdf free -> - 3 pages, no signup.