{ "@context": "https://agentflare.org/schema", "type": "Article", "tier": "L2-full", "title": "Using AgentFlare Social, Predictions and Crypto Data", "description": "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…", "canonical": "https://agentflare.org/guides/using-agentflare-social-predictions-and-crypto-data.html", "category": "guides", "updated": "2026-10-16", "generated_at": "2026-10-16T00:37:01.652Z", "facts": [ { "label": "Track", "value": "Using AgentFlare data" }, { "label": "Level", "value": "Beginner" }, { "label": "Access", "value": "Free / open" }, { "label": "Updated", "value": "2026-10-16" } ], "data": { "topic": "Using AgentFlare Social, Predictions and Crypto Data", "track": "data", "access": "free", "generated_at": "2026-10-16T00:37:01.652Z", "difficulty": "Beginner", "tldr": "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 crypto. Send X-Crawler-Token and read the documented fields.", "intro": "This guide is for developers and agent builders who want structured social, prediction-market and crypto data from agentflare.org. You will learn which directories are metered and what each costs per request, which top-level and nested fields each .data.json file contains, how to authenticate with the crawler header, and how to fetch and parse one index file from each dataset in Python. Every field name and price below comes straight from the published field references and pricing.json.", "prerequisites": [ "A crawler token from AISA, shown as YOUR_CRAWLER_TOKEN below", "curl, or Python 3 with the requests package", "Basic familiarity with reading JSON" ], "steps": [ { "title": "Separate free pages from paid files", "body": "AgentFlare keeps index pages, .html articles, .md teasers, llms.txt, sitemap.xml and robots.txt free (tier L1_free). Complete datasets and full analysis are the paid tier L2_paid: every *.data.json and *.full.md file, metered per request. In pricing.json the directory prices are social 0.005 USD, predictions 0.01 USD and crypto 0.01 USD. Because index.data.json ends in .data.json, it is billed like any other file in its directory.", "code": null, "sources": [ "S5" ] }, { "title": "Send the X-Crawler-Token header", "body": "Identify your crawler with the X-Crawler-Token header. It replaces the earlier name X-AISA-Crawler-Token, which older AISA documentation pages still show. Never put the token in Authorization: Bearer, because that header is reserved for the gateway layer. The example fetches the Social Pulse index, a file priced at 0.005 USD per request. Replace YOUR_CRAWLER_TOKEN with your own token.", "code": { "lang": "bash", "text": "curl -s 'https://agentflare.org/social/index.data.json' \\\n -H 'X-Crawler-Token: YOUR_CRAWLER_TOKEN'" }, "sources": [ "S1", "S2", "S5" ] }, { "title": "Read the Social Pulse category fields", "body": "Every file carries the same envelope: type, tier, title, description, canonical, category, updated, generated_at, facts, data, analysis_md, sources, related, pricing and powered_by. In the social index, data.categories[] lists id, name, headline, url and a stats object with posts, likes, views, medLikes and verified, all numbers. Per-item files follow the pattern /social/.data.json.", "code": { "lang": "python", "text": "import requests\n\nurl = 'https://agentflare.org/social/index.data.json'\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\ndoc = requests.get(url, headers=headers).json()\n\nfor c in doc['data']['categories']:\n s = c['stats']\n print(c['id'], c['name'], s['posts'], s['likes'],\n s['views'], s['medLikes'], s['verified'])" }, "sources": [ "S2" ] }, { "title": "Pull prediction events, then one event file", "body": "The predictions index has data.count, data.total_volume_usd and data.events[] with title, slug, leading, probability, change_pp_30d and volume_usd. Each event has its own file at /predictions/.data.json. That file adds data.event, data.slug, data.volume_usd, data.volume_24h_usd, data.end_date, data.tags and data.markets[], where each market has question, odds[] and volume_usd. Each request costs 0.01 USD.", "code": { "lang": "python", "text": "import requests\n\nbase = 'https://agentflare.org/predictions/'\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\nidx = requests.get(base + 'index.data.json', headers=headers).json()\n\nfor e in idx['data']['events']:\n print(e['slug'], e['leading'], e['probability'],\n e['change_pp_30d'], e['volume_usd'])\n\nfirst = idx['data']['events'][0]\nurl = base + first['slug'] + '.data.json'\nev = requests.get(url, headers=headers).json()\nfor m in ev['data']['markets']:\n print(m['question'], m['odds'], m['volume_usd'])" }, "sources": [ "S3", "S5", "S1" ] }, { "title": "Fetch crypto market and coin data", "body": "The crypto index and the dated file /crypto/YYYY-MM-DD.data.json share one layout: data.total_market_cap_usd, data.coin_count, data.advancers_24h, data.stablecoin_share_pct, data.top[] and data.trending[]. A coin file such as /crypto/zcash.data.json holds price_usd, market_cap_rank, fdv_usd, change_pct, volume_24h_usd, ath_usd, atl_usd, supply, history_90d, analysis, faq and newswire. Each request costs 0.01 USD.", "code": { "lang": "python", "text": "import requests\n\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\nurl = 'https://agentflare.org/crypto/zcash.data.json'\nd = requests.get(url, headers=headers).json()['data']\n\nprint(d['name'], d['symbol'], d['price_usd'])\nprint(d['market_cap_rank'], d['change_pct']['h24'], d['change_pct']['d7'])\nprint(d['ath_usd'], d['ath_date'], d['atl_usd'], d['atl_date'])\nprint(d['supply']['circulating'], d['supply']['max'])\nfor p in d['history_90d'][:3]:\n print(p['date'], p['price'])" }, "sources": [ "S4", "S5", "S1" ] } ], "reference": { "title": "Datasets, key fields and price per request", "columns": [ "File", "Key data fields", "Price (USD)" ], "rows": [ [ "/social/index.data.json", "data.categories[].id, name, headline, url, stats.posts, likes, views, medLikes, verified", "0.005" ], [ "/predictions/index.data.json", "data.count, total_volume_usd, events[].slug, leading, probability, change_pp_30d, volume_usd", "0.01" ], [ "/predictions/.data.json", "data.event, volume_24h_usd, end_date, tags, markets[].question, odds, volume_usd", "0.01" ], [ "/crypto/index.data.json", "data.total_market_cap_usd, coin_count, advancers_24h, stablecoin_share_pct, top[], trending[]", "0.01" ], [ "/crypto/YYYY-MM-DD.data.json", "Same layout as the crypto index", "0.01" ], [ "/crypto/zcash.data.json", "data.price_usd, market_cap_rank, fdv_usd, change_pct, ath_usd, atl_usd, supply, history_90d, faq, newswire", "0.01" ] ], "sources": [ "S2", "S3", "S4", "S5" ] }, "pitfalls": [ { "text": "Do not send the crawler token in Authorization: Bearer. That header is reserved for the gateway layer; use X-Crawler-Token instead.", "source": "S1" }, { "text": "Older AISA pages still show X-AISA-Crawler-Token. Use X-Crawler-Token, the name in the Open Verify specification.", "source": "S1" }, { "text": "Prices differ by directory: social is 0.005 USD per request, predictions and crypto are 0.01 USD. Budget loops over many event or coin files accordingly.", "source": "S5" }, { "text": "Dated files use a YYYY-MM-DD placeholder in their name, for example atp-fokina-tiafoe-YYYY-MM-DD.data.json. Substitute a real date before requesting.", "source": "S3" } ], "takeaways": [ "Only .data.json and .full.md files are paid; index pages, .html articles and .md teasers stay free.", "Social costs 0.005 USD per request; predictions and crypto cost 0.01 USD each.", "Authenticate with X-Crawler-Token, then read data.categories, data.events or data.top from the index files." ], "faq": [ { "q": "How much does an AgentFlare .data.json request cost?", "a": "Per pricing.json, social is 0.005 USD per request, predictions is 0.01 USD and crypto is 0.01 USD. Billing is per request for files matching *.data.json or *.full.md in each directory." }, { "q": "Which header carries the crawler token?", "a": "Use X-Crawler-Token. It replaces X-AISA-Crawler-Token, which older AISA documentation still shows. Do not use Authorization: Bearer for the token, since that header is reserved for the gateway layer." }, { "q": "What fields does a prediction event file contain?", "a": "Besides the common envelope, data holds event, slug, volume_usd, volume_24h_usd, end_date, tags and markets. Each market has question, odds and volume_usd. The index adds count, total_volume_usd and events with probability and change_pp_30d." }, { "q": "Where do I find price history for a coin?", "a": "A per-coin file such as /crypto/zcash.data.json has data.history_90d, an array of objects with date and price. It also has change_pct for h24, d7, d30 and d90, plus ath_usd, ath_date, atl_usd and atl_date." } ], "sources": [ { "title": "Header name: X-Crawler-Token", "url": "https://esa.aisa.one/cdn/open-verify.html", "domain": "esa.aisa.one" }, { "title": "AgentFlare Social Pulse .data.json field reference", "url": "https://agentflare.org/social/index.html", "domain": "agentflare.org" }, { "title": "AgentFlare Predictions .data.json field reference", "url": "https://agentflare.org/predictions/index.html", "domain": "agentflare.org" }, { "title": "AgentFlare Crypto .data.json field reference", "url": "https://agentflare.org/crypto/index.html", "domain": "agentflare.org" }, { "title": "AgentFlare pricing.json (directory price map)", "url": "https://agentflare.org/pricing.json", "domain": "agentflare.org" } ] }, "analysis_md": "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 crypto. Send X-Crawler-Token and read the documented fields.\n\nThis guide is for developers and agent builders who want structured social, prediction-market and crypto data from agentflare.org. You will learn which directories are metered and what each costs per request, which top-level and nested fields each .data.json file contains, how to authenticate with the crawler header, and how to fetch and parse one index file from each dataset in Python. Every field name and price below comes straight from the published field references and pricing.json.\n\n## Before you start\n\n- A crawler token from AISA, shown as YOUR_CRAWLER_TOKEN below\n- curl, or Python 3 with the requests package\n- Basic familiarity with reading JSON\n\n## Step by step\n\n### 1. Separate free pages from paid files\n\nAgentFlare keeps index pages, .html articles, .md teasers, llms.txt, sitemap.xml and robots.txt free (tier L1_free). Complete datasets and full analysis are the paid tier L2_paid: every *.data.json and *.full.md file, metered per request. In pricing.json the directory prices are social 0.005 USD, predictions 0.01 USD and crypto 0.01 USD. Because index.data.json ends in .data.json, it is billed like any other file in its directory.\n\n### 2. Send the X-Crawler-Token header\n\nIdentify your crawler with the X-Crawler-Token header. It replaces the earlier name X-AISA-Crawler-Token, which older AISA documentation pages still show. Never put the token in Authorization: Bearer, because that header is reserved for the gateway layer. The example fetches the Social Pulse index, a file priced at 0.005 USD per request. Replace YOUR_CRAWLER_TOKEN with your own token.\n\n```bash\ncurl -s 'https://agentflare.org/social/index.data.json' \\\n -H 'X-Crawler-Token: YOUR_CRAWLER_TOKEN'\n```\n\n### 3. Read the Social Pulse category fields\n\nEvery file carries the same envelope: type, tier, title, description, canonical, category, updated, generated_at, facts, data, analysis_md, sources, related, pricing and powered_by. In the social index, data.categories[] lists id, name, headline, url and a stats object with posts, likes, views, medLikes and verified, all numbers. Per-item files follow the pattern /social/.data.json.\n\n```python\nimport requests\n\nurl = 'https://agentflare.org/social/index.data.json'\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\ndoc = requests.get(url, headers=headers).json()\n\nfor c in doc['data']['categories']:\n s = c['stats']\n print(c['id'], c['name'], s['posts'], s['likes'],\n s['views'], s['medLikes'], s['verified'])\n```\n\n### 4. Pull prediction events, then one event file\n\nThe predictions index has data.count, data.total_volume_usd and data.events[] with title, slug, leading, probability, change_pp_30d and volume_usd. Each event has its own file at /predictions/.data.json. That file adds data.event, data.slug, data.volume_usd, data.volume_24h_usd, data.end_date, data.tags and data.markets[], where each market has question, odds[] and volume_usd. Each request costs 0.01 USD.\n\n```python\nimport requests\n\nbase = 'https://agentflare.org/predictions/'\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\nidx = requests.get(base + 'index.data.json', headers=headers).json()\n\nfor e in idx['data']['events']:\n print(e['slug'], e['leading'], e['probability'],\n e['change_pp_30d'], e['volume_usd'])\n\nfirst = idx['data']['events'][0]\nurl = base + first['slug'] + '.data.json'\nev = requests.get(url, headers=headers).json()\nfor m in ev['data']['markets']:\n print(m['question'], m['odds'], m['volume_usd'])\n```\n\n### 5. Fetch crypto market and coin data\n\nThe crypto index and the dated file /crypto/YYYY-MM-DD.data.json share one layout: data.total_market_cap_usd, data.coin_count, data.advancers_24h, data.stablecoin_share_pct, data.top[] and data.trending[]. A coin file such as /crypto/zcash.data.json holds price_usd, market_cap_rank, fdv_usd, change_pct, volume_24h_usd, ath_usd, atl_usd, supply, history_90d, analysis, faq and newswire. Each request costs 0.01 USD.\n\n```python\nimport requests\n\nheaders = {'X-Crawler-Token': 'YOUR_CRAWLER_TOKEN'}\nurl = 'https://agentflare.org/crypto/zcash.data.json'\nd = requests.get(url, headers=headers).json()['data']\n\nprint(d['name'], d['symbol'], d['price_usd'])\nprint(d['market_cap_rank'], d['change_pct']['h24'], d['change_pct']['d7'])\nprint(d['ath_usd'], d['ath_date'], d['atl_usd'], d['atl_date'])\nprint(d['supply']['circulating'], d['supply']['max'])\nfor p in d['history_90d'][:3]:\n print(p['date'], p['price'])\n```\n\n## Datasets, key fields and price per request\n\n| File | Key data fields | Price (USD) |\n| --- | --- | --- |\n| /social/index.data.json | data.categories[].id, name, headline, url, stats.posts, likes, views, medLikes, verified | 0.005 |\n| /predictions/index.data.json | data.count, total_volume_usd, events[].slug, leading, probability, change_pp_30d, volume_usd | 0.01 |\n| /predictions/.data.json | data.event, volume_24h_usd, end_date, tags, markets[].question, odds, volume_usd | 0.01 |\n| /crypto/index.data.json | data.total_market_cap_usd, coin_count, advancers_24h, stablecoin_share_pct, top[], trending[] | 0.01 |\n| /crypto/YYYY-MM-DD.data.json | Same layout as the crypto index | 0.01 |\n| /crypto/zcash.data.json | data.price_usd, market_cap_rank, fdv_usd, change_pct, ath_usd, atl_usd, supply, history_90d, faq, newswire | 0.01 |\n\n## Common pitfalls\n\n- Do not send the crawler token in Authorization: Bearer. That header is reserved for the gateway layer; use X-Crawler-Token instead.\n- Older AISA pages still show X-AISA-Crawler-Token. Use X-Crawler-Token, the name in the Open Verify specification.\n- Prices differ by directory: social is 0.005 USD per request, predictions and crypto are 0.01 USD. Budget loops over many event or coin files accordingly.\n- Dated files use a YYYY-MM-DD placeholder in their name, for example atp-fokina-tiafoe-YYYY-MM-DD.data.json. Substitute a real date before requesting.\n\n## Key takeaways\n\n- Only .data.json and .full.md files are paid; index pages, .html articles and .md teasers stay free.\n- Social costs 0.005 USD per request; predictions and crypto cost 0.01 USD each.\n- Authenticate with X-Crawler-Token, then read data.categories, data.events or data.top from the index files.\n\n## FAQ\n\n**How much does an AgentFlare .data.json request cost?**\nPer pricing.json, social is 0.005 USD per request, predictions is 0.01 USD and crypto is 0.01 USD. Billing is per request for files matching *.data.json or *.full.md in each directory.\n\n**Which header carries the crawler token?**\nUse X-Crawler-Token. It replaces X-AISA-Crawler-Token, which older AISA documentation still shows. Do not use Authorization: Bearer for the token, since that header is reserved for the gateway layer.\n\n**What fields does a prediction event file contain?**\nBesides the common envelope, data holds event, slug, volume_usd, volume_24h_usd, end_date, tags and markets. Each market has question, odds and volume_usd. The index adds count, total_volume_usd and events with probability and change_pp_30d.\n\n**Where do I find price history for a coin?**\nA per-coin file such as /crypto/zcash.data.json has data.history_90d, an array of objects with date and price. It also has change_pct for h24, d7, d30 and d90, plus ath_usd, ath_date, atl_usd and atl_date.\n", "sources": [ { "title": "Header name: X-Crawler-Token", "url": "https://esa.aisa.one/cdn/open-verify.html" }, { "title": "AgentFlare Social Pulse .data.json field reference", "url": "https://agentflare.org/social/index.html" }, { "title": "AgentFlare Predictions .data.json field reference", "url": "https://agentflare.org/predictions/index.html" }, { "title": "AgentFlare Crypto .data.json field reference", "url": "https://agentflare.org/crypto/index.html" }, { "title": "AgentFlare pricing.json (directory price map)", "url": "https://agentflare.org/pricing.json" } ], "related": [ { "name": "Reading .data.json: A Field Guide for Agents", "url": "https://agentflare.org/guides/reading-datajson-a-field-guide-for-agents.html" }, { "name": "Getting Started with HTTP 402 Pay-Per-Crawl", "url": "https://agentflare.org/guides/getting-started-with-http-402-pay-per-crawl.html" }, { "name": "Crawler Tokens & Auto-Pay: A How-To", "url": "https://agentflare.org/guides/crawler-tokens-auto-pay-a-how-to.html" }, { "name": "Handling 402 and 403 Responses: An Error Reference for Agents", "url": "https://agentflare.org/guides/handling-402-and-403-responses-an-error-reference-for-agents.html" }, { "name": "Budgeting a Paid Crawl: Discover, Survey, Then Buy", "url": "https://agentflare.org/guides/budgeting-a-paid-crawl-discover-survey-then-buy.html" }, { "name": "Building a Pay-Per-Crawl Client for Your Agent", "url": "https://agentflare.org/guides/building-a-pay-per-crawl-client-for-your-agent.html" } ], "pricing": { "price_usd": 0, "method": "402", "endpoint": "https://esa.aisa.one/api/v1/access/verify", "autopay_hint": "set crawlerAutoPrice=true with the X-Crawler-Token header", "onboarding": "https://esa.aisa.one/agent/guide.html" }, "powered_by": "AISA — agent-native search, settlement & delivery (https://aisa.one)" }