Get started with AARN
Inspect a public request schema, receive the x402 payment challenge, and integrate an x402-compatible buyer. Browsing this guide and inspecting an unpaid challenge do not require a wallet or make a payment.
1. Choose an endpoint
Services use the canonical api.aarn.space origin. This marketing site at aarn.space does not proxy requests or collect payments.
Web Read · POST https://api.aarn.space/v1/web/read · entry price 0.002 USDC · one URL
Web Content Extraction · POST https://api.aarn.space/v1/web-content/extract · entry price 0.005 USDC · up to five URLs
Web Research · POST https://api.aarn.space/v1/web/research · entry price 0.50 USDC · feature-gated
The live x402 manifest and each endpoint's challenge are authoritative about purchasable resources and payment requirements, including network, asset, amount, and payee.
2. Inspect the payment challenge (no payment)
This example uses the exact Web Read request schema. It deliberately omits PAYMENT-SIGNATURE. It is an unpaid protocol probe: it does not authorize execution or initiate a transaction.
curl -i --request POST 'https://api.aarn.space/v1/web/read' \
--header 'Content-Type: application/json' \
--data '{"url":"https://example.com","output_format":"markdown","include_metadata":true,"include_links":false}'When the resource is configured and available, the expected response is HTTP 402 Payment Required, with an encoded PAYMENT-REQUIRED response header describing the x402 v2 requirements. If the backend isn't ready, you may receive an error instead. A 402 is an invitation to negotiate payment — not a successful delivery or proof of revenue.
3. Connect a compatible buyer
Use an x402-compatible client/wallet in your own agent application. Inspect the returned PAYMENT-REQUIRED header, validate the exact recipient, network and amount against your purchasing policy, and only then authorize and submit a payment signature as specified by the current API contract. Any payment or wallet operation is your explicit decision, not an action on this site.
Safety and availability
Research may return HTTP 503 while its readiness flags are off. HTTP 402 only proves a challenge was issued. Full success requires actual execution, QA, delivery and settlement; do not treat a signature, a listing, or a 402 response as proof of a completed paid job.
4. Read the returned result
On successful authorized execution, the API returns a machine-readable response according to its published schema. Web Read and Extraction results include normalized content and per-URL errors when applicable. Web Research (when enabled) includes evidence-linked findings and explicit missing information. See Web Read's request example or the research request fields.
Need help?
Contact [email protected]. See the service terms for the operational boundaries and conditions.