Fluxx
Fluxx is a cloud grants management platform for foundations, government agencies, corporations, and nonprofits, covering the full grant lifecycle from funding announcement through pre-award applications, post-award payments, and measurement and evaluation. Fluxx Grantmaker includes a RESTful API (REST API v2) available to customers for building custom integrations with financial, CRM, and business-intelligence systems. The API is exposed per-client on each customer's own Fluxx instance under https://{client}.fluxx.io/api/rest/v2, is authenticated with OAuth 2.0 credentials created in that instance, and is driven by a dynamic, instance-specific data model whose reference documentation is generated at /api/rest/v2/doc for each deployment. Because the surface is per-instance and gated behind an authenticated customer deployment, the endpoints below are honestly modeled from Fluxx's documented REST v2 conventions rather than pulled from a single public reference.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Fluxx the way a machine reads it — 7 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Fluxx scores 14.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fluxx
Each block below is one kind of artifact we hold for Fluxx. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Fluxx Records API
RESTful create, list, get, update, and delete access to Fluxx model records such as GrantRequest, Organization, and RequestTransaction under /api/rest/v2/{model}. Supports colum...
Fluxx OAuth API
OAuth 2.0 authorization for the Fluxx REST API. Administrators register an application at /oauth/applications on their instance to obtain a client ID and client secret, then exc...
Fluxx Documents API
Access to files and documents attached to grant records, exposed through Fluxx document models (such as ModelDocument) under /api/rest/v2/{model}. Used to list and retrieve atta...
Fluxx Users and Organizations API
RESTful access to Fluxx people and organization records - the User and Organization models under /api/rest/v2/{model} that represent grantees, grantseekers, staff, and funding o...
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Fluxx — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fluxx-grants · machine-readable index on apis.io