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

SDK Documentation

Documentation for the FundLoop SDK

Last updated September 20, 2026

The FundLoop SDK provides an easy-to-use interface for integrating your project with the FundLoop API. It includes client libraries in multiple languages to simplify tasks like user syncing, revenue reporting, and validation checks.

Available SDKs

FundLoop provides official SDKs in:

  • **TypeScript / Node.js**
  • **Python** *(in beta)*
  • More language support coming soon

Each SDK is versioned and available on GitHub and major package managers (e.g., npm, PyPI).

Installation

TypeScript / Node.js

```bash

npm install @fundloop/sdk

````

Python (Beta)

```bash

pip install fundloop-sdk

```

Basic Usage

Initialization

```ts

import { FundLoopClient } from '@fundloop/sdk'

const client = new FundLoopClient({

apiKey: process.env.FUNDLOOP_API_KEY

})

```

Submit Users

```ts

await client.submitUsers([

{ id: 'user-abc123', score: 1, comment: 'Top contributor' },

{ id: 'user-xyz456', score: 0.3 }

])

```

Report Revenue

```ts

await client.reportContribution({

month: '2025-07',

revenue_usd: 18000,

contribution_usd: 180

})

```

Check Validation

```ts

const validation = await client.getValidation('user-abc123')

console.log(validation.tier, validation.valid)

```

Error Handling

All methods return Promise objects and throw exceptions for:

* Invalid input formats

* Missing credentials

* API errors or rate limits

You can use try/catch or client.onError() hooks to handle failures gracefully.

Best Practices

* Use environment variables to manage your API key

* Schedule monthly syncs using cron or task queues

* Cache validation responses to reduce API calls

* Combine SDK calls with your internal user tracking systems

Resources

* [GitHub Repository](https://github.com/fundloop/sdk)

* [API Reference](/docs/api-reference)

* [Project Onboarding Guide](/docs/project-onboarding)

Support

Need help? Join our developer Discord channel or email us at dev@fundloop.org.

```