# 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. On true it fetches the content; on false…

- **Canonical:** https://agentflare.org/guides/how-the-edge-verify-api-decides-access.html
- **Updated:** 2026-10-16
- **Category:** guides

## Key data

- **Track:** For publishers
- **Level:** Intermediate
- **Access:** Free / open
- **Updated:** 2026-10-16

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 it returns the 402 or 403 JSON to the crawler unchanged.

## Sources

1. [Header name: X-Crawler-Token](https://esa.aisa.one/cdn/open-verify.html)
2. [Open Verify specification (edge gateway ↔ verify provider)](https://esa.aisa.one/cdn/open-verify.html)
3. [AISA verify API for publishers and edge gateways (llms.txt)](https://esa.aisa.one/cdn/llms.txt)
4. [AISA publisher API documentation](https://esa.aisa.one/cdn/docs.html)

## Related

- [Pricing Content by Directory: Best Practices](https://agentflare.org/guides/pricing-content-by-directory-best-practices.html)
- [robots.txt, llms.txt & Sitemaps for AI Crawlers](https://agentflare.org/guides/robotstxt-llmstxt-sitemaps-for-ai-crawlers.html)
- [Getting Started with HTTP 402 Pay-Per-Crawl](https://agentflare.org/guides/getting-started-with-http-402-pay-per-crawl.html)
- [Crawler Tokens & Auto-Pay: A How-To](https://agentflare.org/guides/crawler-tokens-auto-pay-a-how-to.html)
- [Handling 402 and 403 Responses: An Error Reference for Agents](https://agentflare.org/guides/handling-402-and-403-responses-an-error-reference-for-agents.html)
- [Budgeting a Paid Crawl: Discover, Survey, Then Buy](https://agentflare.org/guides/budgeting-a-paid-crawl-discover-survey-then-buy.html)

---
_Part of AgentFlare, an agent-native data network powered by AISA. https://aisa.one/docs_