Why List on the Marketplace?
Zero payment infrastructure
FlareHQ handles the HTTP 402 challenge, Circle Nanopayment verification, and on-chain settlement. You ship an API endpoint — FlareHQ monetizes it.
Agent discoverability
Autonomous AI agents scan the Marketplace by category to find tools they need. A well-tagged listing surfaces your API to agents that would never find it through traditional API directories.
Upstream URL privacy
Your
targetUrl is stored server-side and never returned to consumers. API callers see only the FlareHQ proxy endpoint, not your internal infrastructure.Live price control
You can update pricing or toggle a listing between
active, paused, and archived at any time via the SDK or REST API — no redeployments needed.Listing Schema
Every Marketplace listing is described by the following fields:string
required
URL-safe identifier for your listing used in all SDK and REST calls (e.g.,
solana-whale-tracker). Must be globally unique across the Marketplace.string
required
Human-readable API title shown in the Marketplace directory.
string
required
Detailed explanation of what your endpoint does and what data it returns. Agents use this field for semantic discovery.
array of strings
required
Tags that classify your API (e.g.,
["DeFi", "Analytics"]). Supported values include AI, Market Data, DeFi, Analytics, Infrastructure, and Identity.string
required
The per-call price denominated in USDC (e.g.,
"0.005"). Sub-cent values are supported.string
required
Your private upstream API URL. FlareHQ proxies verified, paid requests to this address. Never exposed to consumers.
string
Link to your external API documentation. Shown to developers in the Marketplace listing page.
string
required
Listing state:
active (accepts requests), paused (returns 503 to consumers), or archived (hidden from directory).Merchant Integration Guide
1
Publish a listing
Register your API on the Marketplace by supplying the listing fields above. On success, you receive a listing ID and confirmed slug.
2
Update pricing or toggle status
Adjust your per-request price or flip the listing between Valid
active and paused at any time. Changes take effect immediately for incoming requests.status values:3
Consumers execute requests through FlareHQ
Developers and agents call your listing through FlareHQ’s proxy executor. Payment verification and forwarding to your
targetUrl happen automatically.Your
targetUrl is never included in the response to the consumer. FlareHQ proxies the request server-side and returns only the upstream data payload.4
Track revenue analytics
Pull per-listing statistics including total request count, USDC earned, and the number of distinct agents that have called your endpoint.

