AgentFlareGuides · free & open
Guides for agents, publishers and data users
10 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.
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.
https://esa.aisa.one/api/v1/access/verify
For agent developers
Fetch paid content from code: tokens, 402 handling, budgets and clients.
Getting Started with HTTP 402 Pay-Per-Crawl
An HTTP 402 means the content is for sale, not blocked. Register for a crawler token, check your balance, retry the original URL with X-Crawler-Token, then…
5 steps · 5 code samplesBeginner · 7 minCrawler Tokens & Auto-Pay: A How-To
Crawling AISA-protected sites takes two credentials: a crawler token sent in X-Crawler-Token, and a session token for account calls. This guide covers where…
6 steps · 6 code samplesBeginner · 7 minHandling 402 and 403 Responses: An Error Reference for Agents
Every AISA denial arrives as self-describing JSON: read the error field, act on the guidance block, and report plainly to the user. This guide covers each…
6 steps · 6 code samplesIntermediate · 6 minBudgeting a Paid Crawl: Discover, Survey, Then Buy
Crawl a whole AgentFlare-style site on a fixed budget by reading free discovery files first, choosing from free teasers, then buying only chosen deep files.…
5 steps · 5 code samplesIntermediate · 7 minBuilding a Pay-Per-Crawl Client for Your Agent
Build one small client that registers or logs in, crawls with the X-Crawler-Token header and an honest User-Agent, reads charge receipt headers, and…
6 steps · 6 code samplesFor publishers
Price, open or block directories and make a site readable by agents.
Pricing Content by Directory: Best Practices
Price deep content per directory by sorting each URL into a free, pay, or block rule. This guide walks through the AgentFlare pricing.json, from tiers and…
6 steps · 6 code samplesBeginner · 6 minrobots.txt, llms.txt & Sitemaps for AI Crawlers
robots.txt, llms.txt and sitemap.xml are the free files an agent reads before it spends anything. They lead to pricing.json, which sets the per-directory…
6 steps · 4 code samplesIntermediate · 6 minHow the Edge Verify API Decides Access
The edge gateway calls POST /api/v1/access/verify before fetching from origin and reads one field, accessGranted. On true it fetches the content; on false…
6 steps · 2 code samplesUsing AgentFlare data
What each AgentFlare dataset contains, what it costs, and how to read it.
Reading .data.json: A Field Guide for Agents
Every AgentFlare .data.json shares one envelope of top-level fields, and only the data object changes by vertical. Fetch it with an X-Crawler-Token header;…
5 steps · 5 code samplesBeginner · 6 minUsing AgentFlare Social, Predictions and Crypto Data
AgentFlare serves social, predictions and crypto data as paid .data.json files, priced per request at 0.005 USD for social and 0.01 USD for predictions and…
5 steps · 4 code samplesHow 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
- AISA Agent Integration Guide — API reference esa.aisa.one
- AISA onboarding: HTTP 402 Payment Required esa.aisa.one
- AISA bot flow (llms.txt) esa.aisa.one
- AISA agent skill (SKILL.md) esa.aisa.one
- AISA pay-per-crawl platform overview (llms.txt) esa.aisa.one
- AISA verify API for publishers and edge gateways (llms.txt) esa.aisa.one
- AISA publisher API documentation esa.aisa.one
- Open Verify specification (edge gateway ↔ verify provider) esa.aisa.one