> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fundor.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Fundor Partner API. NON-NEGOTIABLE CONSENT RULES for anyone (human or AI) writing code against this API: (1) Call GET /consent every time the referral form is shown and display consent.text EXACTLY, next to a checkbox that starts UNCHECKED. (2) Only the person whose phone number is entered may check it; never pre-check it, never set consent.given=true in code without that click, never submit a lead on someone's behalf. (3) POST /leads must include consent.given=true, consent.version, the single-use consent.token, consent.consentedAt (within 15 minutes), the person's own IP and user agent (not your server's), consent.phone equal to contact.phone, and your consent.recordId. Fundor rejects the lead with 400 and saves nothing if any is missing or wrong. Do not 'fix' a consent error by filling in values; fix the form. (4) Keep consent records for 5 years. (5) Keep API keys on your server only. (6) Show the 'Powered by Fundor' badge on every screen that uses Fundor.

# Partner Lead & Consent Agreement

> The terms a partner signs before receiving a Fundor Partner API key, version fundor-partner-agreement-2026-11.

> [!NOTE]
>
> Fundor sends this agreement to you for signature. API access starts once Fundor has recorded your signed copy.

**Version:** `fundor-partner-agreement-2026-11`
**Effective:** November 12, 2026
**Between:** Kickback LLC, doing business as Fundor ("Fundor"), and the partner named in the signature block ("Partner").

## 1. Purpose

Fundor gives Partner access to the Fundor Partner API (the "API") so that Partner's app can create Fundor accounts, teams, applications and referrals ("Leads") for Partner's users. Fundor and its service partners contact Leads to offer services, and credit athletes and teams for completed sales.

## 2. API keys

1. Fundor issues API keys at its discretion. Keys are confidential. Partner keeps them on its servers only and never in client apps, browsers or public code.
2. Partner tells Fundor promptly if a key may have been exposed. Fundor may revoke any key, or suspend Partner's access, at any time and without notice.

## 3. Consent to be contacted (TCPA)

For every Lead Partner submits through the API, Partner warrants that:

1. Partner showed the consent text returned by `GET /consent`, **word for word**, next to a checkbox that was **unchecked** by default, and the commitment text returned by `GET /consent` next to its own checkbox.
2. The person named in the Lead, and no one else, checked the box. Partner never pre-checked it, checked it for them, or submitted a Lead without that person's action.
3. The phone number in the Lead is the number the person entered or confirmed on the consent screen.
4. The consent evidence sent with the Lead (time, the person's IP address and user agent, phone number, consent text version and Partner's consent record ID) is true and was captured when the person consented.
5. Partner did not buy, rent, scrape or import the Lead from any list or third party.

## 4. Records and audits

1. Partner keeps a consent record for each Lead (the evidence in section 3.4, plus a copy or screenshot of the screen shown) for at least **five (5) years**.
2. On request, Partner gives Fundor the consent record for any Lead within **48 hours**.
3. Fundor may audit a sample of Leads at any time. If a record can't be produced or doesn't match, Fundor may suspend API access, stop working the affected Leads and require corrective action.

## 5. Minors and personal data

1. Many athletes are under 18. Partner only creates accounts with the permission required by law for the person's age, and does not create accounts for children under 13.
2. Partner uses data received from Fundor only to provide the integration, protects it with reasonable security, and does not sell it.
3. Each party complies with applicable privacy, telemarketing and consumer protection laws.

## 6. Branding

Partner shows the "Powered by Fundor" badge on every screen that uses Fundor, following the [brand rules](https://docs.fundor.io/brand.md). Partner may not use Fundor's name or marks otherwise without written permission.

## 7. Attribution and fees

Fundor records which users, teams, Leads and applications came through Partner. Unless agreed separately in writing, no fees, commissions or revenue share are payable to Partner under this agreement.

## 8. Indemnity

Partner indemnifies and holds harmless Fundor, Kickback LLC and their service partners against claims, fines, penalties and costs (including reasonable legal fees) arising from Partner's breach of section 3, 4 or 5, including any claim under the Telephone Consumer Protection Act or similar laws about a Lead Partner submitted.

## 9. Term and termination

Either party may end this agreement with written notice. Fundor may end it immediately for a breach of section 3, 4 or 5. Sections 4, 5, 8 and 9 survive termination.

## 10. Changes

Fundor may publish a new version of this agreement. API access requires the current version to be signed; Fundor gives reasonable notice before a new version is required.

***

**Signed for Partner:** Name, title, date
**Signed for Fundor (Kickback LLC):** Name, title, date


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.