---
name: agentic-payment-signal-radar
description: Build an Agentic Payment radar brief from Stablehunter curated signals and v1-lite research snapshots.
---

# Agentic Payment Signal Radar

Use this skill when a user asks for a short Agentic Payment radar brief, builder workflow signal, source-backed market pulse, or product/GTM signal scan for agentic payment infrastructure.

Stablehunter positioning:

```text
Signal intelligence API and agent workflow for Agentic Payment builders.
```

## Source Boundary

Only use existing Stablehunter signal surfaces:

```text
GET https://cms.stablehunter.com/api/public/source-intelligence/signals?topic=payment_api
GET https://cms.stablehunter.com/api/public/source-intelligence/research-snapshots?topic=payment_api
GET https://cms.stablehunter.com/api/daily-digests/{digestDate}?category=information_signal&locale={locale}
```

Allowed topics:

```text
payment_api
agentic_payment
x402
stablecoin_payment
agent_commerce
wallet_infra
payment_compliance
```

Do not add crawling, scraping, browser automation, social search, newsletter scraping, search-engine queries, or external data collection inside this skill. If the configured Stablehunter endpoint does not return data, report the access state and stop.

## Access Behavior

- If v1-lite endpoints return HTTP 200, use their curated signal or research snapshot payload.
- If v1-lite endpoints return HTTP 402, state that the Source Intelligence API requires a token or payment credential.
- For public demos only, the skill may read the existing Daily Signal endpoint as a curated fallback.
- Never present a 402 response as a product failure; treat it as access-gated paid API behavior.

## Input Parameters

```json
{
  "topic": "payment_api",
  "locale": "en",
  "max_items": 5,
  "builder_context": "payment API, wallet, stablecoin, compliance, merchant, or agent commerce workflow"
}
```

Locale values:

```text
en | zh-Hans
```

## Radar Output Schema

Return a compact radar brief:

```json
{
  "radar_name": "Agentic Payment Radar",
  "topic": "payment_api",
  "source_surface": "curated_signals | v1_lite_research_snapshot | daily_signal_fallback",
  "access_state": "available | access_gated | unavailable",
  "digest_date": "YYYY-MM-DD",
  "items": [
    {
      "title": "string",
      "signal": "string",
      "why_it_matters": "string",
      "builder_action": "string",
      "affected_builder": "string",
      "source_url": "https://example.com",
      "confidence": "high | medium | low"
    }
  ],
  "caveats": ["string"],
  "canonical_url": "https://stablehunter.ai/agentic-payment-radar.html"
}
```

## Workflow

1. Choose the topic from the user's builder context. Default to `payment_api`.
2. Call the curated signals endpoint for that topic.
3. Call the v1-lite research snapshot endpoint for the same topic when a snapshot-level brief is requested.
4. If both v1-lite endpoints are access-gated, state HTTP 402 and use Daily Signal fallback only for demos or public examples.
5. Normalize the result into the radar output schema.
6. Keep the brief action-oriented: what changed, why it matters, who should care, and what the builder should inspect next.
7. Preserve source links and Stablehunter canonical links.

## Brief Format

```text
Agentic Payment Radar · {topic}
Access: {access_state}
Source: {source_surface}

1. {title}
Signal: {signal}
Why it matters: {why_it_matters}
Builder action: {builder_action}
Source: {source_url}

Caveats:
- {caveat}
```

## Exclusions

Do not provide trading advice, token price calls, investment recommendations, airdrop speculation, unsupported compliance claims, or generic crypto market news. Keep the scope on Agentic Payment builders and the infrastructure around agent-executable payment workflows.