Developer Documentation

Call. Pay. Receive.

AgentNorth is designed to feel like a normal HTTP API with an x402 payment step in front of paid resources.

Quickstart

Unauthenticated discovery endpoints can remain public, while paid API operations return HTTP 402 Payment Required until a valid x402 payment authorization is provided.

GET https://api.agentnorth.dev/health
GET https://api.agentnorth.dev/pricing
POST https://api.agentnorth.dev/v1/pdf

x402 payment flow

  1. Client requests a paid resource.
  2. AgentNorth responds with HTTP 402 and payment requirements.
  3. The client signs/authorizes payment.
  4. The request is retried with the x402 payment payload.
  5. Payment is verified/settled and the requested job runs.
Production network, facilitator and final prices should be configured only after testnet verification.

PDF Render

curl -X POST https://api.agentnorth.dev/v1/pdf \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","format":"A4","printBackground":true}'

Markdown

POST /v1/markdown
{
  "url": "https://example.com"
}

Screenshot

POST /v1/screenshot
{
  "url": "https://example.com",
  "fullPage": true
}

Errors

Status Meaning
400 Invalid request
402 Payment required
408 Browser job timed out
429 Queue or rate limit reached
500 Unexpected server error