Fundz API and Data Licensing

A complete guide for SaaS founders, capital markets platforms, and outreach platforms embedding Fundz signal data into their own products. Commercial license tiers, integration patterns, attribution requirements, and the path from build-phase to revenue-stage OEM.

The job to be done

Some companies don't want a dashboard — they want a data feed. SaaS products that need real-time funding intelligence as a core input. Capital markets platforms that pipe deal-event signals into their own deal-flow systems. Outreach and SDR-as-a-service platforms that trigger sales workflows on company life-events. For these customers, Fundz is best consumed as an API, embedded into their own product or workflow.

The job: provide reliable, real-time signal data with clean attribution, fair commercial terms, and integration patterns that scale from build-phase prototype to revenue-stage OEM partnership.

Who this guide is for

• SaaS founders and data products — building products that need real-time funding, hiring, or M&A data as a core input. They buy the data feed, not the dashboard. Examples: WhoWorksThere, saasyDB, SalesRobot.
• Capital markets and deal platforms — investment platforms, capital markets firms, and deal-sourcing tools piping Fundz signals into their own deal-flow systems. Example: Issuance ($300M+ capital markets platform).
• Outreach and SDR platforms — sales engagement and SDR-as-a-service companies needing trigger data (funding events, exec changes) to power their workflows.

Commercial license tiers

Fundz personal-use API access (Strategic plan, $149/mo) covers individual use of the dashboard and API. It does not authorize commercial redistribution, embedding into products sold to third parties, or white-label use. Commercial use requires a separate addendum.

Build-Phase License (pre-revenue)

For founders building a product that will incorporate Fundz data but don't yet have a paying end customer. Designed to bridge from idea-validation to first sale without paying full OEM rates prematurely.

• Fee: $250/mo, 6-month term
• Scope: Embed Fundz data inside your product UI for use by your authorized end users; pre-launch demos to prospective customers; internal product development and validation
• Restrictions: No resale of raw Fundz data outside your product; no bulk export; no AI model training; no competitive use against Fundz's own offerings
• Attribution: "Powered by Fundz" or substantively equivalent attribution required in your product UI
• Auto-conversion to Commercial OEM Tier on the earliest of: first paying end customer, 6 months elapsed, or any out-of-scope use

Commercial OEM Tier (revenue-stage)

For products with paying customers or shipped commercial integrations. Two pricing models — pick whichever maps cleanly to your product's pricing structure.

Option A — Per-seat

• $1,000–1,500/mo base fee (depending on multi-tenant scale)
• $39 per end-user seat per month
• 1-year term, auto-renewing
• Volume tiers: 50+ seats $29/seat, 100+ seats $25/seat

Option B — Revenue share

• $750–1,000/mo base fee minimum
• 20% of revenue attributable to features in your product that materially incorporate Fundz data
• Quarterly reporting + audit rights (Fundz may audit no more than once per 12-month period, at Fundz's expense, with 30 days' notice)

White-label and multi-tenant

For products that white-label Fundz data into a multi-tenant offering sold to every end customer (rather than a one-off integration), the base fee tier shifts to $1,500/mo + per-seat or $1,000/mo + revshare. The uplift reflects the multi-tenant scale of the integration.

Standard restrictions across all tiers

• No resale, sublicensing, or redistribution of raw Fundz data outside your product
• No bulk export, scraping, or data-warehouse-level extraction
• No use of Fundz data to train or fine-tune AI models
• No use that competes directly with Fundz's own commercial offerings
• Attribution required: "Powered by Fundz" in the embedding product UI

API endpoints (overview)

Full API reference at /knowledge/api-references. The available endpoints (all GET, REST-style):

• /api/v1/fundings — funding rounds (Series A–Z, seed, growth equity)
• /api/v1/executives — executive hires and departures
• /api/v1/acquisitions — M&A transactions
• /api/v1/agreements — contracts, partnerships, government agreements
• /api/v1/products — product launches
• /api/v1/crowdfundings — equity crowdfunding (Reg CF, Reg A)
• /api/v1/models — data model documentation

All endpoints support filtering by date, location, industry, and stage (where applicable), plus pagination via standard offset/limit parameters. Authentication is via API key (Bearer token).

Integration patterns

Pattern 1: Polling with delta sync

Most common for SaaS products. Poll the relevant endpoints (e.g., /fundings) on a schedule (every 15–60 minutes), filter by created_at > last_sync_timestamp, and write deltas into your local database. Maintains a fresh local cache and respects rate limits.

Pattern 2: User-triggered lookup

For products where end users search a specific company or filter on demand (e.g., "show me companies that just raised in [vertical]"), proxy the user's query through your backend to the Fundz API. Cache responses per query for 15–60 minutes to manage rate limits and reduce latency.

Pattern 3: Bulk historical + real-time delta

For products needing the full event history (capital markets platforms running historical analysis), seed your local database with a one-time historical pull (coordinated with Fundz support to avoid rate-limit issues), then poll for deltas going forward.

Pattern 4: Webhook (future)

Webhook delivery is on the roadmap but not yet generally available. Enterprise OEM partners can request priority access. Email john@fundz.net if real-time webhook delivery is mission-critical for your integration.

Data freshness and reliability

