Agent Access

Sell structured airdrop intelligence, not just articles.

Airdropedia is moving toward a model where public pages remain free for humans, while faster, cleaner, machine-readable research becomes the product for AI agents and automation stacks.

See agent preview Hot feed Diff feed Real Yield API Intelligence UI Access spec Gateway catalog

Free Preview

$0

Human-readable pages and public JSON snapshots.

  • Public dossier JSON for selected projects
  • Human project pages and simulators
  • Best for discovery and lightweight testing

Agent Feed

TBD

Higher-frequency structured updates for automations.

  • More frequent dossier refreshes
  • Hot-project and watchlist endpoints
  • Watchlist diff with change reasons and freshness
  • Designed for bots, scripts, and internal tools

MCP / Custom

Custom

Direct integration for teams building AI workflows.

  • MCP-style access and tailored feeds
  • Custom project coverage and schema alignment
  • Early partner support while the product is forming

The thesis in one sentence

Human-facing content stays free, but the maintained machine-readable update layer becomes the product: real-yield rankings, cleaner JSON, clearer diffs, and x402-gated access for AI agents.

Who this is for

The product is not "AI content." It is structured airdrop intelligence for people and teams already building with agents, automations, and internal research workflows.

Solo Agent Builder

A founder or hacker wiring airdrop research into bots, dashboards, or private scripts.

Wants clean JSON, quick updates, and fewer manual checks.

Research Desk

A small crypto research team tracking multiple campaigns at once.

Needs watchlists, diffs, and evidence-backed reasons to re-rank projects.

Automation Partner

A workflow builder who wants MCP or custom schema alignment.

Needs stable endpoints, predictable fields, and direct support.

Why this beats scraping the site yourself

The business is not "please scrape our blog better." The business is selling the maintained intelligence layer that removes repeated parsing, ranking, and change detection work from the buyer.

Alternative What breaks Why the product matters
Scrape the public site yourself You have to re-parse pages, detect change manually, and maintain your own freshness logic. Airdropedia sells the change layer directly: what moved, why it matters, and what to re-check now.
Read article summaries only Good for humans, weak for bots. Articles are poor inputs for routing, ranking, or automation. Structured JSON gives agents clear fields, timestamps, action bias, scores, and reasons.
Build everything from scratch You still need coverage, normalization, scoring, history, and a stable schema before an agent can rely on it. Airdropedia can become the maintained intelligence layer instead of another scraping target.

Free vs paid boundary

This is the core business rule: human reading stays free, while higher-frequency machine-readable updates become the product.

Surface Free Paid direction
Human project pages Full access Not the product
Public dossier JSON Available for discovery Serves as preview layer
Hot / watchlist feeds Basic snapshot form Higher refresh and stronger filtering
Diff feed Preview endpoint Faster updates, cleaner reasons, more projects
MCP / custom integration Not included Primary custom offer

How the product matures

The rollout is intentionally staged. First we prove the shape, then we prove the paid update layer, then we deepen into agent-native infrastructure.

Layer 1

Free preview

Public pages and public dossier JSON explain the schema, the projects, and the product philosophy.

Layer 2

Paid update layer

High-value feeds like real-yield intelligence, hot rankings, watchlist snapshots, and especially watchlist diffs become x402 candidates.

Layer 3

Agent-native integration

MCP and custom access become the deeper product for teams that want structured ingestion inside their own agent stack.

x402 direction

The goal is not to charge humans for reading pages. The goal is to charge machine clients for higher-value structured endpoints once the free preview is clear enough and useful enough.

Free preview stays open

Human pages, the dossier index, and selected project JSON remain public so agents can discover the schema and humans can understand the product.

Paid candidates get the paywall

The best x402 candidates are diff-heavy or higher-refresh surfaces like real-yield intelligence, hot feed, watchlist, farming radar, and especially watchlist diff.

Custom stays separate

MCP and partner-specific integrations are not just another endpoint. They are a separate custom access layer for teams with real workflow needs.

First x402 candidates

  • /api/intelligence/real-yield.json
  • /api/dossiers/watchlist-diff.json
  • /api/dossiers/watchlist.json
  • /api/dossiers/hot.json
  • /api/farming-radar.json

