AgentFlare

Guides · free & open

Guides for agents, publishers and data users

8 free, step-by-step guides with runnable code: fetching paid content with HTTP 402 and a crawler token, pricing a site for AI agents, and reading every AgentFlare dataset. Written from the AISA protocol docs.

Guides8
Tracks2
Code samples40
AccessFreeno metering
✓ Open accessFree

You're reading the full report — free for humans. The machine-readable dataset for this section is open to all agents too — no payment required.

⚡ Agents: fetch .data.json → agents: allowed (no charge) · verify at https://esa.aisa.one/api/v1/access/verify
One request, three outcomesHow a paid fetch works on the AISA network
Pay-per-crawl request flow: 1. Your agent to Publisher edge: GET file + X-Crawler-Token; 2. Publisher edge to AISA: authorize token against price rule; 3. AISA to Publisher edge: grant: deduct price once; 4. Publisher edge to Your agent: 200 content (+ charge receipt); 5. Publisher edge to Your agent: or 402 JSON: error + guidance; 6. Publisher edge to Your agent: or 403 access_blockedYour agentcrawler tokenPublisher edgeCDN gatewayAISAverify + balance1. GET file + X-Crawler-Token2. authorize token against price rule3. grant: deduct price once4. 200 content (+ charge receipt)5. or 402 JSON: error + guidance6. or 403 access_blocked
Price per paid request, by directoryAgentFlare pricing.json · deep files (.data.json, .full.md) only; HTML and .md are free
USD per request: /research/ $0.02, /scholar/ $0.02, /crypto/ $0.01, /markets/ $0.01, /social/ $0.01, /predictions/ $0.01, /news/ $0.005/research/$0.02/scholar/$0.02/crypto/$0.01/markets/$0.01/social/$0.01/predictions/$0.01/news/$0.005

For agent developers

Fetch paid content from code: tokens, 402 handling, budgets and clients.

Beginner · 7 min

Getting Started with HTTP 402 Pay-Per-Crawl

A 402 means the content is for sale, not blocked. Register, get a crawler token, fund the balance if needed, retry the original URL with the token, and read…

6 steps · 6 code samplesBeginner · 6 min

Crawler Tokens & Auto-Pay: A How-To

Use the crawler token in the X-Crawler-Token header for publisher requests, and the session token as a Bearer header for account APIs only. Fetch your…

6 steps · 6 code samplesBeginner · 6 min

Handling 402 and 403 Responses: An Error Reference for Agents

AISA denials arrive as 402 or 403 JSON with an error code and a guidance block. This guide maps each code to the next action and to what your agent should…

5 steps · 5 code samplesIntermediate · 6 min

Budgeting a Paid Crawl: Discover, Survey, Then Buy

Crawl a whole site on a fixed budget by reading the free discovery files first, then using free summaries to choose, and buying only the .data.json or…

5 steps · 5 code samplesIntermediate · 7 min

Building a Pay-Per-Crawl Client for Your Agent

A pay-per-crawl client needs only four moves: get a crawler token, send it with an honest User-Agent, read receipt headers, and branch on the error code in…

6 steps · 6 code samples

For publishers

Price, open or block directories and make a site readable by agents.

Intermediate · 6 min

Pricing Content by Directory: Best Practices

Directory rules let you keep teasers free while charging per request for deep files. This guide walks through the AgentFlare pricing.json: pay, allow and…

6 steps · 5 code samplesBeginner · 6 min

robots.txt, llms.txt & Sitemaps for AI Crawlers

robots.txt, llms.txt and sitemap.xml are free discovery files that tell AI agents where to look, and pricing.json maps which directories cost money.…

5 steps · 5 code samplesIntermediate · 6 min

How the Edge Verify API Decides Access

The edge gateway calls POST /api/v1/access/verify before fetching from origin and reads one field, accessGranted. Denials come back as 402 or 403 JSON that…

5 steps · 2 code samples

How this page is made. Guides are written from the AISA agent and publisher documentation and AgentFlare's own files, checked for headers, endpoints, error codes and figures that the sources do not contain, and refreshed weekly. Everything in this section, including .data.json, is free to agents.

Sources & citations

  1. AISA Agent Integration Guide — API reference esa.aisa.one
  2. AISA onboarding: HTTP 402 Payment Required esa.aisa.one
  3. AISA bot flow (llms.txt) esa.aisa.one
  4. AISA agent skill (SKILL.md) esa.aisa.one
  5. AISA pay-per-crawl platform overview (llms.txt) esa.aisa.one
  6. AISA verify API for publishers and edge gateways (llms.txt) esa.aisa.one
  7. AISA publisher API documentation esa.aisa.one
  8. Open Verify specification (edge gateway ↔ verify provider) esa.aisa.one

Related