Hosting Signup
Sign up for a managed Pry instance in four steps. The whole flow is crypto-native — no account, no card, no KYC.
Step 1 — Create an invoice
Call the signup endpoint with your plan tier (pro, team, or
enterprise):
curl -X POST https://api.pryscraper.com/v1/hosting/signup \
-H "Content-Type: application/json" \
-d '{"plan": "pro"}'
Response:
{
"invoice_id": "inv_01J9...",
"plan": "pro",
"amount": "49.00",
"asset": "USDC",
"chain": "base",
"payment_address": "0x...",
"expires_at": "2026-09-01T12:00:00Z"
}
The invoice contains a payment address and is valid for a limited window — pay before it expires or request a new one.
Step 2 — Pay via x402
Send the exact amount to the payment_address from any wallet:
- USDC on Base (preferred)
- ETH on Ethereum
- SOL on Solana
Then submit the transaction to confirm it, the same way x402 pay-per-call payments are verified:
curl -X POST https://api.pryscraper.com/v1/hosting/pay \
-H "Content-Type: application/json" \
-d '{"invoice_id": "inv_01J9...", "tx_hash": "0x..."}'
Pry verifies the transaction on-chain (via the facilitator router, or EIP-7702 self-verify — see x402 Pay-per-call).
Step 3 — Receive your API key
Once the payment confirms, the signup response (or a follow-up status call) returns your credentials:
{
"status": "active",
"api_key": "pry_live_...",
"endpoint": "https://api.pryscraper.com",
"plan": "pro",
"renews_at": "2026-10-01T00:00:00Z"
}
Store the API key securely — it authenticates every request against your instance.
Step 4 — Start scraping
Use the key on any endpoint:
curl https://api.pryscraper.com/v1/scrape \
-H "Authorization: Bearer pry_live_..." \
-d '{"url": "https://example.com"}'
All 15 data domains and 76 MCP tools are available on your instance. See the API Reference for the full surface.
Enterprise
Enterprise plans are quoted individually — email [email protected] with your expected volume and we'll provision a custom instance.
Troubleshooting
| Problem | Fix |
|---|---|
| Invoice expired | Re-run POST /v1/hosting/signup for a fresh invoice |
| Payment not confirming | Check the tx on the chain explorer; confirm the asset + chain match the invoice |
| Wrong asset sent | Contact support with the tx hash — underpaid/overpaid invoices may need manual reconciliation |
| Key lost | Rotate from the dashboard or email [email protected] |