Skip to main content

​
Become a ShadowFeed Provider

ShadowFeed is a marketplace where AI agents buy real-time data using x402 micropayments on Stacks (Bitcoin L2). As an external provider, you publish a feed — agents pay STX per query — and you keep 97% of every transaction.

​
Why integrate

97% revenue share

3% platform fee. Withdraw any time, min 1 STX. No subscription billing or API key management.

No payment plumbing

ShadowFeed handles x402 settlement. You just expose an HTTPS endpoint that returns JSON.

Agent-native customers

Agents have wallets and pay autonomously. No manual signup, no rate-limit haggling.

Bitcoin-secured

Every paid query is a Stacks transaction, settled to Bitcoin. Verifiable on Hiro Explorer.

​
Two integration modes

Pick one based on what you already have.

Partner Bridge (HMAC)

You already have an HTTPS API — including one already gated by x402 on Solana, Base, or another EVM chain. Add ~50 lines of HMAC verifier middleware (or drop in @shadowfeed/provider-sdk). ShadowFeed signs requests with a shared secret; your endpoint serves data and bypasses your existing paywall for those calls. Your direct buyers are unaffected.

Hosted Mirror

You have data but no API server. Give ShadowFeed an R2/S3 URL, GitHub raw link, or webhook push target. We poll, cache, and serve.

​
How Partner Bridge works

Agent ──pay STX──▶ ShadowFeed ──HMAC-signed request──▶ Your API
                       │                                    │
                       │◀──── JSON response ────────────────┘
                       ▼
                Agent receives data
                97% credited to your provider wallet
ShadowFeed never pays your endpoint — it authenticates with an HMAC signature, so if your API is already behind an x402 paywall, your verifier bypasses the charge for ShadowFeed’s calls while your direct Solana/EVM buyers keep paying normally. Get the canonical PATH right (it must equal your registered source_path) and run the free handshake test before going live — both covered in the HMAC Integration Guide.
Partner Bridge providers should also publish a .well-known/shadowfeed-feeds.json on their own domain so anyone — marketplaces, partners, grant reviewers — can independently verify you opted in. The SDK does this automatically; manual integrators add it in Onboarding → Step 9.

​
How Hosted Mirror works

Your data source                ShadowFeed
  (R2 bucket /                       │
   GitHub raw /          poll every  │
   webhook push)  ◀─── X minutes ───▶ KV cache ──▶ Agent

​
Revenue model

ItemValue
Per-query grossSet by you (suggested 0.003 - 0.05 STX)
Platform fee3% (300 basis points)
Your share97%
Minimum withdrawal1 STX
Max withdrawal per request1000 STX
Settlement currencySTX on Stacks mainnet (Bitcoin L2)
Revenue accrues as a counter in your dashboard. You sign a withdrawal request via your linked Stacks wallet to move funds on-chain.

​
What you get on signup

1

Custodial Stacks wallet

Auto-generated on signup, AES-GCM encrypted at rest. Acts as your provider identity.
2

HMAC secret

Partner Bridge mode only. Shown once during onboarding — we store only a hash.
3

Public profile

Live at https://shadowfeed.app/#/providers/your-handle.
4

Paid endpoint

Agents immediately call https://api.shadowfeed.app/feeds/p/your-handle/feed-slug.

​
Prerequisites

  • A Stacks wallet (Leather or Xverse) — for signing in and receiving withdrawals
  • For Partner Bridge: an HTTPS API endpoint you control
  • For Hosted Mirror: a public URL with JSON data, or willingness to POST to a webhook

Onboarding walkthrough

Step-by-step signup from wallet connect to first paid query.

HMAC integration

Verifier middleware code in TypeScript, Python, and Go.

Withdrawals & revenue

Link a wallet, withdraw STX, view settlement history.

Troubleshooting

Common errors and how to fix them fast.