• Funding rounds: indexed within hours of public announcement; daily reconciliation against Form D filings for verified amounts.
• Executive hires: typically same-day to 24-hour latency from public announcement (LinkedIn updates, press releases, 8-K disclosures).
• Acquisitions: indexed within 24 hours of announcement; deal value updated as disclosure improves.
• SEC filings: indexed within minutes of EDGAR availability for 8-K; same-day for 10-K and 10-Q.
• Product launches and contracts: 24–72 hour latency typical depending on source coverage.
• Hiring intel (job postings): 24-hour ingestion cadence from primary ATS sources (Greenhouse, Lever, Ashby).

Service-level expectations: 99% endpoint availability, sub-second p95 response times for filtered queries under 100 results. Hard SLAs available for enterprise OEM partners on request.

Attribution requirements

All commercial integrations require visible attribution: "Powered by Fundz" (or substantively equivalent text approved in writing) in the product UI, in a location reasonably visible to end users. Acceptable placements:

• Footer of the product UI (most common)
• Data panel header where Fundz data is rendered
• Source citation footnote on individual data points

Attribution is non-negotiable across both Build-Phase and Commercial OEM tiers, and persists for the duration of the integration.

Caching and rate limits

Reasonable-use guidelines during the Build-Phase License period:

• Approximately 50,000 API calls per month
• Approximately 25,000 records returned per month
• Approximately 5 concurrent connections

Sustained usage exceeding these guidelines (e.g., >2x for two consecutive months) triggers a notice and may accelerate conversion to the Commercial OEM Tier or prompt renegotiation. Hard metering and per-key quotas are added at conversion. Commercial OEM tier customers get higher limits negotiated as part of the addendum.

Caching guidance: cache responses on your side for 15–60 minutes for end-user-facing queries; longer (4–24 hours) for derived analytics views. Don't bypass cache for every page load — that's the most common cause of unexpected rate-limit incidents.

Use case patterns

SaaS data products

Embed Fundz signal data alongside your own product's primary data layer. Common patterns: contact-enrichment SaaS adding "recent funding" to enriched profiles; CRM apps adding "trigger events" to account records; sales-prospecting tools showing "companies that just hit a signal" alongside contact lists.

Capital markets and deal platforms

Pipe Fundz signals into deal-flow systems for institutional investors, capital markets firms, and deal-sourcing tools. Funding rounds become inbound deal flow; M&A signals become precedent-transaction context; SEC filings become risk-monitoring inputs.

Outreach and SDR platforms

Trigger workflows on company life-events. Funding round = automated personalized outreach sequence. New CMO = vendor-evaluation play. Hiring surge = scaling-pain campaign. Most outreach platforms benefit from Fundz signals as a trigger layer rather than as a contact-enrichment layer.

Getting started

1. Email john@fundz.net describing your product and intended integration. Include: target audience, expected end-customer count, integration timeline, and which endpoints you'll consume.
2. For pre-revenue builds, sign the Build-Phase License addendum ($250/mo, 6-month term).
3. Receive an API key, attribution-asset bundle, and integration documentation.
4. Build, validate, and ship.
5. On first paying end customer or 6-month milestone, convert to Commercial OEM Tier with pre-agreed terms.

Common mistakes

• Using personal-use API access for commercial integration. The Strategic plan ($149/mo) does not authorize commercial redistribution. If your product embeds Fundz data and you sell that product to third parties, you need the commercial license addendum.
• Skipping attribution. Attribution is non-negotiable and audit-detectable. The integration depends on it.
• No caching layer. Hitting the API on every end-user page load burns rate limits and adds unnecessary latency. Cache for 15–60 min for end-user queries.
• Bulk-pulling for export. The license restricts bulk export and data-warehouse extraction. If you need a one-time historical seed, coordinate with Fundz support so it doesn't trigger abuse-detection.
• Building competitor functionality. Using Fundz data to power a directly competing signal-intelligence product is a license violation. Adjacent or complementary products are fine; competitive replacements are not.

Troubleshooting

I'm getting 429 rate-limit responses

Reduce poll frequency, add a caching layer, or batch requests. If you're sustainably above the reasonable-use guidelines, that's the trigger to convert to Commercial OEM Tier with negotiated higher limits.

The data I need isn't in any endpoint

Email john@fundz.net with the specific use case. Many partners drive net-new endpoint development — the InfinixIQ + Issuance integrations both surfaced functionality that became part of the standard API.

Authentication is failing

Verify your API key is active and your Bearer token format is correct. API keys are scoped to specific tiers; if you upgraded from Build-Phase to Commercial OEM, you may need a new key with the upgraded tier scope.

My customers are asking for white-label / multi-tenant

Multi-tenant white-label requires the uplifted base fee tier ($1,500/mo + per-seat or $1,000/mo + revshare). Email john@fundz.net to discuss the addendum amendment.

I want exclusivity in my vertical

Broad category exclusivity is rarely granted at standard pricing. Limited options exist (24-month first-mover pricing lock, narrow conditional exclusivity in specific sub-categories with revenue milestones, MFN on pricing only). Email john@fundz.net to discuss.

Bonus: the Partner Program (for service-firms reselling)

If you're a services firm (consultancy, agency, advisory) that wants to recommend Fundz to your clients rather than embed the data into your product, the Partner Program is a different fit. Your clients get the dashboard at a discount, you get rev-share on conversions, no API integration required. Email john@fundz.net to discuss.