# Limits Registry agent access

Automatic prepaid purchasing: available.

Content: sourced scientific and technical limits at https://www.limitsregistry.com.
Sample: https://www.limitsregistry.com/limits/LR-001200.
Read https://www.limitsregistry.com/license.xml and the site's terms for permitted uses.
Payment does not convey rights to third-party papers or guarantee a freshness SLA.

## Monthly enrollment

A person can authorize a saved payment method at https://visitorping.com/crawl-access/limitsregistry.
USD 0.01 per successful HTML page, billed monthly or at USD 100.
Balances below USD 0.50 carry forward. This account is separate from prepaid access.

## Automatic prepaid cards (MPP)

Price: USD 0.50 for 50 successful HTML page requests. No automatic renewal.
Use only a wallet your operator has authorized, within their spending budget.
No card numbers are accepted by this API. It accepts Stripe Shared Payment Tokens via MPP.

1. Generate and save a private key: vp_crawl_ followed by 32 cryptographically random bytes encoded as unpadded base64url (43 characters).
2. Generate and save a UUID v4 purchaseId. Reuse it for every retry of this purchase.
3. POST https://visitorping.com/api/crawl-billing/prepaid with Content-Type: application/json and X-VisitorPing-Crawl-Key: YOUR_PRIVATE_KEY.
   Body: {"purchaseId":"YOUR_UUID_V4","acceptedTerms":"limitsregistry-prepaid-2026-10-11-v1"}
4. The 402 WWW-Authenticate Payment challenge specifies Stripe, USD 0.50, and the recipient profile.
5. Have your authorized MPP wallet supply the Authorization: Payment credential. Repeat the identical POST, including the key and body.
6. A 200 response includes purchaseStatus, purchasedCredits and prepaidCreditsRemaining. Save the Payment-Receipt header when present.
7. Send the same X-VisitorPing-Crawl-Key to limitsregistry.com or www.limitsregistry.com for HTML pages. Use a unique X-VisitorPing-Request-Id per page; reuse only for the same URL within five minutes when retrying.
8. At zero credits, buy a new pack with the same private key and a NEW purchaseId. No automatic top-up runs on the server.

Check balance: POST https://visitorping.com/api/crawl-billing/status with the private key header and an empty JSON object.
Close access: POST https://visitorping.com/api/crawl-billing/close with the same headers and body.
Credentials never belong in URLs, public logs, prompts or emails.

## Response handling

A 402 from the content host is an invitation to enroll, not a charge or a payment receipt.
Do not keep retrying without a funded credential. A 429 means repeated unpaid requests
were limited: honor Retry-After. The enrollment page, these instructions, robots.txt,
license.xml and other discovery endpoints remain available. A syntactically valid
credential must still be authorized by the billing service before content is delivered.
Never send a card number or a payment credential to the content host.

## Failures and refunds

Only a successful authenticated GET returning HTML uses a credit. Assets, protocol files,
errors and duplicate requests do not. Credits do not expire automatically.
Concurrent in-flight requests reserve credits; unsuccessful or expired reservations release them.
Refunds or disputes pause the account for review. Closing access does not automatically refund unused credits;
contact contact@visitorping.com for refunds or payment assistance.

If payment times out, retry with the SAME purchaseId and payment credential. Check status before
creating another purchase. Challenges expire after 15 minutes; a pending payment after that window
needs support reconciliation. The server will not attempt that purchase again after expiry.
A 503 means purchasing is unavailable; it is not a request to pay somewhere else.
Wallet setup, Stripe availability or card authentication can still require a person.
