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

Integration Guide

Technical documentation for integrating with FundLoop

Last updated September 20, 2026

Integrating your project with FundLoop allows you to automate key processes such as user syncing, contribution tracking, and validation status updates. This guide outlines how to use FundLoop’s API and optional SDKs to streamline your participation in the ecosystem.

API Authentication

All requests to the FundLoop API require authentication using a project-specific API key. You can generate this key from your FundLoop project dashboard under Settings → API Access.

Include the key as a Bearer token in the Authorization header for all requests.

User Syncing

To ensure accurate attribution, projects should regularly sync a list of active users. Each record should include:

  • A unique user identifier (such as an email, wallet address, or Cubid user ID)
  • A participation score (0 to 1) reflecting the user's engagement
  • An optional comment or reason for the score

Endpoint: `POST /api/v1/project-users`

Example payload:

```json

{

"users": [

{

"id": "user-abc123",

"score": 1,

"comment": "Submitted 3 PRs this month"

},

{

"id": "user-xyz456",

"score": 0.4,

"comment": "Participated in one community call"

}

]

}