Documentation

One public hub for product context, integrations, and support articles.

FundLoop documentation should explain the product honestly: what exists today, what the network is growing toward, and where to look next when you need workflow-level detail.

Support articles

Use the article list to browse current help content. As the support library grows, this hub remains the public entry point instead of splitting product guidance across separate mini-sites.

About FundLoop

FundLoop is building operating logic for a network economy that shares value back out.

The public docs should do more than answer support questions. They should also explain the economic model, why monthly structure matters, and how public discovery, founder operations, and identity-aware workflows fit together.

Mutual prosperity, made operational

FundLoop exists to help projects, participants, and operators move beyond vague community language and into repeatable operational flows.

Product before mythology

The public story should map back to real routes in the app today: discovery, onboarding, project contribution operations, reconciliation, and emerging reporting.

Using FundLoop

The current product has three practical entry paths.

Participants discover projects and build signal, founders manage contribution operations and route setup, and operators verify the payment and reporting pipeline that supports the monthly cycle.

Participation path

Start on the public participation funnel, continue into onboarding, and then move toward workspace-level results visibility over time.

Founder path

Use the founder funnel to understand the commitment model, then move into onboarding and project-side contribution operations.

Support path

Use documentation and FAQ first, then contact support when the issue depends on a real account, route, or payment workflow.

Protocol and integrations

FundLoop is documenting a future-facing integration surface without pretending it is finished today.

The longer-term target includes public protocol docs, MCP-friendly workflows, and agent/operator integrations. Right now, the truthful public guidance is to use the documentation hub as the source of product and workflow context while the formal external surface matures.

Product-aware integrations

The most useful external touchpoints will reflect real FundLoop domains such as identity, contribution cycles, payments, reporting, and observability rather than a generic CRUD API pitch.

Agent and MCP direction

The target architecture expects an MCP-accessible layer for founders, project members, and operators, but that work is still ahead of the current public docs surface.

For Projects

Project Onboarding

Guide for projects joining the FundLoop ecosystem

Last updated September 20, 2026

This guide explains how to onboard your project into the FundLoop ecosystem. By committing to the 1% pledge, you gain access to a growing network of verified users, shared services, and a regenerative funding loop that rewards participation and impact.

Step 1: Create Your Project Profile

Start by submitting basic details about your project:

  • Project name and logo
  • Website or landing page URL
  • Short description and mission statement
  • Primary contact person or account

Once submitted, your project profile will be reviewed and added to the public FundLoop directory.

Step 2: Commit to the 1% Pledge

By joining FundLoop, your project agrees to contribute 1% of monthly revenue (or equivalent value from grants or token inflows) into the shared FundLoop pool. This pool funds:

  • Citizen salaries for active, verified users
  • Public goods
  • Shared services across the ecosystem

This pledge is flexible in structure but must be recorded transparently each month.

Step 3: Nominate Active Users

You can assign a share of your monthly contribution to specific users who actively contribute to your project. For each user, you may:

  • Nominate them for a payout
  • Assign a fractional value (0 to 1) reflecting their engagement level

Only users who meet a minimum verification standard via Cubid are eligible to receive funds.

Step 4: Stay Consistent

Consistency is key to building trust and retaining engaged users. Projects are encouraged to:

  • Make regular monthly contributions
  • Maintain a visible pattern of user support
  • Avoid large gaps between activity spikes (e.g. funding drives) and dry months

A reliable flow of value helps ensure long-term user loyalty.

Step 5: Collaborate with the Ecosystem

Projects benefit most when they:

  • Recommend other FundLoop apps to their users
  • Join multi-project referral loops
  • Help users complete identity validation
  • Participate in governance and feedback loops

By contributing consistently and encouraging cross-project usage, you strengthen both your community and the wider ecosystem.

Next Steps

Once you’ve completed onboarding, we recommend exploring the [Integration Guide](/docs/integration-guide) to automate your reporting and user syncing, and the [Governance Documentation](/docs/governance) to participate in decision-making about thresholds, weights, and future rules.