Recovery-gated beta

AgentWatch API

AgentWatch is an API for AI-agent activity signals across GitHub pushes, social mentions, and more. One real x402 paid production proof already exists, but broader onboarding resumes only after the current redeploy + verification pass, and the next wave stays intentionally small.

View current API surface View on GitHub

Current API Surface

Reference public route

curl https://agentwatch.axiomlabs.systems/agent-watch/yesterday

Paid-boundary check (x402)

curl --silent -i "https://agentwatch.axiomlabs.systems/agent-watch/today"

What You Get

🐙

GitHub Signals

Get notified when new AI-agent repositories are created, when code is pushed, or when discussions happen in issues and PRs. Each signal includes repo name, description, star count, commit activity, and relevant keywords.

{"source": "github", "type": "repo_created", "agent": "devon-agent", "repo": "creatoronsocial/devon", "stars": 142, "keywords": ["agent", "autonomous"]}

𝕏

Twitter / X Mentions

Capture every mention of your agent with full context: who posted it, engagement metrics (likes, retweets), sentiment analysis, and the actual tweet text. Find early adopters and track sentiment.

{"source": "twitter", "type": "mention", "agent": "openclaw", "author": "@builder_dev", "text": "Just shipped with @openclaw!", "likes": 47, "sentiment": "positive"}

📰

Hacker News Discussions

Track when AI-agent projects hit Hacker News frontpage. Each signal includes post title, URL, score, comment count, and keywords. Spot trending projects and time your launch.

{"source": "hackernews", "type": "post", "agent": "ai-agent", "title": "Show HN: Autonomous agent", "points": 234, "comments": 67}

What You Can Do

📊

Agent Monitoring

Track mentions, activity, and growth of your own AI agent projects across all platforms in one dashboard.

Example: "Show me all mentions of 'devon-agent' this week"

🔍

Competitive Intelligence

Discover new agent projects, track competitor activity, and identify emerging patterns in the agent ecosystem.

Example: "What new agent repos were created this month?"

🎯

Lead Generation

Find builders creating AI agents → reach out with tools, services, or partnerships.

Example: "Show me builders who shipped agents in the last 7 days"

📈

Trend Detection

Spot emerging agent patterns, popular frameworks, and shifting community interest in real-time.

Example: "Which agent frameworks are trending this month?"

Wallet Setup for AI Agents

AgentWatch accepts USDC on Base Mainnet via x402. For AI agents, we recommend the CDP Server Wallet for automated, non-custodial payments.

Option 1: CDP Server Wallet (Recommended for Agents)

1
Install CDP SDK
```
npm install @coinbase/coinbase-sdk
```

Create Server Wallet

import { Wallet } from '@coinbase/coinbase-sdk';

const wallet = await Wallet.create({
  networkId: 'base-mainnet'
});

3
Fund with USDC
Bridge USDC to Base via Coinbase Bridge or Bungee.
Revenue wallet: 0x45A5...6D46

Make x402 Payment

const payment = await wallet.createTransfer({
  amount: "0.01",
  tokenId: "usdc",
  destination: "0x45A5254593a1a327B5644b498D22228b40EC6D46"
});

Option 2: Standard Wallet (MetaMask, Coinbase Wallet)

Add Base Mainnet to Wallet

Network: Base Mainnet
Chain ID: 8453
RPC: https://mainnet.base.org
Currency: ETH

Add USDC Token

Contract: 0x833589fCD6eDb6E08f4c7C32D4f71d54bdA488d6
Symbol: USDC
Decimals: 6

3
Get USDC on Base
- Buy on Coinbase, send to Base
- Bridge from Ethereum via official bridge
- Use DEX aggregator (Bungee, Li.Fi)
4
Pay via x402
When you hit a paid endpoint, the 402 response includes payment requirements. Sign and submit to unlock access.

Tip: For the paid production proof path, use CDP Server Wallet for x402 payments once onboarding resumes. For one-off verification, use x402 with any Base-compatible wallet.

Current API Surface

GET/agent-watch/yesterdayPublic route

Reference public route for yesterday's aggregated signals. Treat current availability as recovery-gated until the redeploy + verification pass is clear.

GET/agent-watch/todayx402 paid

Paid-route surface for today's signals. Expect the 402 boundary first, then retry with x-payment-token after the recovery gate clears.

GET/agent-watch/archivex402 paid

Historical paid-route surface. It stays on the x402 paid flow, and broader onboarding to this path resumes only after the current recovery gate is clear.

GET/healthPublic

Readiness route used to verify the current recovery gate.

Want the next AgentWatch wave?

One real x402 paid production proof exists. Broader onboarding resumes after the current redeploy and verification pass.

Open current API surface View Pricing