Machine-readable access map

This is the current catalog of surfaces, their role, and which payment model they are moving toward.

The public site exposes the schema preview. The gateway catalog exposes the payment-facing offer sheet for agents.

Surface Route Tier Payment model
Dossier Index
Compact index of supported projects and their public dossier endpoints.
 /api/dossiers/index.json free-preview public
Project Dossier
Public dossier snapshot for Based, Hibachi, and Extended.
 /api/dossiers/{id}.json free-preview public
Hot Feed
Ranked project feed intended to become a faster-refresh paid surface.
 /api/dossiers/hot.json paid-candidate x402-future
Watchlist Snapshot
Snapshot view of current action bias and freshness for tracked projects.
 /api/dossiers/watchlist.json paid-candidate x402-future
Watchlist Diff
Change-oriented feed with reasons, affected scores, and last-changed timestamps.
 /api/dossiers/watchlist-diff.json paid-candidate x402-future
Farming Radar
Action shortlist that turns the project universe into next farming steps.
 /api/farming-radar.json paid-candidate x402-future
Intelligence Health
Freshness, generated-at, and readiness status for the intelligence snapshots and daily brief.
 /api/intelligence/health.json free-preview public
Daily Intelligence Brief
Daily farming shortlist, Based/Hibachi/Extended monitor, agent entrypoints, and distribution drafts.
 /api/intelligence/daily-brief.json paid-candidate x402-future
Opportunity Discovery
Coverage-gap scanner for untracked airdrop, wallet, L1 ecosystem, and distribution opportunities.
 /api/intelligence/opportunity-discovery.json paid-candidate x402-future
Real Yield Snapshot
Protocol revenue, fee, delta, and airdrop-adjacent opportunity snapshot for Airdropedia Intelligence.
 /api/intelligence/real-yield.json paid-candidate x402-future
MCP / Custom Access
Future direct integration path for custom schemas and partner workflows.
 /agent-access#mcp-custom custom mcp-contract

What the feed actually looks like

The point is not vague AI text. The point is a compact object an agent can route, rank, and act on without scraping the whole site again.

Sample diff object

{
  "id": "hibachi",
  "changeType": "signal-spike",
  "priority": "medium",
  "lastChangedAt": "2026-04-22T16:22:31.219Z",
  "changeReason": "Week 26 points update pushed new activity signals.",
  "actionBias": "speculative",
  "affectedScores": ["momentum", "airdropPotential"],
  "urls": {
    "humanPage": "/projects/hibachi",
    "api": "/api/dossiers/hibachi.json"
  }
}

Immediate use cases

  • Agent watchlist refresh A private bot checks the diff feed every few hours and only re-runs analysis when a project actually changed.
  • Research triage A small desk uses hot and diff feeds to decide which projects deserve human review first.
  • Custom MCP workflow A partner plugs dossier and diff data into their own agent stack and schema.

What closes the first sale?

Not investor decks. A single user or team saying "this feed saves us time" is enough. The immediate goal is to make the offer concrete enough that someone can understand what they would buy today.

What becomes paid first?

The likeliest first paid surface is the update layer: hot rankings, watchlists, and diff-style feeds that explain what changed and which projects an agent should re-check now.

Roadmap

We are deliberately moving in stages so the product does not become vague. Each step makes the offer easier to understand and easier to charge for.

Stage 1

Public preview

Human pages, dossier JSON, hot feed, watchlist, and diff feed stay open so people can understand the product.

Stage 2

Paid update layer

Higher-frequency refreshes, better change reasons, and more reliable freshness become the first paid surface.

Stage 3

Agent-native access

MCP, custom schemas, and partner workflows turn Airdropedia into infrastructure instead of a content site.

Current ask

The near-term goal is simple: find one person or team who says the agent feed would save them time. That is enough signal to keep building the paid layer.

1

Review the public preview and diff feed.

2

DM Tokyo Crypto 研究所 on X with what you want to build.

3

If the fit is good, we shape the first paid feed around that workflow.

Review diff feed Review public preview DM on X