!

Legal Disclaimer

PipeAgent is a data distribution gateway. We do not own, verify, or endorse the data provided by third-party creators. Use at your own discretion.

Docs/consumer / request board

Request Board (Consumer)

The Request Board is the public list of data requests from the community. You will find it in the app under Request Board (/feed-requests). It answers: *“What structured feeds do people wish existed?”*

What you can do

  • Browse open requests, sorted by Hot (vote-weighted) or Latest.
  • Vote on requests you care about. Votes are a signal of demand; they help providers and the community see which datasets matter most.
  • Open a request to read the full description and vote from the detail page.
  • Submit a new request from New Data Request (/feed-request) while signed in. Your published requests appear under Dashboard → My Activities → My Requests.
  • Indicate an Intended Bounty when submitting a request. This is the amount you are willing to pay (in USD) to use the data feed once it’s built.

    • Intended Bounty

    When you submit a request, you can optionally include an Intended Bounty. This is a powerful signal:

  • It tells providers exactly what the market value of the data is to you.
  • It helps attract high-quality providers who can prioritize your request based on potential revenue.
  • High-bounty requests are prominently featured to ensure they get the visibility they deserve.

    • What the Request Board is not

  • It is not a support ticket or a guaranteed roadmap. Posting or voting does not obligate PipeAgent or any provider to build a feed.
  • It is not a binding contract. The bounty you indicate is an intent price, not a guaranteed payment. Actual payment only happens if and when you subscribe to a feed that meets your needs.
  • It does not replace the Feeds catalog. Published, pipe-ready feeds are listed there; the Request Board is for ideas and demand before (or instead of) a live feed.

    • Tips

  • Write a clear title and concrete description (sources, fields, update cadence, or example use case) so providers can estimate effort.
  • If your need targets a specific creator, use a provider-targeted flow when the product offers it (e.g. from a provider profile), so the right audience sees it.

    • For providers

    If you build or curate data, see Request Board (Provider) for how to use the same board from a supply-side perspective.

    Version 1.0.4 - Premium Infrastructure