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.

API Reference

API Reference

Complete reference for the FundLoop API

Last updated September 20, 2026

This section provides a complete reference to the FundLoop API, including all available endpoints, request formats, authentication requirements, and response schemas. These APIs enable projects to automate user syncing, revenue reporting, and validation queries.

Base URL

All API requests are served over HTTPS.

Base URL: https://api.fundloop.org/v1

Authentication

Each project must authenticate using a unique API key. This key can be generated from the project dashboard.

Include the key in the Authorization header of all requests:

```

Authorization: Bearer YOUR\_API\_KEY

````

Endpoints

`POST /project-users`

Submit or update your monthly list of active users.

#### Request Body

```json

{

"users": [

{

"id": "user-abc123",

"score": 1,

"comment": "Submitted several bug reports"

},

{

"id": "user-xyz456",

"score": 0.5,

"comment": "Joined two community calls"

}

]

}

````

* id: The user’s unique identifier (Cubid user ID or other authorized ID)

* score: Participation fraction between 0 and 1

* comment: Optional, for internal tracking

---

`POST /contributions`

Report your monthly revenue and calculate your contribution to the FundLoop pool.

#### Request Body

```json

{

"month": "2025-07",

"revenue_usd": 12800,

"contribution_usd": 128

}

```

* month: ISO date string representing the reporting period

* revenue_usd: Gross revenue for that month in USD

* contribution_usd: Your 1% pledge (or equivalent value)

---

`GET /user-validation/{user_id}`

Fetch Cubid validation status for a specific user.

#### Response Format

```json

{

"user_id": "user-abc123",

"tier": 2,

"valid": true,

"last_verified": "2025-06-28T13:32:00Z"

}

```

* tier: Validation tier (0 = unverified, 1 = basic, 2+ = fully validated)

* valid: Boolean flag indicating active validation

* last_verified: Timestamp of the most recent verification

---

Rate Limiting

Standard rate limits apply:

* 100 requests per minute

* Contact support for elevated access

Error Codes

* 401 Unauthorized: Invalid or missing API key

* 422 Unprocessable Entity: Validation error in submitted data

* 500 Internal Server Error: Unexpected error, try again later

Support

For questions, contact dev@fundloop.org or join the #api-support channel in Discord. For SDK integration, see the [SDK Documentation](/docs/sdk-documentation).

```